Capturing Careem OTPs with an API-driven verification number

What is the call sequence for a Careem verification code API?

All requests go to https://otproute.com/api/v1 with a Bearer key (prefix or_live_) from the Developer console. For Careem the flow is short:

1. GET /api/v1/prices?country=ae&service=careem returns the live price for a UAE number; swap the country id for the market you are testing.
2. POST /api/v1/activations with {"service": "careem", "country": "ae"} returns an activation id and the number.
3. Your test device or emulator types that number into Careem's phone screen.
4. The code reaches you through a webhook or a polling call, and your script submits it.
5. POST /api/v1/activations/{id}/cancel frees the activation if the run aborts before the code is needed.

The account limits are 10 API keys, 5 webhook endpoints and 300 requests per minute, which is plenty for a parallel test matrix. Endpoint reference lives in the docs.

How should a webhook handler process Careem codes?

Subscribe an endpoint to activation.sms_received, activation.expired and activation.cancelled. Every delivery includes X-OTPRoute-Signature: t=<unix>,v1=<hex>; compute HMAC-SHA256 over <t>.<raw body> with that endpoint's secret, compare it in constant time, and reject timestamps outside a small tolerance. The HMAC webhook guide shows the details.

Make the handler idempotent by keying writes on the activation id, because a retried delivery should not submit a code twice. Answer with a 2xx quickly and hand slow work to a queue.

Polling is the simpler alternative for a single test: call GET /api/v1/activations/{id} every few seconds until the code appears or the activation reports that it expired.

When does Careem ask for a phone number?

Careem is a ride-hailing and everyday-services app based in Dubai and best known across the Gulf, the wider Middle East and Pakistan. Like most ride apps, it treats the mobile number as the core account identifier: a code is typically sent at sign-up, and again when someone signs in on a new device or recovers access. Drivers and support staff also rely on that number to reach the rider during a trip.

For a QA team, that makes the phone step the first gate in every journey worth testing, from a new rider's onboarding to a corporate travel admin signing in on a fresh laptop.

Which country should the Careem phone number come from?

The Careem route currently spans 197 countries, but the useful choice is the market your account or test case belongs to. A rider profile for Riyadh should carry a Saudi number, and a rider onboarding test for Karachi or Lahore belongs on a Pakistani one. Commonly used options:

• United Arab Emirates (ae) and Saudi Arabia (sa)
• Pakistan, Jordan, Qatar and Egypt
• Kuwait, Bahrain, Oman and Morocco for other regional flows
• Turkey, the United Kingdom, India and Kenya for travellers and diaspora scenarios

The country routing article explains how to pick a fallback when the first country is short on stock.

How do I get a Careem code from the dashboard?

Open the OTP Gateway, choose Careem as the service and the country you need, and check the displayed price. Order the number, enter it in the Careem app, and leave the activation card open; the code appears there when it is received. The number is good for that single code.

Why might a Careem OTP not arrive?

Careem may refuse virtual numbers, depending on its own risk checks, and it can change that behaviour without notice. That is precisely why the refund exists: if no SMS lands in the 20-minute window, or you cancel, the money returns to the wallet automatically.

• Wait out the window before ordering again.
• Retry later or in another country that matches your scenario.
• Confirm the number was submitted in full international format.
• Do not hammer the route with back-to-back orders from CI; add a backoff.

Should a long-lived Careem login sit on a Dedicated Number instead?

An OTP Gateway number handles one code. If a Careem business account or a long-lived staging profile must log in again weeks later, a Dedicated Number keeps the same line while it renews. These are available instantly in the United States and Canada only, from $1.95/month, with inbound SMS in the dashboard and through the number.sms_received webhook. See virtual numbers.

Funding is a prepaid USD wallet topped up by card or USDT/USDC, with a PDF invoice per top-up and no monthly fee; development accounts can request a sandbox for simulated runs. The service exists so teams can test what they build and run accounts that genuinely belong to them. Follow Careem's terms, keep to one account per real person or business, and remember the Acceptable Use Policy applies. Careem is a trademark of its owner, and OTP Route has no affiliation with it.

Frequently asked questions

What service id does OTP Route use for Careem?

The service id is careem. Combine it with a country id, for example {"service": "careem", "country": "sa"}.

Can I receive a Careem OTP without a Gulf SIM card?

Yes. Order a number for the country you need from the OTP Gateway and read the code in the dashboard or through the API.

Does Careem accept virtual numbers?

Not always. Careem decides that on its side, which is why activations with no SMS are refunded automatically.

How much does a virtual number for Careem cost?

From $0.20 per code. The exact price varies by country and is returned by GET /api/v1/prices before you order.

Should I poll or use webhooks for Careem SMS verification testing?

Polling is fine for a single manual run. For parallel CI jobs, a signed webhook with an idempotent handler scales better.

Can I keep the same Careem phone number for future logins?

Only with a Dedicated Number, which is a US and Canada product. OTP Gateway numbers cover a single verification code.

Can I use OTP Route to create several Careem rider accounts?

No. Use it for your own testing and legitimate business accounts, and stick to one account per real person or business under Careem'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.