Anguilla (+1 264) verification codes: checklist, API steps and fixes

Pre-flight checklist: what should be ready before the first Anguilla order?

Run through this list once and the first live test usually goes cleanly:

• An API key. Create it in the Developer console; keys carry the or_live_ prefix and an account can hold up to 10, so give staging and CI their own.
• Funds in the wallet. A quick GET /api/v1/balance at the top of a suite fails the run early instead of halfway through.
• The right country id. Anguilla is ai in the API. That two-letter code is easy to confuse with an "AI" label elsewhere in a config file, so keep it in a named constant.
• The service id. Pull it from GET /api/v1/services rather than guessing a slug.
• A webhook endpoint (optional). Register it in the console, store its secret, and decide how the handler finds the waiting test.
• A phone field that accepts +1 outside the US. This is the item teams most often discover too late; the next section explains why.

If you want to wire everything up before spending anything, ask support to switch a development account to sandbox, which returns simulated numbers and codes.

Why does a +1 264 number trip up phone validation?

Anguilla sits inside the North American Numbering Plan, so its numbers share the +1 country code with the United States, Canada and a long list of Caribbean territories. What identifies the island is the area code 264: an Anguilla number is +1, then 264, then seven digits, ten digits after the plus-one in total. Within NANP the domestic trunk prefix is 1, which is why the same line may be written as 1-264-xxx-xxxx in local material.

That shared code produces a familiar set of bugs:

• forms that treat every +1 number as American and try to map it to a US state;
• country pickers that store "US" for anything starting with +1, which skews analytics and SMS policy lookups;
• validators that reject area codes they do not recognise.

Store the number in E.164 as +1264 followed by the seven-digit subscriber number, and derive the region from the full prefix with a maintained numbering library instead of from the country code alone. English is the official language, so verification texts on this route normally arrive in a service's English template, which keeps code extraction simple. Teams test here when they launch in the Eastern Caribbean, serve tourism and hospitality customers, or simply want proof that their NANP handling works beyond the fifty states.

Step by step: ordering an Anguilla number through the API

Every call goes to https://otproute.com/api/v1 with the key in a Bearer header.

1. Confirm the route with GET /api/v1/countries and cache the response for the day.
2. Ask for the live price: GET /api/v1/prices?country=ai&service=<id>. Prices and availability move during the day, so query them per run instead of hard-coding.
3. Create the activation with POST /api/v1/activations and the body {"service": "<id>", "country": "ai"}. The response holds an activation id and the +1 264 number.
4. Type the number into the sign-up or login screen of the product you are testing.
5. Wait for activation.sms_received on your webhook, or poll GET /api/v1/activations/{id} every few seconds; the 300 requests per minute limit leaves plenty of room.
6. If the test aborts, release the order with POST /api/v1/activations/{id}/cancel so the hold returns to the wallet.

The full request and response reference lives in the API docs.

Which services can receive codes on an Anguilla route?

The Anguilla route currently lists more than 600 services. Among the popular ones in today's snapshot are WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, X (Twitter), ChatGPT (OpenAI), Microsoft & Outlook, Amazon, Discord, LinkedIn, Uber and Airbnb. Travel and ride apps tend to matter to teams working with visitors to the island.

Treat that list as a starting point, not a promise: inventory on any OTP routing network shifts through the day, which is exactly why the prices endpoint reports live availability for each service and country pair.

How do non-developers run the same test from the dashboard?

Product managers and support staff do not need the API. After signing in, open the OTP Gateway, pick Anguilla and the service, check the price shown before ordering, and confirm. The number appears with a countdown; paste it into the app, and the code shows up on the same screen when the SMS arrives. A cancel button sits next to the order if plans change. For repeatable regression work, our QA testing guide shows how teams split manual checks from automated ones.

Troubleshooting: the Anguilla code didn't arrive

Work through these before opening a ticket:

• Let the window run. An activation stays open for 20 minutes. Ordering a second number a minute after the first only splits your attention.
• Check acceptance. Some services refuse virtual numbers or apply their own risk rules to new numbers. If the sign-up form rejects the number outright, cancel and choose a different route.
• Retry later or switch route. Availability on a small island route changes; trying again later, or testing the same flow on another country, often clears it.
• Avoid tight loops. Re-ordering in a loop burns rate limit and can make the target service more suspicious, not less.
• Check your webhook. Confirm the handler verifies X-OTPRoute-Signature and returns success; the HMAC verification guide covers constant-time comparison and timestamp checks.

Whatever the cause, a code that never arrives costs nothing: when the window closes empty, or when you cancel, the full amount goes back to the wallet automatically.

Long-term lines, wallet and invoices

Although Anguilla dials with +1, it is not part of the Dedicated Numbers product. Self-serve long-term lines are offered only in the United States and Canada, from $1.95/month, with inbound SMS, webhook forwarding and browser calling; see virtual numbers. If you need a lasting Anguilla line, email [email protected]; whether one can be arranged depends on local rules.

Billing is one prepaid USD wallet with no monthly fee and no plan to choose. Top up by card or with USDT/USDC, and a PDF invoice arrives by email for every top-up. Current pricing is on the pricing page. OTP Route is meant for testing and operating your own products and accounts, under each service's terms and our Acceptable Use Policy.

Frequently asked questions

Can I test my app's Anguilla sign-up flow without a local SIM?

Yes. Order a one-time +1 264 number from the OTP Gateway, enter it in your app, and read the code in the dashboard or through the API.

What country id does the OTP Route API use for Anguilla?

Anguilla is ai. Pass it as the country value in the prices and activations requests.

Is a +1 264 number treated as a US number?

It should not be. It shares the +1 code, but area code 264 belongs to Anguilla, so region detection must look at the full prefix.

How much does an Anguilla verification code cost?

Codes start from $0.20 per code. The exact amount depends on the service and is shown in the dashboard and returned by the prices endpoint before you order.

What happens if no SMS reaches the number?

Nothing is charged. If the 20-minute window closes without a code, or you cancel first, the full amount returns to your wallet.

Can I keep an Anguilla number for future logins?

Not self-serve. Long-term numbers are a US and Canada product; for anything else, email the team to ask.

Is there a way to wire up Anguilla tests before topping up the wallet?

Yes. On request, a development account can be moved to sandbox, which returns simulated numbers and codes for end-to-end tests.

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.