Pick the country
Start with the country where the verification needs to happen.
A focused workspace for buying temporary virtual numbers, checking country-based pricing, and receiving one-time SMS codes from the existing ScrapingBuddy dashboard.
Use it within 5 minutes. Your personal phone number stays private.
Start with the country where the verification needs to happen.
Select the app or website from the live service catalogue.
See the current country-based cost before wallet credit is used.
Copy the number, wait for the message, and capture the code.
The dashboard shows the live catalogue. These examples show the kind of services teams commonly check before placing an order.
Browse live servicesAvailability and price change by service and country. Open the dashboard to find the current route that works for your verification need.
Availability updates by country and service so your team can pick the best route before starting an order.
Fund once and pay per verification. Each order shows its current price before purchase.
Numbers, statuses, messages, and final outcomes stay visible in the same workspace.
Run manual checks in the dashboard first, then automate repeated verification flows with API keys.
Numbers are designed for short verification windows, not permanent ownership or account recovery.
Track pending, received, cancelled, completed, and refunded order states without guessing.
Start manually in the dashboard. When the pattern is clear, use API keys for repeatable verification jobs.
View SMS API docs/api/v1/orders/{id}{
"order": {
"status": "RECEIVED",
"phone": "+440000000000",
"sms": [{ "code": "123456" }]
}
}There is no monthly plan to understand before starting. Pick a country and service, review the live price in the dashboard, and pay from wallet credit only when placing an order.
A quote is valid for two minutes, but it does not reserve stock. Availability is checked again at purchase. If a purchase is explicitly rejected, obtain a fresh quote and review its price. If the response was lost or timed out, first recover the original order; immediately buying against a new quote could purchase a second number.
Not until you know the original outcome. Retrieve the existing order if you have its ID. For an API retry, reuse the saved Idempotency-Key and the same quote ID. A purchasing state means allocation is still in progress; purchase_unknown needs support review. Neither is a reason to create a replacement purchase automatically.
Cancellation is available while the order is active and no SMS has arrived, subject to the server's current order state. If cancellation returns a conflict, refresh the order before trying again. Check refunded_at for a recorded refund; an expired browser countdown or a local timeout is not confirmation. Contact support with the order ID if a refund remains under review.
Inspect the order's sms array, including each message's text and code. RECEIVED alone does not guarantee a usable verification code: a message may contain other content or no separately extracted code. Finish the order only after the message you need has arrived and been used. Keep the order ID if the delivery needs investigation.
Background provider checks continue while the order is active, even if your browser or application disconnects. Reopen the same order instead of purchasing again. API integrations should read active orders about every ten seconds, deduplicate received messages and stop polling terminal states. Closing the page does not extend the number's lifetime.
Do not rely on it. The number is temporary and tied to its activation order; a future order is not a promise of the same number. Use an account-recovery method you control for long-term access. A successful SMS delivery also does not guarantee that the target service will accept the number or approve the account.
Open the existing dashboard, choose a country and service, and see the current verification price before buying a number.
Open Dashboard