Verifying Algerian sign-ups: one-time +213 numbers, API calls and billing

One code or a number you keep: which product fits an Algerian test?

Before writing any integration code, settle one question: will the account you are verifying need this phone number again next month? The answer decides which OTP Route product you reach for.

• OTP Gateway covers a single verification event. You pick a service plus Algeria, receive one +213 number, read one code, and the activation closes. It suits sign-up tests, regression runs and pre-launch checks.
• Dedicated Virtual Numbers are long-term lines you hold while they renew, with inbound and outbound SMS plus calling from the browser. They are sold only for the United States and Canada, from $1.95/month.

No self-serve long-term number exists for Algeria. If an operations team genuinely needs a lasting +213 line, email [email protected] with the use case; anything beyond the one-time route depends on local rules and may not be possible. For most QA work the per-code route is the correct tool, and our note on temporary vs dedicated numbers covers the grey areas.

Which apps can an Algeria verification number be ordered for?

The live snapshot for Algeria lists more than 1,700 services. Those product teams ask about most include WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, Viber, imo, Signal, Microsoft & Outlook, LinkedIn, Uber and ChatGPT (OpenAI).

Routes open and close through the day, so read that list as orientation, not a promise. Ask the API for current availability right before each run and let your test harness skip a pairing that is unavailable instead of failing the whole suite.

What does the Algeria OTP API sequence look like in practice?

Everything lives under https://otproute.com/api/v1 and is authenticated with a Bearer key prefixed or_live_, generated in the Developer console. Algeria's country id is dz.

1. Fetch service ids with GET /api/v1/services and cache them instead of calling it for every test.
2. Query GET /api/v1/prices?country=dz&service=<id> for the present price and availability of that pairing.
3. Create the activation with POST /api/v1/activations and a body like {"service": "telegram", "country": "dz"}. Persist the returned activation id beside the +213 number.
4. Type that number into the sign-up screen of the app under test.
5. Take the code from your webhook as activation.sms_received, or poll GET /api/v1/activations/{id} at a modest interval.

Each webhook delivery carries X-OTPRoute-Signature: t=<unix>,v1=<hex>. Recompute HMAC-SHA256 over <t>.<raw body> using the endpoint secret, compare in constant time and drop stale timestamps. One account can hold up to 10 keys and 5 webhook endpoints, with a ceiling of 300 requests per minute. This SMS verification API is documented in full in the API docs.

Can a non-developer get a +213 code from the dashboard?

Yes. A product manager or support lead can do the same by hand: sign in, open the OTP Gateway, choose the service and Algeria, check the price displayed before ordering, and confirm. The number appears straight away; paste it into the app, and the code lands on that same screen once the SMS is received. If the check is abandoned halfway, cancel the activation and the amount goes back to the wallet. Teams mixing manual spot checks with automated suites usually keep both paths, as our QA testing page explains.

How should Algerian numbers be normalised, and what language do codes use?

Domestically, Algerian mobile numbers are dialed with a trunk 0 followed by nine digits. In international form that zero is dropped, so a local 0X XX XX XX XX becomes +213 X XX XX XX XX. Store the E.164 version (plus sign, 213, nine digits, no spaces) and format only at display time. A frequent bug is a form validator that accepts the local ten-digit entry but rejects the international one, or the reverse, so cover both in your test cases.

Arabic and Tamazight are the official languages, and French is widely used in business and administration. Depending on the service and the account locale, a code can arrive in Arabic, French or English. If your own product sends Arabic text, confirm that right-to-left layout and the digits render properly on the verification screen, and that your parser pulls the code out whatever script surrounds it.

Teams usually look at Algeria when launching across the Maghreb or serving French-speaking North African customers. Bilingual localisation QA is the typical reason to verify on a real +213 route instead of a mocked one.

What if the +213 code never shows up?

Each activation runs for 20 minutes. You only pay if the code arrives: when the window ends empty, or you cancel, the full amount returns to the wallet automatically. Some services refuse virtual numbers, which is exactly why that refund exists.

When nothing comes through:

• Let the window run instead of cancelling after a minute; delivery time depends on the service and the route.
• Retry later, or try another service route if the test allows it.
• Check whether the service accepts virtual numbers for this flow at all.
• Do not re-order in a tight loop; back off between attempts.

Our guide to reducing failed OTP deliveries goes deeper. Follow each service's terms; OTP Route's Acceptable Use Policy applies to every activation.

How do payment and sandbox testing work?

Billing runs through a single prepaid USD wallet, with no monthly fee and no plan to choose. Top up by card or with USDT/USDC stablecoins, and every top-up produces a PDF invoice by email. For integration work, a development account can be switched to sandbox on request; it returns simulated numbers and codes so the entire OTP routing flow, webhooks included, can be exercised without spending wallet funds. Current rates live on the pricing page, and you can open an account with a 6-digit email code or Google sign-in.

Frequently asked questions

Can I test my app's Algerian sign-up flow without a local SIM?

Yes. Order a +213 number for testing from the OTP Gateway, enter it in your app, and read the code in the dashboard or via the API. It costs from $0.20 per code and is refunded when no SMS arrives.

What is Algeria's country id in the OTP Route API?

It is dz. Pass it in the country field of POST /api/v1/activations and as the country query parameter on the prices endpoint.

Can I keep an Algerian number for repeat logins?

Not on a self-serve basis, because long-term lines are offered only in the US and Canada. You can email [email protected] to ask about Algeria, but the answer depends on local rules and may be no.

Should I strip the leading zero from Algerian numbers?

Yes, when converting to E.164: remove the domestic trunk 0 and prefix +213. Keep the stored value in that canonical shape and reformat only for display.

Am I charged if a service rejects the virtual number?

No. If no code reaches the number before the 20-minute window closes, the amount is credited back to your wallet automatically.

Do I need a webhook, or is polling enough?

Polling GET /api/v1/activations/{id} is fine for small suites. Webhooks scale better once many activations run in parallel, and they spare you a polling loop.

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.