A checklist for receiving Bolt SMS codes on OTP Route numbers

Where does Bolt ask for a phone number?

Bolt, the Tallinn-founded mobility company behind ride-hailing, food and grocery delivery and scooter rental, builds its accounts around a mobile number. The rider app confirms that number with a one-time SMS code at registration, and the same kind of code typically reappears when someone signs in on a new device or recovers access. Driver, courier and business products follow a similar pattern.

For a business, that means the Bolt phone number is effectively the account key. Teams that run a company travel account, check how their own partner integration behaves in a new city, or keep a staff member's personal SIM out of a shared work login all need a controlled way to receive that code.

Pre-flight checklist before ordering a Bolt number

Work through these before spending anything:

• Purpose is legitimate: the account belongs to your organisation or is a test account for your own product, and Bolt's terms allow it.
• Market is chosen: the number's country matches where the account will operate. A rider account registered on one country's number and used elsewhere can behave differently.
• API key ready: a Bearer key with the or_live_ prefix, created in the Developer console (up to 10 per account).
• Webhook endpoint tested: subscribed to activation.sms_received, with signature checking switched on.
• Wallet funded: confirm with GET /api/v1/balance, or ask for sandbox mode to rehearse the flow with simulated numbers.
• Fallback agreed: decide in advance what the test does if no code comes back.

Which countries carry Bolt routes?

Bolt routes are currently listed for 198 countries. Examples include Estonia, Latvia, Lithuania, Poland, Czech Republic, Portugal, Germany, Croatia, Malta, Georgia, South Africa, Nigeria, Kenya, Ghana, Tanzania and Uganda.

Pick the country deliberately. Bolt's features, payment options and sign-up checks differ by market, so a test in Warsaw tells you little about a flow in Nairobi. Availability per country changes through the day; GET /api/v1/prices and the dashboard show what is live.

Step by step: the Bolt verification code API

1. Confirm the service id with GET /api/v1/services; for Bolt it is bolt.
2. Pick the country id from GET /api/v1/countries, for example ee for Estonia.
3. Read the live price: GET /api/v1/prices?country=ee&service=bolt.
4. Order: POST /api/v1/activations with {"service": "bolt", "country": "ee"}. Store the activation id and the returned number.
5. Enter the number in the Bolt app on your test device and request the SMS.
6. Handle the activation.sms_received event. Verify X-OTPRoute-Signature: t=<unix>,v1=<hex> by computing HMAC-SHA256 over <t>.<raw body> with the endpoint secret, reject old timestamps, and key writes on the activation id so a repeated delivery changes nothing.
7. If webhooks are not an option, poll GET /api/v1/activations/{id} every few seconds, well inside the 300 requests per minute limit.
8. Call POST /api/v1/activations/{id}/cancel if the test is abandoned.

Endpoint details are in the API docs, and securing OTP webhooks explains the signature check.

Step by step: the dashboard route

For a single Bolt SMS verification for testing or a one-time account setup, the browser is enough. Sign in, open the OTP Gateway, select Bolt and the market, check the price and confirm. Copy the number into the app, request the code, and watch it appear on the order card before the 20-minute timer runs out.

Troubleshooting: the Bolt code never showed up

An empty window costs nothing; when 20 minutes pass without an SMS, or you cancel, the full amount returns to your wallet. Common reasons and fixes:

• Bolt declined the number: like many platforms, it does not accept a virtual number for Bolt sign-up in every market. Try another country route if your test allows, or a later attempt.
• Slow delivery: timing depends on the service and the route, so let the window finish before cancelling.
• Repeated requests: tapping resend many times or re-ordering in a loop can trigger Bolt's own throttling. Space out attempts.
• Wrong market: a number from a country Bolt does not serve in your test scenario may never be accepted.

The guide on country routing for OTP covers choosing fallbacks.

When is a Dedicated Number the better fit?

A one-time number suits a single verification. If a Bolt account must sign in again weeks later, for instance a staging rider profile your QA team reuses, or an operations login that gets re-verified on new devices, the number needs to stay with you. Dedicated Numbers do that, but only in the United States and Canada, from $1.95/month, with inbound SMS in the dashboard and forwarded to your webhook as number.sms_received. Check that the account's Bolt market works with a US or Canadian number before relying on one. See virtual numbers for details.

Using Bolt numbers responsibly

Follow Bolt's terms of service in every market. Keep one account per real person or business, and use OTP Route only to test your own products or to operate legitimate accounts your organisation owns; creating throwaway rider profiles or farming promotions is not acceptable use. The OTP Route Acceptable Use Policy applies to every order, and Bolt is a trademark of its owner with no affiliation implied.

Frequently asked questions

Can I receive a Bolt OTP without a local SIM card?

Yes. Order a number for the bolt service in the right country, enter it in the app and read the code in your dashboard or via the API.

What is the Bolt service id in the API?

It is bolt. Combine it with a country id such as pl or ke when you call POST /api/v1/activations.

How much does a Bolt verification number cost?

From $0.20 per code. The exact amount depends on the country and comes back live from GET /api/v1/prices.

Does Bolt accept every virtual number?

No. Bolt may reject virtual numbers in some markets or flows, which is why an undelivered code is refunded automatically.

Which country should I pick for a Bolt test?

Use the country where the account will actually be used, so the sign-up rules, language and payment options match what real users see.

Can I keep the same number for future Bolt logins?

Not with a one-time activation. For repeat logins, a Dedicated Number in the US or Canada is the self-serve option.

Can I test the flow before paying?

Yes. Ask for sandbox mode on a development account to receive simulated numbers and codes without spending wallet funds.

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.