Receiving Hong Kong (+852) SMS OTPs for testing and operations

What makes +852 numbers simple to normalize?

Hong Kong uses a closed numbering plan: every subscriber number has eight digits, there are no area codes, and there is no trunk prefix to strip. The number a local user types is therefore the same eight digits that follow +852 in E.164. Mobile ranges commonly begin with 5, 6 or 9.

People usually write the eight digits as two groups of four, so your sign-up form should drop spaces and hyphens before validation. Store the canonical +852XXXXXXXX string, compare on that value, and format only at display time. Because the length is fixed, a simple length check catches most typos, but keep a proper phone library in the loop for range validation.

Which languages do Hong Kong verification texts use?

Chinese and English are both official, Cantonese is the everyday spoken language, and written Chinese here uses Traditional characters. A service may send its code in English or in Traditional Chinese depending on the account's locale, and Chinese-script messages travel as Unicode SMS.

Two practical consequences for QA. First, extract the code by matching the digit pattern rather than nearby words, so the parser works for both templates. Second, if your own product sends a localized message, check that the Traditional Chinese version renders correctly on the received side, not just in your template editor.

Why do teams run sign-up tests on a Hong Kong route?

Hong Kong is a regional base for many Asia-Pacific businesses, and its users often keep accounts on both international and mainland-facing apps. That mix makes it a useful market for checking localization, cross-border onboarding and support flows.

The current snapshot shows more than 3,600 services for Hong Kong. Frequently used ones include WhatsApp, WeChat, LINE, Signal, Alibaba, Telegram, Google (Gmail & YouTube), Facebook, Instagram, LinkedIn, Uber, Airbnb, Netflix, AliExpress and Amazon. Payment and wallet products test here too, since a broken phone step on a Hong Kong onboarding screen stops a customer before any transaction can happen. Live availability changes through the day, so read it at run time.

How does the Hong Kong OTP API flow run with country `hk`?

Authenticate against https://otproute.com/api/v1 with a Bearer key that starts with or_live_. An account can hold up to 10 keys and 5 webhook endpoints.

1. Read GET /api/v1/services and GET /api/v1/countries once per run to map names to ids.
2. Query GET /api/v1/prices?country=hk&service=<id> for the live price.
3. Send POST /api/v1/activations with {"service": "wechat", "country": "hk"}.
4. Submit the +852 number in the flow you are testing.
5. Pick up the code from the activation.sms_received event, or fall back to polling GET /api/v1/activations/{id} every few seconds.
6. On activation.expired or activation.cancelled, mark the test as no-code and move on.

Verify the X-OTPRoute-Signature header (HMAC-SHA256 over <t>.<raw body>) and reject stale timestamps. The integration guide walks through each call.

How can a non-developer get a Hong Kong verification number?

Open the OTP Gateway in the dashboard, pick Hong Kong and the service, check the displayed price and place the order. Copy the number into the app, then watch the activation card; the code appears there as soon as it is received. This is handy for support staff reproducing a customer report on the same route your CI uses.

What if the +852 code does not show up?

Give the activation its full 20 minutes. If no SMS arrives, or you cancel early, the charge returns to your wallet automatically, because you only pay when a code lands. Then:

• check whether the service refuses virtual numbers, which some do;
• try again later or through another service route;
• confirm the app received all eight digits after +852, since a form that inserts a stray leading zero breaks the number;
• avoid re-ordering in a tight loop, which tends to repeat the same outcome.

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

No self-serve long-term +852 number exists on OTP Route. Dedicated Numbers are offered only in the United States and Canada, from $1.95/month, and are described on the virtual numbers page. For a Hong Kong line, email [email protected]; whether one can be provided depends on local rules.

Everything else is pay as you go from a prepaid USD wallet, topped up by card or USDT/USDC, with a PDF invoice for each top-up. A sandbox mode with simulated numbers is available on request for development accounts. Follow each service's terms and the Acceptable Use Policy.

Frequently asked questions

Can I receive a Hong Kong SMS OTP without a local SIM card?

Yes. OTP Route issues a one-time +852 number for a chosen service, and the code is delivered to the dashboard and your webhook.

Do I need to remove a trunk prefix from Hong Kong numbers?

No. Hong Kong has no trunk prefix, so the eight local digits go straight after +852.

What is the API country id for Hong Kong?

Use hk in the prices query and the activation body.

Will the code arrive in Chinese or English?

Either can happen, depending on the service and the account's language settings. Parse the digits by pattern so both templates work.

What does a +852 number for testing cost?

From $0.20 per code; the live price per service comes from GET /api/v1/prices and is shown in the dashboard before ordering.

Can I get my money back if WeChat or another service sends nothing?

Yes. Any activation that receives no SMS inside 20 minutes, or that you cancel, is refunded to the wallet in full.

Is OTP routing to Hong Kong suitable for CI pipelines?

It is, provided you use webhooks or modest polling and handle expiry as a normal outcome. See the CI pipeline article.

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.