English
Receiving a Battle.net SMS Code on a Test Number, Step by Step
A team receives a Battle.net verification code with OTP Route by ordering an OTP Gateway number for service battle_net in the country that matches the account, entering it at the phone step, and reading the SMS in the dashboard or from a webhook. Each activation costs from $0.20 per code and is refunded in full if no code arrives within 20 minutes.
The situation: a studio or esports team needs a Battle.net phone number it controls
Picture a QA lead at a company that builds companion tools, overlays or tournament software around Blizzard games. The team runs official company accounts for testing and broadcast, and nobody wants an engineer's personal mobile number attached to them. Another common case is an esports organization whose operations staff manage shared team accounts and need verification to land somewhere the whole team can see.
Battle.net uses a phone number for several things: confirming the person behind an account, sending codes when sensitive details change, supporting account recovery, and acting as a security layer alongside the Blizzard Authenticator app. Some Blizzard titles have also asked for a phone number on the account before play. A Battle.net SMS verification for testing therefore touches flows your team may need to reproduce more than once.
Checklist before you order a virtual number for Battle.net
- Pick the right product. One-time checks suit the OTP Gateway. An account that will keep its phone attached and must pass future security prompts belongs on a Dedicated Number (see below).
- Match the country. The country on a Battle.net account is chosen at creation and is generally not something a user can switch later, so order the number from the same market as the account.
- Prepare credentials. A Bearer key from the Developer console (prefix
or_live_) and, ideally, a webhook endpoint with its secret. - Fund the wallet. Card or USDT/USDC into the prepaid USD wallet; there is no monthly plan.
- Dry run in sandbox. Support can switch a development account to sandbox so the integration receives simulated numbers and codes without spending.
The QA testing page describes how teams organize this kind of reusable test data.
Which countries can receive a Battle.net OTP?
The battle_net route currently spans 197 countries. Among them are the United States, Canada, the United Kingdom, Germany, France, Spain, Poland, Sweden, South Korea, Taiwan, Japan, Singapore, the Philippines, Australia, Brazil, Mexico, Turkey and South Africa. Blizzard serves players through regional game hubs, so the country you pick should reflect the region and storefront your test case is about, not whichever route happens to be cheapest. Live availability per country comes from GET /api/v1/prices.
How does the Battle.net verification code API flow work?
Base URL https://otproute.com/api/v1, Bearer authentication, 300 requests per minute.
- Confirm price and availability:
GET /api/v1/prices?country=<id>&service=battle_net, using the country id fromGET /api/v1/countries. - Create the activation with
POST /api/v1/activationsand a body like{"service": "battle_net", "country": "us"}. - Enter the returned number in Battle.net and request the code.
- Handle
activation.sms_receivedon your webhook. VerifyX-OTPRoute-Signatureby computing HMAC-SHA256 over<t>.<raw body>with the endpoint secret, and refuse old timestamps. - Make the handler idempotent: key processing on the activation id so a retried delivery does not submit the same code twice.
- No public endpoint? Poll
GET /api/v1/activations/{id}instead, and treat anactivation.expiredoractivation.cancelledevent as the end of that test run.
The webhook capture guide covers queueing and retries in detail.
What do non-developers do in the dashboard?
Open the OTP Gateway, choose Battle.net and the account's country, look at the price shown, and confirm. Type the number into the Battle.net phone field, request the SMS, and keep the activation page open; the code appears there when delivered. The same 20-minute window and automatic refund apply.
Why might a Battle.net code fail to arrive?
Blizzard may refuse virtual or prepaid-style numbers for some security features, and that policy can change without notice. If the code never comes, the full amount returns to your wallet once the window ends or you cancel. Then:
- let the full window elapse, since delivery timing depends on the service and route;
- retry later, or with another country that still matches the account;
- avoid rapid cancel-and-reorder loops, which waste your rate limit;
- if the number is rejected outright, treat that as a policy answer rather than something to work around.
The failed delivery checklist lists more signals to log.
When is a Dedicated Number the better Battle.net phone number?
A one-code number is gone after its window, so it is a poor fit for any account that will need to receive a security code again. For a long-lived company account, a Dedicated Number in the United States or Canada, from $1.95/month, keeps the same line while it renews from the wallet and forwards inbound SMS to the dashboard and to your webhook as number.sms_received.
Whatever you choose, follow Blizzard's terms: one account per real person or business, no extra accounts and no attempts to get around a suspension. OTP Route exists for testing and operating your own legitimate accounts and products, and its Acceptable Use Policy applies. Battle.net is a trademark of its owner, and OTP Route has no affiliation with it.
Frequently asked questions
Can I receive a Battle.net OTP without using my personal phone?
Yes. Order an OTP Gateway number for battle_net, enter it in Battle.net, and read the code in the dashboard or via webhook. It costs from $0.20 per code, charged only on delivery.
Does Battle.net accept every virtual number?
No. Blizzard may decline virtual or prepaid numbers for some features, which is why undelivered activations are refunded automatically.
Which country should I choose for a Battle.net test account?
Use the same country as the account. A Battle.net account's country is set when it is created, so a mismatched number can lead to confusing results.
What is the service id for Battle.net in the API?
The service id is battle_net. Combine it with a country id in POST /api/v1/activations.
What keeps a Battle.net webhook handler from acting on one code twice?
Store the activation id when you first handle activation.sms_received and ignore any later delivery carrying the same id, after verifying the signature.
Should a company account that needs codes later use a temporary activation?
No. For repeat security prompts, a US or Canada Dedicated Number from $1.95/month keeps the same line while it renews.
How many countries does the Battle.net route cover?
197 countries at the latest snapshot. Availability shifts during the day, so read live prices from the API before ordering.
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.