Receiving Flipkart OTPs on test numbers via API or dashboard

Where does Flipkart ask for a phone code?

Flipkart, the Indian e-commerce marketplace, leans heavily on the mobile number as the account key. Shoppers typically sign up and log in with a number plus a one-time code, and a code can also be requested when contact details change or when the app wants to confirm it is really the owner. Sellers working in Seller Hub meet similar checks.

For a team building around Flipkart, such as an affiliate tool, a seller integration or a QA lab checking a partner flow, every one of those prompts is a step that needs a real SMS. Using a staff member's personal phone for that is fragile and leaks private numbers into business accounts.

Which countries can deliver a Flipkart OTP?

The Flipkart service currently routes through 201 countries. Examples include India, Nepal, Bangladesh, Sri Lanka, United Arab Emirates, Saudi Arabia, Qatar, Singapore, Malaysia, United Kingdom, United States, Canada, Kosovo and Bulgaria.

Country choice should match the test case. Flipkart's storefront is built for Indian shoppers, so a +91 route mirrors the most realistic user. Other countries help when you need to see how a flow treats an overseas number; whether Flipkart accepts one is Flipkart's decision and can change.

Teams serving Indian shoppers who live abroad, for example in the Gulf, sometimes test both sides: the +91 number the shopper still keeps and the local number they use day to day. Running the same test script across two countries only means changing the country id, so that comparison is cheap to set up.

How do I pull a Flipkart verification code through the API?

With a Bearer key (or_live_ prefix) from the Developer console:

1. Check the live rate: GET /api/v1/prices?country=in&service=flipkart.
2. Order: POST /api/v1/activations with {"service": "flipkart", "country": "in"}.
3. Type the returned number into Flipkart and request the code.
4. Handle the activation.sms_received webhook, or poll GET /api/v1/activations/{id}.

Verify X-OTPRoute-Signature before trusting a webhook and discard stale timestamps. Make the handler idempotent by keying on the activation id, so a redelivered event cannot submit the same code twice. The webhook capture guide shows the pattern.

Why might the Flipkart OTP not arrive?

Several things can stop it: the route is busy, Flipkart throttles repeated requests from one session, or Flipkart declines the number because it recognises it as virtual. None of that costs you anything, because an activation with no SMS after 20 minutes is refunded to the wallet automatically, and cancelling early does the same.

If it happens, let the window finish, try again later or on another route, and don't fire new orders in a tight loop; that tends to trip rate limits on Flipkart's side too.

Can a non-developer do this from the dashboard?

Yes. Open the OTP Gateway, search for Flipkart, choose a country, check the price and confirm. The number appears with a countdown; once the code lands it sits next to the number, ready to copy. Merchandisers and support staff often work this way while engineers use the API.

For a manual QA pass, note three things per attempt: the country used, whether the code arrived, and what Flipkart showed on screen. Those notes make it easy to tell a route issue from a change in Flipkart's own flow when someone repeats the test a week later.

When does a dedicated number fit better, and what counts as fair use?

Gateway numbers serve one code, so they suit tests, not accounts that must log in again next month. Dedicated Numbers, from $1.95/month, stay yours while they renew, receive SMS in the dashboard and by webhook, but exist only in the US and Canada; they suit a Flipkart-related account only if that account accepts such a number.

Whatever you choose, follow Flipkart's terms: one account per real person or business, no promo farming, nothing that evades checks. OTP Route is for testing and running your own legitimate products and accounts, under the Acceptable Use Policy. See temporary vs dedicated numbers.

Frequently asked questions

What is the Flipkart service id in the OTP Route API?

The id is simply flipkart, passed as the service value for price checks and activation orders.

Can I receive a Flipkart OTP without an Indian SIM?

Yes. An Indian number from the OTP Gateway receives the Flipkart code, and you read it in the dashboard or via the API.

Is a virtual number for Flipkart always accepted?

No. Flipkart may refuse some virtual numbers, which is why you are refunded when no code arrives.

Is Flipkart SMS verification for testing possible in a CI pipeline?

Yes. Poll GET /api/v1/activations/{id} from the job, or point a webhook at a test receiver; a sandbox account can return simulated codes during development. Real runs draw on a prepaid USD wallet, topped up by card or USDT/USDC, with no monthly fee and a PDF invoice per top-up.

How much does a Flipkart phone number for a code cost?

From $0.20 per code; the exact price depends on the country and is returned by the prices endpoint before ordering.

Can I log back into the same Flipkart account later?

Not with a gateway number, since it covers one verification. Plan long-lived accounts around a number your business controls.

Which country should I pick for a Flipkart test?

Start with India, because that is where Flipkart's shoppers are. Pick another country only when the test case is specifically about an overseas number.

Is OTP Route affiliated with Flipkart?

No. Flipkart is a trademark of its owner, and OTP Route has no affiliation with it.

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.