Getting DoorDash SMS codes into your test runs and ops accounts

Where does DoorDash ask for a phone code?

DoorDash ties accounts to a mobile number so customers, couriers and stores can be reached about an order. Typical moments when it sends an SMS code:

• creating a customer account or adding a phone number to one;
• signing in on a new device or browser, as a login check;
• changing the phone number on file, or recovering access;
• onboarding as a Dasher, where the number becomes the courier's contact line;
• setting up merchant and store logins that restaurant staff share.

The exact prompts change as DoorDash updates its app, so build tests around "a code may be requested here" rather than a fixed screen sequence.

Which teams use a DoorDash phone number from OTP Route?

Mostly three groups. Developers building ordering, delivery or point-of-sale integrations need a test login that is not someone's personal phone. Restaurant groups and agencies set up store accounts for clients and want the verification step off an employee's SIM. QA teams in delivery and food-tech companies compare onboarding against a well-known reference app in the markets they launch in. The QA testing and operations teams pages describe both patterns.

Which country should the DoorDash number come from?

The DoorDash route is available in 196 countries, including the United States, Canada, Australia, New Zealand, Japan, Mexico, the United Kingdom, Germany, Finland, Sweden, Norway, Poland, Puerto Rico, India and the Philippines.

Pick the country that matches the account under test. A number from a market where the account will never order looks inconsistent to DoorDash's risk checks and is more likely to be refused. For a US store login, use a US number; for an Australian consumer test, an Australian one. Availability per country changes through the day, so ask GET /api/v1/countries before each run.

How does the DoorDash SMS verification API flow run?

With a Bearer key (prefix or_live_) against https://otproute.com/api/v1:

1. GET /api/v1/prices?country=us&service=doordash returns the live price.
2. POST /api/v1/activations with {"service": "doordash", "country": "us"} reserves a number and returns an activation id.
3. Enter the number in DoorDash and request the code.
4. Handle activation.sms_received on your webhook. Verify X-OTPRoute-Signature (t=<unix>,v1=<hex>, HMAC-SHA256 of <t>.<raw body> with the endpoint secret), reject stale timestamps, and make the handler idempotent by keying on the activation id, since a retry can deliver the same event twice.
5. No public endpoint in your CI? Poll GET /api/v1/activations/{id} instead, at a sensible interval.

The webhook capture guide shows a full handler.

How do I do it from the dashboard?

Choose DoorDash as the service, then the country, check the displayed price and order. Paste the number into DoorDash; the code appears beside it when the SMS lands. If you finish early, cancel to release the hold. Each order stays in your activation history. Ops staff who only need a virtual number for DoorDash now and then can stay in the dashboard entirely; nothing there requires an API key.

Why might DoorDash not send the code?

Each activation lasts 20 minutes, and you only pay if the code arrives; otherwise, or after a cancel, the full amount returns to the wallet. DoorDash, like many apps, may decline numbers it classifies as virtual, which is exactly why that refund exists. If the window closes empty, retry later, try another country that fits the account, and avoid tapping "resend" repeatedly, which can trigger rate limits. Space out automated retries rather than looping.

It also helps to check your own side: confirm the number was entered with the right country selector in DoorDash, that your parser reads digits rather than a fixed English phrase, and that your webhook endpoint returned a success status so events are not stuck in retry. The failed delivery guide lists more checks.

What does responsible DoorDash testing look like?

Follow DoorDash's terms. Keep one account per real person or business, and never use OTP Route numbers to claim new-customer promotions more than once or to recreate a restricted account. OTP Route is for testing your own products and operating your own legitimate accounts, and its Acceptable Use Policy applies to every order. DoorDash is a trademark of its owner, and OTP Route is not affiliated with it.

Frequently asked questions

Can I receive a DoorDash OTP through an API?

Yes. Create an activation with service doordash and the country id you need, then read the code from the activation.sms_received webhook or by polling the activation.

Which DoorDash phone number country should I choose?

The one that matches the account's market, for example us for a US store login. Mismatched countries are more likely to be refused.

Does DoorDash accept a virtual number for verification?

Not always. DoorDash can decline numbers it treats as virtual, and when no code arrives within 20 minutes your wallet is refunded automatically.

What is a better option for a store account that must log in again later?

A Dedicated Number in the US or Canada, from $1.95/month, which you keep while it renews and which forwards inbound SMS to your webhook as number.sms_received. A one-time OTP Gateway number cannot receive a later login code.

Can I run DoorDash SMS verification for testing in CI without spending money?

Yes. Request sandbox mode on a development account to get simulated numbers and codes for end-to-end tests that leave the wallet untouched.

How much does a DoorDash verification code cost?

From $0.20 per code; the exact price depends on the country and is returned by GET /api/v1/prices and shown before you order.

How do I pay for DoorDash codes?

Top up the prepaid USD wallet by card or with USDT/USDC. There is no monthly fee, and every top-up comes with a PDF invoice by email.

Can I use OTP Route to create several DoorDash accounts for promo codes?

No. That breaks DoorDash's terms and OTP Route's Acceptable Use Policy; numbers are for testing and running your own legitimate accounts.

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.