Getting US (+1) verification codes: a one-time number or a line you keep

One-time code or dedicated US number: which do you need?

Start with a single question: will this account ever need another code on the same number?

• OTP Gateway covers one verification event. You pick a service and the us route, get a +1 number, and receive exactly one code. It suits automated test runs, onboarding QA and a sign-up you will not repeat on that number.
• Dedicated Virtual Number covers anything that has to keep working. You buy it instantly in the dashboard, it renews on a prepaid term from your wallet, and you can release it whenever you like. It suits a staging account that logs in every week, recovery for a shared team login that should not sit on someone's personal phone, a support or operations line, and a US business presence.

Plenty of teams run both: the gateway inside CI for throwaway sign-ups, plus a few dedicated lines for the long-lived QA accounts testers reuse. We compare the two in more depth in temporary vs dedicated numbers.

What comes with a dedicated US line?

A dedicated number on OTP Route is a working line, not just an inbox:

• Inbound SMS shown in the dashboard and forwarded to your webhook as a number.sms_received event.
• Outbound SMS, so support or ops can answer from the same number.
• Outbound calling from the browser, with no app to install and no SIM to manage.
• Prepaid terms from $1.95/month that renew from the wallet, and release at any time.

These lines are offered only in the United States and Canada, which makes them the two markets where a team can hold its own number self-serve. Purchase and renewal are explained on the virtual numbers page.

How do I pull a one-time +1 code through the US OTP API?

For automation, the US route behaves like every other gateway country. Authenticate against https://otproute.com/api/v1 with a Bearer key (prefix or_live_) created in the Developer console, then:

1. Read the live price with GET /api/v1/prices?country=us&service=<id>.
2. Open an activation with POST /api/v1/activations, sending {"service": "discord", "country": "us"} or whatever service id the test needs.
3. Feed the returned number to the app under test.
4. Pick up the code from the activation.sms_received webhook, or poll GET /api/v1/activations/{id}.
5. Abort cleanly with POST /api/v1/activations/{id}/cancel if the test fails before the SMS step.

On the webhook side, check the X-OTPRoute-Signature header, an HMAC-SHA256 of <t>.<raw body> keyed with the endpoint secret, discard events with stale timestamps, and dedupe on the activation id. Limits are 10 API keys, 5 webhook endpoints and 300 requests per minute, enough for a parallel suite with one key per environment. The QA testing page shows how teams fit this into a pipeline.

Which services can verify on a US number?

More than 5,000 services can currently be verified on the US route. Frequent picks include WhatsApp, Telegram, Google (Gmail & YouTube), Instagram, TikTok, Discord, ChatGPT (OpenAI), Claude, Microsoft & Outlook, Amazon, LinkedIn, Uber, Signal and Netflix.

Treat that as a snapshot. What can be ordered changes during the day, so let your code read availability from the API instead of from a page like this one. Whatever you verify should be your own product or an account your business legitimately runs; each service's terms and OTP Route's Acceptable Use Policy apply.

Can a non-technical colleague order a United States verification number?

Yes, from the dashboard. Pick United States, choose the service, check the price displayed before you commit, and paste the +1 number into the sign-up form. The code shows up on screen inside the same 20-minute activation window the API uses. If no SMS arrives before the window closes, or you cancel, the full charge goes back to the wallet automatically, so you only pay for codes that actually arrive. Dedicated lines are bought from the same dashboard, and their inbound messages appear there as well.

What if the US code never shows up?

• Give the activation time. The 20-minute window exists for senders that are slow.
• Check whether the service accepts virtual numbers. Some turn them away, and the automatic refund covers exactly that case.
• Retry later, or switch to another service route, rather than hammering the same one.
• Put a backoff between orders in automated suites; a tight retry loop only wastes time.

If an account needs codes again and again, step back and ask whether it should live on a dedicated line instead of fresh one-time numbers.

How should +1 numbers be formatted and stored?

US numbers follow the North American Numbering Plan: a three-digit area code plus a seven-digit local number, ten digits in all. In E.164 that becomes +1 followed by those ten digits, with no spaces, dashes or parentheses. Users often type a leading 1 or wrap the area code in parentheses, so strip that before storing anything.

One trap matters for multi-country products: Canada and several Caribbean territories share +1, so the dial code alone never tells you the country. Keep country as its own field, or derive it from the area code with a maintained library.

Verification texts on US numbers are nearly always in English, with Spanish showing up in apps localized for Spanish-speaking users. Many services send from short codes rather than ten-digit numbers, so any sender filter should allow both. Teams want a +1 number for testing because the US is a frequent first launch market, American customers expect a +1 flow, and a US line helps with partners and support.

How are codes and lines billed?

One prepaid USD wallet funds both products, with no monthly fee and no plan to pick. Top up by card or with USDT/USDC; every top-up and number purchase produces a PDF invoice by email. Before wiring the SMS verification API into production tests, ask support to put a development account in sandbox, which returns simulated numbers and codes so the full OTP routing flow can be exercised without spending funds. Current figures live on the pricing page.

Frequently asked questions

Can I keep a US number for an account that has to log in again?

Yes. Buy a Dedicated Virtual Number from the dashboard; it renews from your wallet from $1.95/month and receives every SMS sent to it until you release it.

Can I test my app's US sign-up flow without an American SIM card?

Yes. Order a +1 number from the OTP Gateway with the country id us, trigger the sign-up, and read the code in the dashboard, on a webhook or by polling.

Do I pay if the verification code never comes?

No. If nothing reaches the number within 20 minutes, or you cancel first, the full amount is returned to your wallet automatically.

Can a dedicated US number make phone calls?

It can place outbound calls straight from the browser and send outbound SMS, with no app or SIM involved.

Are dedicated numbers available outside the United States?

Canada is the only other country with them. Elsewhere the OTP Gateway handles one-time codes, and you can email [email protected] to ask about a long-term line.

Does OTP Route offer a sandbox for US integration tests?

Yes, on request. A development account can be switched to sandbox so simulated numbers and codes reach your webhook without spending wallet money.

Service names are trademarks of their respective owners. OTP Route is not affiliated with them. Use numbers lawfully, follow each service's terms and our Acceptable Use Policy.