Real-number OTP testing for iOS and Android apps

Mobile apps depend on phone verification more than most products, often using the phone number as the primary identity. Each platform adds its own details: Android SMS retrieval with app hashes, iOS one-time code autofill, deep links, and different behaviour on emulators, simulators and physical devices. Testing all of it with a handful of SIM cards rarely covers the markets an app actually ships to.

OTP Route lets mobile teams request verification numbers in many countries through a REST API and receive codes through signed webhooks. Device farms and emulator-based tests can fetch the code from your test harness and type it into the app, while the raw message text helps confirm templates, app hashes and formatting. Live inventory varies by service and time, so tests should check availability first. Unused activations are refunded automatically to your USD wallet.

Start free OTP Gateway

The problem

⚠️

SIM-based testing does not scale across device farms and countries

⚠️

Platform-specific SMS formats such as app hashes are easy to break

⚠️

Emulators and simulators cannot receive real SMS on their own

How OTP Route helps

🧭

Device-farm friendly

Because codes arrive server-side, tests running on emulators, simulators or remote device farms can fetch them via the API and enter them through UI automation tools such as Espresso, XCUITest or Appium. No physical SIM needs to be inserted into each device.

⚡

Template and app-hash checks

The API returns the full message text, so you can confirm that the Android app hash, the iOS domain-bound code format and the wording are correct before running autofill tests on physical devices. Formatting regressions are caught early in the cycle.

🔐

Coverage for app store markets

Test signup in the countries where your app is listed. Verification numbers across many markets help reveal number-format bugs, localisation issues and regional routing differences before they show up in app store reviews, ratings and support queues.

📈

Pay only for completed checks

Activations are charged from a USD wallet, and those that do not receive a code are refunded automatically. Mobile release cycles with many test runs stay predictable, and the dashboard shows each activation's outcome for debugging.

A typical workflow

Configure the OTP Route API key in your mobile test harness

Request an activation for the target country before the signup test

Enter the number in the app via UI automation on an emulator, simulator or device

Fetch the code from the signed webhook payload or by polling the API

Type the code into the app, assert success and close the activation

FAQ

Will iOS or Android autofill the code from a verification number?

No. The SMS is received by OTP Route's number, not by the test device, so platform autofill will not trigger. Use the API to read the code and enter it through UI automation. Test autofill separately on a physical device with its own SIM, using the message format you validated via the API.

Which mobile test frameworks can I use?

Any framework that can make HTTP requests or call a helper service works, including Espresso, XCUITest, Appium, Detox and Maestro. Typically a small helper in your test code requests the activation, waits for the code and returns it to the UI step that types it in.

Can I test apps that verify phone numbers via WhatsApp or flash calls?

OTP Route verification numbers receive SMS. Verification through OTT messaging apps or flash calls is outside the scope of temporary activations. If your app supports several channels, choose SMS for these tests and cover the other channels on physical devices.

Build it on OTP Route

Pay as you go with no monthly fee, USD wallet, signed webhooks and automatic refunds on unused activations.

Create account API docs