How to get a WhatsApp API key: two routes, step by step

There are two routes. Meta's official WhatsApp Cloud API doesn't hand out an "API key": you register as a Meta developer, create an app and generate an access token, a temporary one for testing and a long-lived system user token for real use. An own-number API such as WbizTool links the WhatsApp number you already use, and you create an API key on one settings page, next to your Client ID.

Route 1: an access token for Meta's WhatsApp Cloud API#

These steps follow Meta's developer documentation, checked November 2026. Screen names may change.

What you need first#

• A Facebook account or a managed Meta account.
• A Meta developer registration at developers.facebook.com.
• A business portfolio. You can pick an existing one or create one while you set up the app.

Get a test token#

1. Go to developers.facebook.com/apps and create an app.
2. Choose the Connect with customers through WhatsApp use case, and select or create a business portfolio.
3. Click Start using the API.
4. In API Setup, connect the app to a Messaging account. Its "Messaging account ID" is the same value as the WABA ID.
5. Click Generate access token.

This token sends a test message from a test business number Meta creates for you. Meta says it "expires quickly and is not suitable for development purposes", and its access-tokens page says user tokens need regenerating "every few hours".

Get a long-lived token#

For an app that runs on its own, use a system user token:

1. Open Meta Business settings at business.facebook.com/latest/settings.
2. Go to System users and click Add.
3. Click Assign assets. Give the system user your app with Manage app (full control), and your WhatsApp account with full control.
4. Click Generate token. Choose an expiration preference and these permissions: business_management, whatsapp_business_management and whatsapp_business_messaging.

Meta calls system user tokens "long-lived". Note the expiration you picked.

Send a first message#

Calls go to Meta's Graph API with the token in an Authorization: Bearer header. PHONE_NUMBER_ID is the ID of the business number that sends:

curl -X POST "https://graph.facebook.com/v23.0/PHONE_NUMBER_ID/messages" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"messaging_product": "whatsapp", "to": "15551234567", "type": "text", "text": {"body": "Hello"}}'

Meta's examples use different versions (v23.0 and v27.0 both appear); use the one in Meta's current docs.

What else to know#

• Templates. Free-form text works only inside the 24-hour customer service window, which starts when the customer messages you. Outside it, you need templates approved by Meta.
• Your number. A number registered on the API can't be used in the WhatsApp app. A number already on WhatsApp can't be registered until its WhatsApp account is deleted. The exception is Coexistence, which keeps the WhatsApp Business app on the number and is set up through a Meta partner.
• Pricing. Meta charges per delivered message, by category and recipient country, with 1,000 free service messages a month per number. Meta's pricing page says that without a payment method, service messages stop being delivered after the free tier, so set one up in Billing Hub.
• Limits. A new business portfolio can reach 250 unique users per 24 hours outside a service window. Business verification is one way to raise that to 2,000.

Number, pricing and limit facts from Meta's own pages, checked October 30, 2026. Our WhatsApp API providers comparison compares Meta with other providers.

Through a provider such as Twilio#

A provider gives you credentials for its own API, but Meta's rules stay. Twilio's documentation (checked October 17, 2026) says you need a Meta Business Portfolio and business verification before production, and pre-approved templates outside the customer service window. Twilio charges $0.005 per message plus Meta's fees. See Twilio vs WbizTool.

Route 2: an API key for your own number with WbizTool#

WbizTool is an independent service, not affiliated with WhatsApp or Meta. It sends from the WhatsApp number you already use, linked as a device like WhatsApp Web. There's no Meta app, business portfolio or template approval.

Get your key#

1. Sign up and confirm your email address.
2. Connect your WhatsApp number with a QR code or a pairing code.
3. Open Settings → API keys (also API keys under Integrations in the sidebar). Only workspace Owners see this page.
4. Click Create key, name it after the app that will use it, such as n8n or Website, and click Create key again.
5. Copy the key. The full key isn't shown again, but Copy key copies it later.

You now have three values:

Integrations such as Zapier ask for the Client ID and the key. In your own code, send the key in an Authorization: Bearer header; client_id is then optional.

Test it and send a first message#

POST /api/v1/me/ checks your key without sending anything; a working key answers "status": 1. Then send a message:

curl -X POST https://wbiztool.com/api/v1/send_msg/ \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"whatsapp_client": 101, "phone": "919876543210", "msg": "Hello from WbizTool"}'

See the API keys guide, the Send message API, and how-tos for Python, Node.js, PHP and cURL.

API v2 keys (beta)#

API v2, in public beta, has its own keys in the API v2 keys card on the same page: up to 10, each with scopes, Live or Test (a Test key checks everything and sends nothing), and an expiry of never, 30 days, 90 days or 1 year. v1 and v2 keys don't work on each other's API.

Limits and the risk#

A workspace can have up to 10 v1 keys, which work until you delete them; v2 keys can have an expiry date. Every paid plan sends unlimited messages under fair use, up to 1,000 messages per number in any 24 hours.

WbizTool isn't Meta's official API, and the number you link carries the risk: WhatsApp can ban a number that sends messages people don't want. Message people who expect you, at a steady pace. Can my WhatsApp number get banned? explains how to keep the risk low.

The two routes side by side#

Keep your keys safe#

Anyone with your key can use the API as your workspace, so treat it, and a Meta token, like a password.

• One key per app. Then you can replace or delete one without breaking the others.
• Send it in a header, not the body. Bodies end up in logs more often than headers.
• Keep it on your server, in an environment variable or credential store. Never put a key in a website's JavaScript, a mobile app, a shared spreadsheet or published code, or send it by email or chat.
• Delete a leaked key. Create a new key, update your apps, then delete the old one: it stops working at once. Check Reports for messages you didn't send.

Questions people ask#

Is a WhatsApp API key free?#

Meta has no monthly fee; you pay per delivered message, after 1,000 free service messages a month per number. WbizTool keys work on every plan, including the free trial with 50 messages in any 30 days.

Can I use my current WhatsApp number?#

With Meta's API, a number already on WhatsApp can't be registered until its WhatsApp account is deleted, unless a partner sets up Coexistence for a WhatsApp Business app number. With WbizTool, yes: you link the number you already use.

Who can create a WbizTool API key?#

Workspace Owners. Editors and Analysts don't see the API keys page, so they ask an Owner.

Is WbizTool the official WhatsApp API?#

No. It's independent, not affiliated with WhatsApp or Meta. For the official route, use the Cloud API or a provider such as Twilio.

Get your key and try it#

The free trial includes 50 messages in any 30 days on one number and needs no card. Sign up, connect your number and create your first key. Plans start at $25 a month in the US; prices are regional. The WhatsApp API page explains how it works.