WhatsApp API & Developers

WhatsApp API Phone Number Requirements: What Qualifies

The number is the one part of a WhatsApp API project you can't easily change later. It goes on your website, your packaging and your ads, and customers save it. Yet it is usually picked in a hurry during signup: someone types the office landline, the verification call hits the reception menu, and the project stalls for a week.

This guide sets out the WhatsApp API phone number requirements as Meta documents them in October 2026: which numbers qualify, which number types verify reliably, what to do with toll-free and IVR lines, how verification works by API, and how many numbers a business can register. At the end there's practical advice on choosing a number you will still be happy with in five years.

The hard rules

Meta's eligibility list for a Cloud API number is short. The number must:

  1. Be owned by you. Not borrowed from an employee, and not a number you could lose to someone else.
  2. Have a country and area code. Short codes are not supported.
  3. Be able to receive a voice call or an SMS, for the ownership code.
  4. Not be in use with WhatsApp. A number active on WhatsApp Messenger or the WhatsApp Business app has to have that account deleted first. The one exception is coexistence, where a Business app number connects to the API through a partner without deletion.

Meta also lists "scaled capabilities" as a requirement, linking to its Help Center rather than defining it in the developer docs, so ask your provider if a number is refused for no obvious reason. Two more conditions trip people up. A number that is banned on WhatsApp must be unbanned through WhatsApp's appeal process before it can be registered. And a registered number can still make calls and send texts as normal; it just can't be used in the WhatsApp apps at the same time.

Which number types work

Any number that meets the rules can be registered. What varies is how reliably the verification code reaches you. Meta's own table rates each type for SMS and voice codes:

Number typeSMS codeVoice codeNotes
MobileStandardStandardMeta's recommended type
Fixed line (landline)Not recommendedStandardChoose a voice call; turn off call forwarding and IVR
Toll-free / freephoneNot recommendedStandardNeeds to accept international calls; see the IVR steps below
VoIPNot recommendedStandardConfirm the provider accepts international calls and SMS
Premium rateNot recommendedStandardWorks, but rarely a good customer-facing choice
Universal accessNot recommendedStandardSame handling as toll-free
Inbound onlyNot recommendedStandardMust be able to take the registration call
Shared costNot recommendedNot recommendedExpect trouble verifying
Personal number (not tied to a device)Not recommendedNot recommendedExpect trouble verifying
M2M / IoT SIMNot recommendedNot recommendedAllow incoming international SMS and calls
PagerNot supportedNot supportedCan't be used

The pattern: for anything except a mobile, ask for the code by voice call, and make sure the line accepts calls from international numbers, because the verification call may not come from your country.

Toll-free and IVR numbers

A 1-800 number or any line behind a phone menu can be registered, but the automated registration call can't get past the menu. Meta's process:

  1. WhatsApp gives you one or two phone numbers the registration call will come from.
  2. Add those numbers to an allow list so they reach a person or a voicemail box rather than the menu.
  3. Route the call to someone who can read out the code.

If your phone system can't allow-list callers, add the number to your WhatsApp account first, then open a Direct Support ticket asking for the registration caller numbers, including the number you are registering. Lines behind an IVR that can't receive the registration call at all are not supported.

Verifying ownership by API

Signup flows and WhatsApp Manager handle verification with a form. If you add numbers programmatically, it is two calls. First request a code, choosing SMS or voice and a language:

curl -X POST "https://graph.facebook.com/v23.0/PHONE_NUMBER_ID/request_code?code_method=VOICE&language=en_US" \
  -H "Authorization: Bearer $WHATSAPP_TOKEN"

Then submit what you received:

curl -X POST "https://graph.facebook.com/v23.0/PHONE_NUMBER_ID/verify_code" \
  -H "Authorization: Bearer $WHATSAPP_TOKEN" \
  -F "code=123456"

If the number is already verified, request_code returns HTTP 400 with error 136024, so check the code_verification_status field first. Verification proves ownership but does not make the number usable: you still have to register it for Cloud API with the register endpoint, which our WhatsApp Cloud API setup guide walks through. Use the current Graph API version from Meta's changelog.

How many numbers you can have

  • Registered number cap. A new business portfolio can register two business phone numbers. Meta raises the cap to 20 automatically once the business is verified or reaches the 2,000 messaging limit, and sends a business_capability_update webhook with the new value.
  • Shared messaging limit. The number of unique people you can message outside the customer service window is set per business portfolio and shared by all its numbers. Adding numbers does not add capacity.
  • Registration attempts. Each number gets 10 register or deregister attempts in a moving 72 hours; after that, error 133016 blocks it for 72 hours.
  • 555 numbers. Through some partners' Embedded Signup flows, eligible businesses can claim up to two US numbers with a 555 area code. They verify automatically but can't be moved to another WhatsApp account or used outside the platform, and their display names must be approved before they send.

If you plan to run a number per region or per brand, read our guide to WhatsApp API multiple numbers before buying lines.

Choosing a number you won't regret

The rules decide what is allowed. These decide what works for your customers.

  • Use a number the company owns for good. A founder's or salesperson's personal mobile becomes a problem the day they leave. The trade-offs of personal numbers are covered in using a personal number with the WhatsApp API.
  • Prefer a number customers already know, if you can free it up. Moving an existing number is covered in how to migrate a WhatsApp number to the API.
  • Match the country to your customers. Meta prices messages by the recipient's country code, not your number's, but people answer local numbers more readily.
  • Keep the line alive. You will need to receive codes again if you re-register, so do not let the SIM or VoIP subscription lapse after setup.
  • Think about calls. A registered number still takes normal calls. Put it somewhere a ringing phone gets answered, or route it to voicemail that points people to WhatsApp.

For the wider decisions around the platform, the complete guide to the WhatsApp API is the place to start.

Where Tenashi fits

The strictest requirement on Meta's list is the fourth one: the number must not be on WhatsApp. For a business whose existing number is its main customer channel, that means deleting the account, losing the app and leaving its groups. Tenashi works the other way round. It needs a number that is already on WhatsApp or WhatsApp Business, links it with a QR scan as a linked device, and leaves the phone working. The team then shares one inbox for DMs and groups, with a CRM, notes and scheduled sends, from $18/mo, with up to three numbers on Growth and unlimited on Scale.

The trade-offs are real: Tenashi is not Meta's platform, so there is no green tick, no templates and no OTP-grade throughput. New numbers are warmed up gradually, and the phone that owns the number should come online regularly so WhatsApp keeps the linked device signed in.

See every feature · Get started

FAQ

Can I use a landline for the WhatsApp API?

Yes. Landlines are eligible as long as you own the number, it has a country and area code, and it can receive the verification call. Meta does not recommend SMS codes for fixed lines, so choose the voice call option, and switch off call forwarding and any phone menu while you verify so the call reaches a person.

Can I use a virtual or VoIP number?

Usually, yes. Meta rates VoIP numbers as standard for voice-call codes but does not recommend SMS codes on them. Check that your VoIP provider accepts international calls and SMS, keep its app or service running during verification, and keep the subscription active afterwards, because you may need to receive a code again later.

Can my API number also be used on the WhatsApp app?

Not at the same time, unless you use coexistence. A number registered on the Cloud API can't be active on WhatsApp Messenger or the WhatsApp Business app. Coexistence lets a WhatsApp Business app number connect to the API through a partner while staying in the app, with some app features switched off.

Does the API number need a SIM in a phone?

No. The Cloud API is hosted by Meta, so nothing runs on a handset for that number once it is registered. The line only needs to receive the verification SMS or voice call during setup and if you ever re-register. Many businesses use a landline or a hosted number for exactly this reason.

Can I use a phone number from a different country?

Meta's eligibility rules ask for a number with a country and area code that you own and can verify; they do not require it to match your business address. Pricing depends on the recipient's country, not your number's. Customer trust is the bigger factor, so most businesses use a number local to the people they message.


Choose the number as carefully as you would a domain name: owned by the company, reachable for codes and familiar to customers. If your best number is the one already on WhatsApp, see how Tenashi uses it as it is.