Testing Brunei (+673) sign-up and login codes without a local SIM

Calling code +673OTP Gateway from $0.20 per codeDedicated numbers: US & Canada onlyAPI id: bn
Quick answer

Yes, you can receive Brunei (+673) verification codes with OTP Route: the OTP Gateway issues a one-time Bruneian number for the service you choose and hands the code to your dashboard, a REST polling call or a signed webhook. Prices start at $0.20 per code, and if nothing arrives inside the 20-minute window the charge goes back to your wallet.

What makes Brunei its own case for verification testing?

Brunei is a small, highly connected sultanate on the island of Borneo, and its users move between the same apps their neighbors in Malaysia and Indonesia rely on. That overlap tempts teams to treat it as an afterthought, yet a Bruneian phone number behaves differently in forms and validators than a Malaysian one, so it deserves its own test cases.

Malay is the official language and English is common in business and government, so an SMS code from a regional app may arrive in either, depending on the locale the account was set up with. Teams typically reach for a Brunei route when they:

  • add Brunei to an ASEAN launch and need proof that registration works end to end;
  • run localisation QA on Malay message templates and in-app strings;
  • operate a regional business account and want staff to keep personal numbers off it.

How should a +673 number be stored and normalised?

Bruneian numbers use a closed seven-digit plan with no trunk prefix, so there is no leading zero to strip. The E.164 form is simply +673 followed by the seven national digits, ten digits in all once the country code is counted.

That short length is where bugs hide. A phone field tuned for Malaysia or Indonesia often enforces a minimum length that silently rejects a valid Bruneian entry. Good habits for this route:

  • Store numbers as strings in E.164 with the plus sign, never as integers.
  • Accept 673 typed without the plus and rewrite it on save.
  • Strip spaces and hyphens before validation, then check the length per country rather than with one global rule.

A one-time +673 number for testing is the quickest way to confirm your validator, your SMS template and your login screen all agree.

Which apps can be verified on a Brunei route today?

The live snapshot for Brunei lists more than 1,400 services. The ones teams ask about most include WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, WeChat, LINE, Microsoft & Outlook, Discord, ChatGPT (OpenAI), and the regional marketplaces Shopee, Lazada and Tokopedia.

Inventory shifts through the day, so treat any list as a starting point and ask the API before each run. The price for a given pair is returned live and shown in the dashboard before you confirm an order.

What does the Brunei OTP API sequence look like?

All calls go to https://otproute.com/api/v1 with a Bearer key starting or_live_, created in the Developer console. An account can hold up to 10 keys, which makes it easy to give CI, staging and a support tool separate credentials.

  1. Read GET /api/v1/services and GET /api/v1/countries once and cache them; Brunei's country id is bn.
  2. Query GET /api/v1/prices?country=bn&service=<id> to confirm availability and the current price.
  3. Create the order with POST /api/v1/activations and a body such as {"service": "shopee", "country": "bn"}.
  4. Type the returned +673 number into the flow under test.
  5. Receive the code through the activation.sms_received webhook or by polling GET /api/v1/activations/{id}.

Webhook deliveries carry X-OTPRoute-Signature: t=<unix>,v1=<hex>. Recompute HMAC-SHA256 over <t>.<raw body> with the endpoint secret, compare in constant time and drop stale timestamps; the HMAC guide walks through it. The limit of 300 requests per minute leaves room for polling across parallel jobs, and full schemas live in the API docs.

Can a non-developer order a Bruneian number from the dashboard?

Yes. Operations staff and agency account managers often prefer clicking to scripting:

  1. Sign in and open the OTP Gateway.
  2. Choose Brunei as the country and pick the service.
  3. Check the price shown, then confirm.
  4. Copy the +673 number into the app you are verifying.
  5. Watch the activation; the code appears on the same screen once it lands.

The same activation also fires your webhooks, so a developer and a support lead can follow one order from two places.

What should you do when the +673 code never shows up?

Each activation stays open for 20 minutes. If no SMS arrives in that time, or you cancel with POST /api/v1/activations/{id}/cancel, the full amount returns to your wallet automatically; you are only billed when a code is actually delivered.

If a code is missing, let the window run first, since some services send late. Then try again a little later or order the same service through another route. Confirm the target app accepts virtual numbers at all, because some refuse them, and resist re-ordering in a tight loop, which tends to trigger the sender's own rate limits. More patterns are in our note on reducing failed OTP deliveries. Always follow each service's terms; OTP Route's Acceptable Use Policy applies to every order.

Is there a long-term Brunei line, and how does billing work?

There is no self-serve long-term number for Brunei. Dedicated lines that you keep while they renew are a US and Canada product from $1.95/month, covered on the virtual numbers page. If your team truly needs an ongoing Bruneian line, email [email protected]; whether one can be arranged depends on local rules and is not promised.

Spending on +673 activations comes out of a single prepaid USD wallet, pay as you go, without a subscription or plan tier. Brunei projects draw on it like any other route: fund it by card, USDT or USDC, and keep the PDF invoice emailed after each top-up for your records. For integration work, a development account can be switched to sandbox on request so your QA pipeline receives simulated numbers and codes without touching wallet funds.

Frequently asked questions

Can I check my app's Brunei sign-up flow without buying a local SIM?

Yes. Order a +673 number from the OTP Gateway for the service you are testing and read the code in the dashboard or through the API.

What is the OTP Route country id for Brunei?

It is bn. Pass bn as the country in the prices query and in your activation request body.

Do Bruneian phone numbers have a leading zero to remove?

No. Brunei has no trunk prefix, so the E.164 form is just +673 plus seven digits.

Will the verification message be in Malay or English?

That depends on the app and the account locale. Regional apps commonly send English, and some send Malay when the account is set up that way.

Am I charged if the Shopee or WhatsApp code does not arrive?

No. If no SMS reaches the number within 20 minutes, or you cancel, the full amount goes back to your wallet.

How many services does the Brunei route support?

The current snapshot shows more than 1,400. Call GET /api/v1/services or check the dashboard for live availability.

Can I keep a Bruneian number for future logins?

Not on a self-serve basis. Long-term dedicated numbers are only offered in the US and Canada, and you can email support to ask about Brunei.

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.

Route your first OTP in minutes

Create a free account, top up your USD wallet and order a number from the dashboard or the API. No monthly fee.