Getting +670 verification codes for Timor-Leste without a local SIM

Why is a +670 number hard to come by for a remote team?

Timor-Leste is a small market, and few engineering teams have a colleague in Dili who can receive a code on demand. Yet the need is real: development programmes, NGOs, mobile-money and telecom projects, and apps aimed at Portuguese-speaking countries all run into the same blocker when they test a phone step for Timorese users. Shipping a SIM halfway around the world for one regression suite is slow and fragile.

A routed verification number removes the courier from the plan. Your test requests a +670 number, the code lands in your system, and the run finishes. Operations teams use the same flow to verify a business profile tied to their Timor-Leste office without exposing a staff member's personal phone. The operations teams page explains that use in more detail.

What does a Timorese phone number look like?

The country code is +670 and there is no trunk prefix, so local and international forms differ only by that code. Mobile numbers are eight digits and generally begin with 7. Store them in E.164 as +670 followed by the eight digits, with no spaces, and normalise anything a user types by stripping separators first.

Tetum and Portuguese are the official languages, while Indonesian and English are also widely used. International apps usually send verification texts in the language the account is set to, so your parser should look for the digits rather than an expected sentence.

Which services currently reach Timor-Leste numbers?

The current snapshot shows around 1,000 services on the Timor-Leste route. Popular ones include Telegram, Facebook, Signal, Google (Gmail & YouTube), WhatsApp, Instagram, TikTok, Viber, Microsoft & Outlook, LinkedIn, Discord and ChatGPT (OpenAI).

Smaller routes can change faster than large ones, so check the live list (GET /api/v1/countries and GET /api/v1/services, or the dashboard) before you plan a test around one service. If a particular app is missing for +670, a nearby route such as Indonesia can help confirm that your own flow works while you wait.

How does a test fetch a +670 code through the API?

Point your client at https://otproute.com/api/v1 with a Bearer key from the Developer console (prefix or_live_). The country id for Timor-Leste is tl.

• Price check: GET /api/v1/prices?country=tl&service=telegram.
• Order: POST /api/v1/activations with {"service": "telegram", "country": "tl"}; store the activation id it returns.
• Read: poll GET /api/v1/activations/{id}, or receive activation.sms_received at a webhook endpoint.
• Abort: POST /api/v1/activations/{id}/cancel if the test stops early.

Every webhook is signed in X-OTPRoute-Signature as t=<unix>,v1=<hex>. Verify the HMAC-SHA256 of <t>.<raw body> with your endpoint secret and discard old timestamps. The OTP API integration guide walks through a full client.

Can I order one from the dashboard instead?

Yes. Open the OTP Gateway, select Timor-Leste and the service, check the price, and order. Enter the number in the app you are verifying, and the code shows up in the activation card when it is received. No API key is involved.

This path suits a programme officer or a field coordinator who needs to confirm one account for a local partner, or a product manager spot-checking the Tetum or Portuguese copy of an onboarding screen before release. If the session ends before the code arrives, the activation simply runs out and the funds go back to the wallet.

What if the Timor-Leste code is slow or missing?

The activation window is 20 minutes. If it expires with no SMS, or you cancel, the full amount is refunded automatically, so a failed attempt costs nothing.

1. Wait for the window to finish before deciding the route is down.
2. Check whether the service accepts virtual numbers at all; some refuse them.
3. Try later, or test with a different service to rule out your own integration.
4. In automation, add a delay between attempts rather than ordering in a tight loop.

Is there a long-term Timorese line, and how do I pay?

No self-serve long-term number exists for Timor-Leste. Dedicated Numbers are limited to the United States and Canada, from $1.95/month, and you can compare them on the temporary vs dedicated numbers explainer. For a lasting +670 line, email [email protected]; whether one can be arranged depends on local rules.

Payment is pay as you go from a prepaid USD wallet, topped up by card or USDT/USDC, with a PDF invoice for every top-up and no monthly fee. A sandbox mode with simulated numbers and codes is available on request for development accounts. Each service's terms and OTP Route's Acceptable Use Policy apply.

Frequently asked questions

Can I test a Timor-Leste sign-up flow from outside the country?

Yes. Order a +670 number from the OTP Gateway, enter it in your app, and read the code from the dashboard or API.

Which country id does Timor-Leste use in the API?

Use tl in both the price lookup and the activation request.

How long are Timorese mobile numbers?

Mobile numbers are eight digits after +670 and usually start with 7. There is no trunk prefix.

Is the price fixed for every service?

No. It starts from $0.20 per code and depends on the service; the live figure comes from GET /api/v1/prices.

Do I lose money if a +670 code never arrives?

No. Expired and cancelled activations are refunded to the wallet in full.

Can I run my CI pipeline against +670 numbers without spending money?

Ask for a sandbox on a development account. It returns simulated numbers and codes, so your integration can be exercised end to end before you switch to real activations.

Can I keep a Timor-Leste number for future logins?

Not self-serve. OTP Gateway numbers are single-use, and long-term Dedicated Numbers are offered only in the US and Canada.

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.