Meesho SMS verification for testing: checklist, API steps and fixes

What does Meesho use a phone number for?

Meesho is an Indian online marketplace built around low-cost products, resellers and small suppliers. Its shopping app signs people in with a mobile number and a one-time code instead of a password, and the same kind of code appears when an account is opened on a new device. Suppliers registering on the seller side also confirm a Meesho phone number. For QA staff, agencies and seller-tools developers, that means every login test depends on reading an SMS. Automating that step is what turns a manual, phone-in-hand check into something a test runner can repeat on every build.

Pre-flight checklist before ordering a number

• A legitimate account in scope. A test profile for your own integration, or a supplier account your business or agency runs for a client.
• The service id meesho, confirmed with GET /api/v1/services.
• A country chosen on purpose (see the next section).
• An or_live_ API key from the Developer console, or dashboard access for manual runs.
• Wallet funds, added by card or USDT/USDC.
• A webhook or polling job ready before you request the SMS, so the code is captured even if nobody is watching.

Which country should a Meesho test number come from?

The meesho service is available across 197 countries in the catalog, including India, Bangladesh, Nepal, Sri Lanka, United Arab Emirates, Saudi Arabia, Singapore, Malaysia, Indonesia, the Philippines, Kenya, Nigeria, the United Kingdom, Canada and the United States.

Meesho is designed for shoppers and sellers in India, so a +91 number is usually the one that reflects a real customer journey. Other routes can still be useful when you test how your own tools handle an unexpected number format, but whether Meesho accepts a number from a particular country is Meesho's decision. The country routing article explains how to keep that choice explicit in test configs.

Step by step: the Meesho verification code API flow

1. Check the live price with GET /api/v1/prices?country=in&service=meesho.
2. Create the activation: POST /api/v1/activations with {"service": "meesho", "country": "in"}. Save the activation id.
3. Enter the returned number in the Meesho login or supplier form and request the OTP.
4. Receive activation.sms_received at your webhook. Verify X-OTPRoute-Signature (HMAC-SHA256 over "<t>.<raw body>" with the endpoint secret) and reject stale timestamps.
5. Make the handler idempotent: store the activation id the first time, and ignore repeat deliveries for the same id so a retried webhook never runs the login step twice.
6. As an alternative, poll GET /api/v1/activations/{id} until the code appears or the run ends with activation.expired.

The webhook-based OTP capture guide covers queueing and retries in more detail.

Ordering a Meesho number from the dashboard

Sign in, open the OTP Gateway, choose Meesho as the service and India (or your intended country) as the route. Confirm the price on screen, copy the number into Meesho and request the code. It appears in the activation row when it lands, and the number keeps listening for the full 20 minutes.

Why might a Meesho code fail to arrive?

• Meesho, like many platforms, may refuse some virtual numbers. When that happens the refund covers you, and trying a different route later is reasonable.
• The SMS may simply be slow. Let the window run out before you judge the route.
• Repeated requests within seconds can hit Meesho's own throttling. Space out retries rather than re-ordering in a tight loop.
• Cancelling with POST /api/v1/activations/{id}/cancel ends the run and returns the full amount at once.

When does a Dedicated Number make more sense?

A one-time number is ideal for a single verification. An account that must sign in again next week needs a number you still control. OTP Route Dedicated Numbers, from $1.95/month, give you a long-term line with inbound SMS in the dashboard and forwarded through number.sms_received, but they exist only in the United States and Canada. Because Meesho is focused on India, confirm that it accepts such a number for your case before relying on one.

Using Meesho numbers responsibly

Follow Meesho's terms: one account per real person or business, no referral or promo farming, and no attempts to work around a suspended account. OTP Route is for testing and operating your own legitimate products and accounts, and its Acceptable Use Policy applies to every order. Teams running client work can read the agencies and resellers page for the recommended setup. Keep a record of which client each activation served; it makes audits and handovers far simpler.

Frequently asked questions

Can I receive a Meesho OTP online for testing my seller tools?

Yes. Order a meesho activation, use the number in the Meesho form, and read the code in the dashboard or through the API. You only pay if it arrives.

Is a virtual number for Meesho always accepted?

No. Meesho decides which numbers it accepts, and some virtual numbers are refused. If no code arrives in 20 minutes the charge is refunded.

Which Meesho phone number country should I pick?

India matches most real Meesho journeys. Pick another country only when your test case specifically needs it.

How much does Meesho SMS verification for testing cost?

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

Can I keep the same number for future Meesho logins?

One-time activations cover a single code. Long-term lines are Dedicated Numbers, available only in the US and Canada, so check Meesho accepts them first.

Can my CI pipeline run the Meesho flow without spending money?

Request sandbox mode for a development account; it returns simulated numbers and codes so the integration can be tested end to end.

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.