Mexican verification codes on +52 numbers for QA and launch teams

What is unusual about Mexican phone numbers?

Mexico moved to a uniform ten-digit national plan in 2019. The old dialing prefixes, such as 01 for long distance and 044/045 for calling mobiles, were retired, and so was the extra 1 that used to sit between +52 and a mobile number in international format.

For anyone storing numbers that means one rule: E.164 for Mexico is +52 followed by exactly ten digits, for landlines and mobiles alike. Legacy databases and some older SDKs still hold values shaped like +521 plus ten digits. Normalise those by removing the stray 1, otherwise deduplication and lookup will treat one customer as two. A validation test that feeds both shapes into your sign-up form is cheap and catches a lot.

Why do product teams test against Mexico?

Mexico is one of the largest Spanish-speaking markets, and it is often the first stop for US companies expanding south or for nearshore engineering teams building for their home market. Typical reasons to keep a +52 number for testing in the pipeline:

• Localisation QA. Mexican Spanish copy, date formats and currency display differ from Spain's, and the verification SMS usually arrives in Spanish when the app locale is set that way.
• Messaging-first onboarding. WhatsApp is the default messenger for many Mexicans, so flows that offer a WhatsApp code as well as SMS deserve coverage on a local number.
• Cross-border customers. Families and businesses on both sides of the border mean a US product may see real +52 sign-ups well before any formal launch.

The mobile app verification page describes how app teams wire this into release testing.

Which services can I receive Mexico SMS OTP codes from?

Mexico is one of the broader routes, with more than 1,800 services available in the current snapshot. A selection that shows up often in launch plans: WhatsApp, Telegram, Facebook, Instagram, TikTok, X (Twitter), ChatGPT (OpenAI), Microsoft & Outlook, Amazon, Uber, Discord, Netflix, Airbnb, eBay and AliExpress.

Inventory moves during the day. Before a test depends on a particular service, confirm it through GET /api/v1/services or in the dashboard, and read the live price for Mexico rather than hard-coding one.

What does the Mexico OTP API sequence look like?

Authentication is a Bearer key with the or_live_ prefix against https://otproute.com/api/v1. The country id is mx.

1. Check cost with GET /api/v1/prices?country=mx&service=whatsapp.
2. Start an activation: POST /api/v1/activations with the body {"service": "whatsapp", "country": "mx"}. Keep the returned activation id.
3. Submit the ten-digit number in the flow you are testing.
4. Collect the code by polling GET /api/v1/activations/{id}, or subscribe to activation.sms_received and let the event come to you. activation.expired and activation.cancelled close the loop.

When using webhooks, validate X-OTPRoute-Signature by computing HMAC-SHA256 of <t>.<raw body> with the endpoint secret and rejecting old timestamps. Handlers should be idempotent, keyed on the activation id. The developer overview and the guide to OTP testing in CI pipelines go further.

How do I get a +52 number without writing code?

From the dashboard, open the OTP Gateway, choose Mexico and the service, and confirm the price on screen. Press order, paste the number into the app, and watch the activation card; the code is displayed there once received. This route suits growth managers checking a landing-page funnel or support agents reproducing a customer's report.

A Mexican code is late. How should I troubleshoot?

A +52 activation stays live for 20 minutes, so hold off on judging the route until that clock has run out. If nothing comes, the amount is refunded to the wallet without any action from you, and cancelling early does the same.

• Confirm the service accepts virtual numbers; several platforms reject them by policy.
• Try again later, or exercise the flow with another service to separate a route problem from a bug in your own form.
• Check that your app sent the number as +52 and ten digits, not a legacy +521 shape.
• Space out retries in automated jobs instead of re-ordering in a tight loop.

Can I keep a Mexican number long term, and how is it paid for?

Not as a self-serve product. Dedicated Numbers are sold instantly only for the United States and Canada, from $1.95/month; there is no equivalent Mexican line in the dashboard. Teams that need one can write to [email protected], though availability depends on local regulation and cannot be promised.

Everything else is pay as you go from a single USD wallet: no subscription, top-ups by card or USDT/USDC, and a PDF invoice for each top-up. A sandbox account with simulated numbers and codes can be requested for integration testing. The pricing page has the details. Use every number in line with the service's terms and OTP Route's Acceptable Use Policy.

Frequently asked questions

Do Mexican mobile numbers still need a 1 after +52?

No. Since the 2019 numbering change, Mexican numbers are written as +52 plus ten digits. Strip a leftover 1 from older records.

What is the API country id for Mexico?

It is mx. Pass it in GET /api/v1/prices and in the JSON body of POST /api/v1/activations.

Will the verification SMS be in Spanish?

Often, yes, when the app's language is Spanish, but wording depends on each service. Parse the numeric code rather than a fixed phrase.

How much is a +52 number for testing?

From $0.20 per code; the price depends on the service and is shown live before you order.

What happens to my money if no Mexican code arrives?

It goes back to your wallet automatically when the 20-minute window ends or when you cancel.

Can I test a WhatsApp sign-up for Mexico without a local phone?

Yes, if WhatsApp is available on the Mexico route at that moment. Request a number with the service id whatsapp and country mx, and follow WhatsApp's terms.

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.