A Practical Checklist for Receiving OpenAI Phone Verification Codes

What does OpenAI ask a phone number for?

OpenAI has used SMS verification at several points: when someone creates a ChatGPT or developer platform account, during some security checks, and occasionally when an account's activity triggers an extra confirmation step. The exact rules differ by region and change over time, so treat any prompt as something your flow has to handle rather than something you can predict.

OpenAI is also known to limit how many accounts a single number can verify. That matters for teams: if three engineers each verify a test workspace with their personal phones, those phones get tied up. A ChatGPT phone number that belongs to the test setup, not to a person, keeps the arrangement clean and auditable.

Pre-flight checklist: is everything ready before you order?

Run through this list once and most failed attempts never happen:

• Account and wallet. An OTP Route account with a funded USD wallet. Top-ups by card or USDT/USDC each produce a PDF invoice.
• API key. A Bearer key from the Developer console, starting with or_live_, stored in your secrets manager rather than in a test file.
• Webhook endpoint. A public HTTPS route with its endpoint secret saved, if you plan to receive codes by push.
• Country decided. Match the market of the account you are testing; the next section covers this.
• Purpose checked. The account is yours, your company's, or a test account for a product you build, and it will be used within OpenAI's terms.
• Temporary or persistent? If the account must log in again later, read the Dedicated Number section first.
• Sandbox for the build phase. Ask for sandbox on a development account if you want simulated numbers and codes while writing the integration.

Which country should the number come from?

The openai service is currently routable in 197 countries, including the United States, Canada, the United Kingdom, Germany, France, the Netherlands, Spain, Italy, Poland, India, Japan, South Korea, Singapore, Australia, Brazil, Mexico, Nigeria, Kenya, the Philippines and the United Arab Emirates.

Pick deliberately. OpenAI does not offer its products in every country, and an account whose number, billing details and usage all point to different places looks odd to any fraud model. For QA, choose the country your test case describes: if you are checking the onboarding of a UK customer, use a UK route. Our QA testing guide shows how teams map test cases to countries.

Steps: receiving the code through the API

This is the core of the ChatGPT verification code API flow:

1. Call GET /api/v1/prices?country=gb&service=openai (swap in your country id) to see whether the pairing is available and what it costs right now.
2. Create the order with POST /api/v1/activations and the body {"service": "openai", "country": "gb"}. Save the returned activation id next to your test run.
3. Type the returned number into OpenAI's verification screen, in full international format.
4. Wait for activation.sms_received on your webhook. Before trusting it, recompute HMAC-SHA256 over "<t>.<raw body>" with your endpoint secret, compare it with the v1 value in X-OTPRoute-Signature, and reject the event if t is too old. The article on securing OTP webhooks with HMAC walks through it.
5. Make the handler idempotent. Key on the activation id, so a retried delivery does not submit the code twice or fail a test that already passed.
6. No webhook? Poll GET /api/v1/activations/{id} every few seconds instead, staying well under the 300 requests per minute account limit.
7. If the run is abandoned, send POST /api/v1/activations/{id}/cancel so the funds return immediately.

Steps: the dashboard route for manual testers

Not everyone needs code to receive ChatGPT OTP messages. A support lead verifying one company workspace can:

1. Sign in with email and a 6-digit code, or with Google.
2. Select the ChatGPT (OpenAI) service and a country.
3. Confirm the displayed price and copy the number.
4. Paste it into OpenAI's form and wait on the activation page; the code appears there when it lands.

Turning on two-factor (TOTP) for your own dashboard login is a sensible extra step, since that account can receive codes for your company.

Troubleshooting: what if the code never shows up?

First, the safety net: an activation lasts 20 minutes, and if no SMS arrives in that window, or you cancel, the full amount goes back to your wallet. You are charged only for delivered codes.

Then work through the likely causes:

• OpenAI declined the number. Some services refuse virtual numbers outright or for certain regions. If the form rejects the number immediately, no SMS will follow.
• Slow delivery. Leave the activation open for the full window before concluding it failed.
• Route conditions. Try again later, or with another country that fits the test, rather than firing new orders in a loop.
• Wrong format. Make sure the number was entered with its country code and no stray trunk zero.

Keep the activation id in your logs; it makes support conversations short.

When does a Dedicated Number fit better?

A one-time code is fine for a throwaway test workspace. It is the wrong tool for an account your team will log back into next month, because a temporary number can't receive a second verification later.

For those cases, a Dedicated Virtual Number is the better fit: a US or Canadian line you keep while it renews, from $1.95/month, bought instantly in the dashboard. Inbound SMS appear there and are forwarded to your webhook as number.sms_received. Dedicated lines are available only in those two countries.

What counts as responsible use?

OTP Route is for testing and operating your own legitimate accounts and products. Follow OpenAI's terms, keep to one account per real person or business, and remember that our Acceptable Use Policy applies to every activation. A virtual number for ChatGPT should support a real QA, onboarding or operations need, never a way around a platform's limits.

Frequently asked questions

Can I use OTP Route for ChatGPT SMS verification for testing?

Yes. Order an openai activation, enter the number in the test account, and read the code from the API, webhook or dashboard.

What is the service id for ChatGPT in the API?

It is openai, sent in the service field of the activation request and the prices query.

Does OpenAI accept every virtual number?

No. It may reject some numbers or regions, which is why undelivered codes are refunded to your wallet automatically.

How do I avoid processing the same code twice from a webhook?

Store the activation id when the first event arrives and ignore repeats with the same id, after verifying the signature each time.

Can my team log back into the ChatGPT account later with the same number?

Not with a one-time activation. Use a US or Canadian Dedicated Number if repeat verification is likely.

Is there a monthly fee to receive OpenAI codes?

No. The wallet is prepaid and pay as you go, with no plan to choose.

Is OTP Route affiliated with OpenAI?

No. ChatGPT and OpenAI are trademarks of their owner, and OTP Route is an independent routing service.

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.