Chilean verification codes for QA and launch teams, routed by API

Gateway number or Dedicated Number: which one does a Chilean test need?

The choice turns on a single question: will anyone need a code on this exact +56 number again? For most Chilean work, such as a registration test, a one-off onboarding check or confirming a business profile, the answer is no, and the OTP Gateway fits. You get one number, it receives one code, and the job is finished.

A Chilean line that stays with you is a different product, and it is not one we sell self-serve. Dedicated Numbers from OTP Route exist only for the United States and Canada, from $1.95/month. If your team truly needs a long-lived +56 line, email [email protected] and describe the use case; whether anything can be arranged depends on local rules, so plan as if the answer may be no.

• Use the OTP Gateway when the code is needed once: sign-up regression, a smoke test before a Chilean release, a single account confirmation.
• Use a US or Canadian Dedicated Number when a shared staging login must keep receiving codes and the account does not need a Chilean identity.

The article on temporary vs dedicated numbers lays out the trade-offs in more depth.

How does the Chile OTP API work from order to code?

The SMS verification API is plain REST under https://otproute.com/api/v1, authenticated with a Bearer key beginning or_live_ that you create in the Developer console. Chile's country id is cl.

1. Call GET /api/v1/services and cache the service ids your tests use, for example whatsapp or uber.
2. Read the current figure from GET /api/v1/prices?country=cl&service=<id> rather than hard-coding a cost.
3. Place the order with POST /api/v1/activations and a body such as {"service": "whatsapp", "country": "cl"}. The response carries the +56 number and an activation id.
4. Type that number into the flow under test and trigger the SMS.
5. Poll GET /api/v1/activations/{id}, or let the activation.sms_received webhook tell you.
6. If a run is abandoned, send POST /api/v1/activations/{id}/cancel so the wallet is credited straight away.

Webhook deliveries are signed. The X-OTPRoute-Signature header holds t=<unix>,v1=<hex>, an HMAC-SHA256 of <t>.<raw body> keyed with the endpoint secret. Recompute it over the untouched request bytes, compare in constant time, discard stale timestamps, and treat the activation id as the idempotency key so a repeated event changes nothing. Each account gets up to 10 API keys, 5 webhook endpoints and 300 requests per minute; the OTP API integration guide adds retry and error handling to this loop.

Which apps can send codes to a +56 number for testing?

The Chilean route currently reaches more than 1,800 services. The ones QA teams reach for most often include WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, Uber, Microsoft & Outlook, Amazon, LinkedIn, ChatGPT (OpenAI), Discord and Netflix.

Inventory moves through the day, so treat any list, this one included, as a snapshot. Before a scheduled job, ask GET /api/v1/countries and the prices endpoint what is live for cl and skip gracefully when a pairing is missing, instead of discovering the gap halfway through a test suite.

How should +56 numbers be stored and validated?

Chilean mobile numbers are nine digits after the +56 country code and begin with 9, so a full mobile in E.164 reads +569 followed by eight more digits. Current Chilean numbers are written at home with the same nine digits that follow +56, which keeps normalization short.

Users will still type the number three different ways: with spaces and a plus, as 56 plus the national digits with no plus, or as the nine local digits alone. Store one canonical E.164 string, keep the raw input next to it for support tickets, and add test cases for all three shapes. Rejecting an eight-digit entry at the form stage saves you an SMS that was never going to land.

Why do product teams verify Chilean sign-up flows?

Chile is a frequent early stop for products expanding across Latin America, and its users expect Spanish copy written for the region rather than text localized for Spain. Codes sent to +56 numbers usually arrive in Spanish, although many apps follow the account's locale, so check that your parser pulls the digits out regardless of the wording around them.

Other reasons teams run Chilean checks: confirming the phone field defaults to +56 for local visitors, proving the full route works for Chilean numbers specifically, and letting support or operations staff confirm business accounts without lending a personal SIM. Our QA testing page shows how teams fold this into release checklists.

What if a Chilean code never shows up?

Every activation stays open for 20 minutes. You pay only if a code arrives; when the window closes empty, or you cancel first, the full amount returns to the wallet automatically. If a +56 number stays quiet:

• Let the window run its course before marking the test failed, because some senders are slow.
• Find out whether that particular app takes virtual numbers in the first place. Some refuse them by policy, which is exactly why the refund rule exists.
• Retry later, or switch to another service route for the same scenario.
• Space your retries out; firing a fresh order every few seconds only burns through numbers.

Further troubleshooting ideas live in our post on reducing failed OTP deliveries.

How do billing and sandbox testing work?

OTP Route uses one prepaid USD wallet: pay as you go, no monthly fee and no plan to pick. Funding works by card or with USDT/USDC stablecoins, and accounting receives a PDF invoice by email for each top-up.

While you build, ask for your development account to be moved to sandbox. It returns simulated numbers and codes, so the whole Chile flow can be exercised without touching wallet funds. Colleagues who never open a terminal can use the dashboard instead: select Chile, select the service, confirm the price shown, copy the number and watch the code appear.

Use it for your own products and accounts only, respect each service's terms, and keep in mind that OTP Route's Acceptable Use Policy applies. You can create an account in a couple of minutes.

Frequently asked questions

Can I test my app's Chilean sign-up without a local SIM card?

Yes. Order a +56 number from the OTP Gateway, enter it in your sign-up form and read the code in the dashboard or through the API. Each number covers one code.

What country id does the API expect for Chile?

Use cl, for example GET /api/v1/prices?country=cl&service=telegram.

How much does a +56 number for testing cost?

From $0.20 per code; the exact amount depends on the service and is returned live by the API. You are charged only when a code arrives.

Can I keep a Chilean number so the account can log in again next quarter?

Not self-serve. Dedicated Numbers are a US and Canada product from $1.95/month; for a +56 line, email [email protected], and availability depends on local rules.

Which language do Chilean verification texts use?

Usually Spanish, though many apps send in the account's chosen language. Parse the digits rather than matching fixed wording.

Is polling or a webhook better for Chilean test runs?

Polling is fine for a single manual check. Once several runs happen in parallel, a signed webhook keyed on the activation id is easier to scale.

Can our finance team pay with stablecoins?

Yes. The wallet accepts cards and USDT/USDC, and each top-up comes with a PDF invoice.

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.