Receiving Singapore SMS codes on +65 numbers: what teams ask first

Why do product teams test against Singapore numbers?

Singapore is a common base for regional headquarters, so plenty of Southeast Asian rollouts start here before moving to larger neighboring markets. Business runs mostly in English, while Malay, Mandarin and Tamil are also official languages, which makes it a compact place to check multilingual sign-up copy. QA teams use a +65 route to confirm that their own verification SMS reaches a Singaporean subscriber and that the login screen behaves on a local number; growth teams use it when launching SaaS onboarding for the region.

There is a practical angle too. Regional e-commerce and ride-hailing apps are heavily used here, so marketplace and delivery teams often need a Singapore case in their regression suite next to Malaysia, Indonesia or the Philippines. Having that case run against a real +65 number catches problems a mocked SMS provider never shows, such as a sender that formats the code differently for this market or a screen that rejects an eight-digit local number.

Which services can send codes on the +65 route?

More than 1,600 services are available for Singapore right now. Popular ones in the current snapshot include Shopee, Lazada, WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, LINE, WeChat, Microsoft & Outlook, Amazon, Airbnb and LinkedIn. Stock changes hour by hour, so let your code read live availability rather than hard-coding a list.

For e-commerce teams the two marketplace entries are the interesting ones: a seller tool or storefront integration that relies on a Shopee or Lazada login can be exercised on a Singapore number before it is rolled out to neighboring markets. Messaging apps like LINE and WeChat matter for products that serve visitors and residents from elsewhere in Asia.

What is the API call sequence for `sg`?

1. GET /api/v1/prices?country=sg&service=shopee returns the price and whether the pair can be ordered.
2. POST /api/v1/activations with {"service": "shopee", "country": "sg"} reserves the number and returns an activation id.
3. Your test triggers the SMS, then waits for activation.sms_received on a webhook signed with X-OTPRoute-Signature (HMAC-SHA256 of "<t>.<raw body>", timestamps checked), or polls GET /api/v1/activations/{id}.
4. POST /api/v1/activations/{id}/cancel closes an activation you no longer need, and the money goes straight back to the wallet.

Keys use the or_live_ prefix, and the developer hub explains limits: 10 keys, 5 webhook endpoints and 300 requests per minute per account.

Two habits keep a Singapore suite stable. First, write the activation id to your test log before triggering the SMS, so a failed run can be traced afterwards. Second, treat a webhook delivery as possibly repeated and process each activation id only once; the walkthrough on verifying OTP webhooks with HMAC shows a compact way to do both checks.

How does a non-developer do the same thing?

In the dashboard, open the OTP Gateway, pick Singapore and the service, check the displayed price and confirm. Copy the +65 number into the app, request the code, and watch it appear in the activation row. That is all; there is nothing to install. Support and operations staff often use this path when a business profile registered to a Singapore office has to be confirmed once, without putting an employee's personal mobile on the account.

How should +65 numbers be stored?

Singapore numbers have eight digits and no trunk prefix, and mobile numbers begin with 8 or 9. In E.164 that becomes +65 followed by the eight digits. Normalize input by removing spaces and a leading 00, and keep the stored value free of formatting so lookups match. A common bug in regional apps is reusing a validator from a market with a domestic zero, which then rejects perfectly valid +65 entries; one automated test with a Singapore number prevents it.

Can I keep a Singapore number long term?

Not on a self-serve basis. Long-term lines (Dedicated Numbers, from $1.95/month) are sold only for the United States and Canada. Teams that need a permanent +65 line can email [email protected] to ask; availability depends on local regulation and is not assured. The temporary versus dedicated numbers article helps decide which model your test case needs.

Billing is the same for every route: a prepaid USD wallet, card or USDT/USDC top-ups, and a PDF invoice by email after each one. There is no monthly fee, and current rates are listed on the pricing page.

Frequently asked questions

Can I verify a Singapore account on my product without a Singapore SIM card?

Yes. Order a +65 number on the OTP Gateway, send the code from your product and read it in the dashboard or through the API.

What is the Singapore country id in the OTP Route API?

It is sg, used with a service id in the prices and activations endpoints.

How long does a +65 activation wait for the SMS?

Twenty minutes. A run that times out or is cancelled refunds the full amount to the wallet automatically.

What should I do if the Singapore code never arrives?

Let the window finish, then retry later or try another route. Check that the service accepts virtual numbers, and avoid ordering again in a tight loop, which tends to trigger the sender's rate limits.

Does OTP Route charge a monthly fee for Singapore numbers?

No. You pay as you go from a prepaid USD wallet funded by card or USDT/USDC, with a PDF invoice by email for each top-up.

In which language will Singapore verification texts arrive?

Usually English, since that is the main business language, but it depends on the sending service and the account's language setting.

Can I run Singapore OTP tests in CI without spending funds?

Ask for sandbox mode on a development account. It returns simulated numbers and codes so the whole integration can run end to end.

Is OTP Route allowed for creating many marketplace accounts?

No. It is meant for testing your own product and running legitimate business accounts, under each service's terms and the OTP Route Acceptable Use Policy.

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.