English
Testing +236 sign-up flows when nobody on the team holds a Central African SIM
Yes, you can receive Central African Republic (+236) verification codes with OTP Route: the OTP Gateway hands you a one-time +236 number, and the SMS code appears in the dashboard and reaches your backend through REST polling or a signed webhook. Pricing starts from $0.20 per code, and if no message lands within the 20-minute window the charge returns to your wallet.
Why is a +236 verification step so hard to reproduce from abroad?
The usual situation looks like this: a product ships to francophone Central Africa, someone files a bug saying the one-time code never showed up for a user in Bangui, and the engineer assigned to it has no way to put a Central African number into the form. Roaming SIMs are slow to obtain, colleagues on the ground are busy with real work, and emulators cannot produce a genuine carrier SMS.
An OTP routing service such as OTP Route closes that gap, and its Central African Republic OTP API is the same one used for every other country. Instead of shipping hardware around, you ask for a +236 line through an API call, type it into your own sign-up screen, and read the code back programmatically. The same request works in a laptop session, a nightly regression job or a support engineer's browser tab, which makes a hard-to-reach market behave like any other row in your test matrix.
Which services can receive Central African Republic SMS codes today?
The live snapshot for cf lists more than 900 services. Popular routes include WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, Viber, imo, Signal, Microsoft & Outlook, LinkedIn, ChatGPT (OpenAI) and Uber.
Availability shifts during the day as our carrier partners rotate inventory, so treat any list on a web page as a starting point rather than a promise. Before each run, ask GET /api/v1/prices?country=cf&service=<id> for the current price and whether the route is open. Some apps in the catalogue also decline virtual lines entirely; that is a decision made by the app, not by the network, and it is exactly why unanswered orders are refunded.
How does a backend request a +236 number for testing?
Everything lives under https://otproute.com/api/v1 and authenticates with a Bearer key prefixed or_live_, issued in the Developer console. A minimal SMS verification API session goes like this:
- Look up identifiers once with
GET /api/v1/servicesandGET /api/v1/countries; the Central African Republic iscf. - Confirm price and availability with
GET /api/v1/prices. - Create the order using
POST /api/v1/activationsand a body like{"service": "viber", "country": "cf"}. - Submit the returned +236 number to the screen under test.
- Receive the code via the
activation.sms_receivedwebhook, or pollGET /api/v1/activations/{id}every few seconds. - If the test aborts, release the line with
POST /api/v1/activations/{id}/cancel.
Webhook calls carry X-OTPRoute-Signature: t=<unix>,v1=<hex>. Your receiver should rebuild the HMAC-SHA256 of <t>.<raw body> using that endpoint's secret, match it against v1 in constant time and discard any delivery with an aged timestamp. The webhook capture guide walks through a full handler, and the reference lives in the API docs.
What should we know about Central African phone numbers and message language?
Numbers in the Central African Republic follow a closed eight-digit plan with no trunk prefix, so the domestic and international forms differ only by the country code. Store every value in E.164, for example +236 followed by the eight local digits, and strip spaces or dashes on input. Validation that insists on a leading zero, or on ten digits, will quietly reject real users.
French and Sango are the official languages. Most international apps send verification text in French or English depending on the account's locale, so make your parser look for the digits rather than a specific sentence. Teams typically test here when they expand a West or Central African rollout, run NGO and field-operations tooling, or support customers with family in the region.
Can a non-developer get a Central African Republic verification number?
Yes. Product managers, support leads and agency staff can do the whole thing from the browser:
- Create an account with an email code or Google sign-in, and turn on TOTP two-factor.
- Open the OTP Gateway, choose the service and pick Central African Republic.
- Check the live price shown before ordering, then confirm.
- Paste the +236 number into the app and wait for the code to appear on screen.
The activation stays open for 20 minutes. You pay only if a code arrives; cancel or let the window close and the full amount goes back to the wallet.
What if the code never shows up on the +236 line?
A silent number usually means the app throttled the request, refused a virtual line, or the route was busy. Work through it calmly:
- Let the window run its full course before deciding it failed; some senders queue messages.
- Cancel and try again later, or switch to another route for the same service if one is offered.
- Check whether the service is known to reject virtual numbers; if it is, no retry will help.
- Avoid re-ordering in a tight loop. Repeated attempts can trigger rate limits on the app side and on ours (300 requests per minute per account).
More patterns are in reducing failed OTP deliveries.
Is there a long-term +236 line, and how is usage billed?
No. Self-serve Dedicated Numbers exist only in the United States and Canada, from $1.95/month, so there is no permanent Central African line to buy in the dashboard. If a project truly needs one, email [email protected]; whether it can be arranged depends on local rules and is not something we can promise.
Billing for the OTP Gateway runs from one prepaid USD wallet with no monthly fee. Funding works by card or with USDT/USDC stablecoins, and each top-up triggers an emailed PDF invoice. Developers who want to rehearse an integration without spending can ask for sandbox mode, which returns simulated numbers and codes. Full rates are on the pricing page. Please follow each app's terms; OTP Route's Acceptable Use Policy covers every order.
Frequently asked questions
How do I receive Central African Republic SMS OTP codes without a local SIM?
Yes. Order a +236 number from the OTP Gateway, enter it in your app and read the code from the dashboard, a webhook or the activations endpoint.
What is the country id for the Central African Republic in the API?
It is cf. Use it in the prices query and in the activation body.
How much does a +236 number for testing cost?
Codes start from $0.20 each, and the exact figure depends on the service. The current figure for a +236 route is visible in the dashboard and in the prices endpoint before ordering.
Is a +236 order charged if the verification text fails to land?
No. If no message arrives during the 20-minute window, or you cancel first, the whole amount is credited back to your wallet automatically.
Should I store Central African numbers with a leading zero?
No. The plan has no trunk prefix, so keep the E.164 form with +236 and the eight local digits.
Can I keep the same +236 number for later logins?
Not through self-serve. Each OTP Gateway number covers one code, and long-term lines are a US and Canada product; you can email support to ask about other options.
Is there a way to test the integration without paying?
Yes. On request a development account can switch to sandbox, which simulates numbers and codes 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.