WAME API

Meta Business PartnerOfficial Meta partner4.8 out of 5 from 230 reviews

WhatsApp, Instagram and Messenger API — official and unofficial, in a single instance

The official one is Meta's Cloud API: compliance, the green badge and per-message billing. The unofficial one connects by QR Code, costs a flat monthly fee and takes text volume with no platform limit. Both in the same account, with the same SDK and the same webhook — you choose per instance and switch without rewriting code.

Creating an account is free and asks for no card.

Continue with Google
See pricingOfficial or unofficial? Compare in 10 seconds
  • On the market since 2017
  • 50,000+ instances created
  • 99.9% uptime
  • 24/7 human support
MCP for AIConnect Claude and let the AI send and read messages across all three channels.

Comes in through

  • WhatsApp
  • Instagram
  • Messenger

1 instance

1 API key
1 webhook

Goes out to your webhook

{
  "object": "wame",
  "provider": "whatsappinstagrammessenger",
  "official": true,
  "entry": [{
    "changes": [{
      "field": "messages",
      "value": {
        "messages": [{
          "type": "text",
          "text": { "body": "Did my order arrive?" }
        }]
      }
    }]
  }]
}

The envelope is identical across all three channels. What changes is the value of provider.

Official or unofficial

Official or unofficial WhatsApp API?

Anyone looking for a WhatsApp API reaches this fork sooner or later. If you want the official WhatsApp API, that is the left column: Meta's Cloud API, with the green badge and per-message billing. If you want the unofficial WhatsApp API, that is the right one: QR Code connection and a flat monthly fee. Below is what actually differs between them — including what the unofficial one does not solve.

Official API

Meta's Cloud API, through WAME

Cost
The instance subscription plus what Meta charges per message sent.
Activation time
Minutes. Sign-in through Embedded Signup, Meta's own flow.
Risk of the number being blocked
No risk of a ban for using the API. The number operates inside Meta's rules.
Green badge
Eligible, subject to Meta's approval.
Meta approval
Required — but it is already ours. You do not create an app on Meta for Developers, do not go through business verification and do not become a Tech Provider.
Sending limit
Meta's tier: starts limited and grows with the number's quality rating.
Best fit
Companies that need compliance, the green badge and campaigns at volume.
I want the official one

Unofficial API

QR Code connection, flat price

Cost
Only the instance subscription, from $5.99. No per-message cost.
Activation time
Minutes. Scan a QR Code, same as WhatsApp Web.
Risk of the number being blocked
It exists. It depends on the number's behaviour — volume, speed and reports from recipients. Nobody can guarantee otherwise.
Green badge
No.
Meta approval
Not applicable.
Sending limit
No platform limit. The practical limit is the number's behaviour.
Best fit
Developers and agencies: support, automation, prototypes and predictable cost.
I want the unofficial one

Still unsure? Full comparison between the official and unofficial API · How the official API works through WAME

Three channels, one instance

WhatsApp, Instagram and Messenger in the same instance

These are not three integrations talking to each other. It is one. Switching channels means changing the value of one field in the request — the rest of your code stays the same.

  • One API keyThe same credential authenticates all three channels. There is no separate account per network and no token to keep in sync.
  • One webhookA single URL receives everything. The provider field says which channel it came from; official says whether it came from the Cloud API or the unofficial connection.
  • One payload formatA Meta-standard envelope, identical across all three channels. What changes is the provider value and the contents of value.

In practice: one integration instead of three, a single place to manage conversations, and a maintenance cost that does not triple with every new channel your client asks for.

Connect all three channelsHow the Instagram and Messenger API works

Send

await wa.message.send({
  type: TypeMessage.TEXT,
  body: {
    to,
    text: "Your order is out for delivery",
    provider: "whatsapp",
  },
});

Receive — the webhook that arrives

{
  "object": "wame",
  "provider": "whatsapp",
  "official": true,
  "instance": "552199999999",
  "entry": [{
    "changes": [{
      "field": "messages",
      "value": { "messages": [{ "text": { "body": "Did it arrive?" } }] }
    }]
  }]
}

Notice what did not change between the tabs: the endpoint, the key, the envelope structure. Only the value of provider.

Pricing

How much the official WhatsApp API costs — and the unofficial one

Prices on screen, no form and no sales call. They are two different bills: the unofficial one is just the instance subscription; the official one is the subscription plus what Meta charges for each message you start.

Unofficial WhatsApp API — flat monthly price

No per-message cost. Unlimited text on the Pro and Enterprise plans.

Basic

Basic plan for simple needs. Ideal for beginners.

USD$5.99/month
1 instance
Text messaging
Receive webhook events
Reply to messages
Manage contacts
Manage groups
Send images
Send audio
Send location
Send documents
Send polls
Send lists (MENU)
Action Buttons
Reply Buttons
Pix payment messages
Trigger call event
Official with Meta
Subscribe

Enterprise

Everything unlocked. Ideal for businesses looking for a complete solution.

USD$12.99/mo
1 instance
Unlimited text messaging
Receive webhook events
Reply to messages
Manage contacts
Manage groups
Send images
Send audio
Send location
Send documents
Send polls
Send lists (MENU)
Action Buttons
Reply Buttons
Pix payment messages
Trigger call event
Mobile Connection
Official with Meta
Subscribe

Pro

Includes interactive buttons. Ideal for businesses seeking more engagement.

USD$9.99/month
1 instance
Unlimited text messaging
Receive webhook events
Reply to messages
Manage contacts
Manage groups
Send images
Send audio
Send location
Send documents
Send polls
Send lists (MENU)
Action Buttons
Reply Buttons
Pix payment messages
Trigger call event
Official with Meta
Subscribe

Resell the WhatsApp API: partner pricing from 20 instances

For CRMs, SaaS products and agencies that sell the automation as their own. See the CRM and SaaS program

🚀 Partner Program

Resell the platform as your own

Scale your business with your own automation — 100% over the API, with no dashboard to depend on.

Official (Meta) and unofficial instances on the same platform
Full management over the API (create, activate, deactivate, delete)
One consolidated monthly invoice (every instance in a single payment)
Low per-unit price, leaving a healthy profit margin
Dedicated, separate infrastructure

Offer free trials to your customers. Because billing is monthly, you can hand out trials freely.

Every instance with Enterprise permissions

Everything unlocked: unlimited sending, webhooks, buttons, lists, media, and official (Meta) + unofficial instances.

Price per instance, billed monthly:

20–99 instancesTalk to us
100–299 instancesTalk to us
300–799 instancesTalk to us
800+ instancesTalk to us

Minimum of 20 instances · no lock-in

Example with 20 instances:

Partner pricing is quoted per region — talk to us.

I want to be a partnerGoing past 300 instances? Talk to sales →
Public, real-time uptimeNo dressed-up metrics — check for yourselfDedicated infrastructure

Minimum 20 instances · cancel anytime

Official WhatsApp API: the subscription price plus the per-message cost

Since 1 July 2025, Meta charges per template message delivered — it used to be per 24-hour conversation. The amount depends on the template category, the recipient's country and, for utility and authentication, your monthly volume.

Replying to a customer inside the 24-hour window they opened is free — most day-to-day support generates no per-message cost. You pay for the templates you start. See the rates by category and simulate your cost.

Meta's price is the same if you go direct. What changes is everything else

Meta gives no discount for going direct — the per-message cost is identical. The difference is what you have to build and maintain before sending the first message. Through WAME, none of this is your problem:

  • Create an app on Meta for Developers
  • Go through Meta's business verification
  • Configure webhook, verify token and HMAC signature
  • Generate and renew System User tokens by hand
  • Become a Tech Provider to resell

Instead: one sign-in through Meta itself, and the number is already sending.

Connect the official API

Technical proof

REST, webhooks and SDKs — no mandatory dashboard

One HTTP request sends the first message. Below is the request and the response you get back, unsimplified.

Request

curl -X POST "https://us.api-wa.me/YOUR_KEY/message/text" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "559999999999",
    "text": "Hello!",
    "provider": "whatsapp"
  }'

Response

{
  "status": 200,
  "data": {
    "key": {
      "remoteJid": "[email protected]",
      "fromMe": true,
      "id": "3EB0A0B1C2D3E4F5A6B7C8"
    },
    "messageTimestamp": "1718900000",
    "status": "PENDING"
  }
}
TypeScript / Nodenpm i @raphaelvserafim/client-api-whatsappPHPcomposer require raphaelvserafim/client-php-api-wa-me
Checking…Uptime —Latency —Status page

Already integrates with

ChatwootA single inbox with the channels connected.n8nAutomation and an AI bot without writing a backend.MCPClaude and other assistants reading and replying directly.CRM e SaaSREST and webhooks: integrates with any system that speaks HTTP.

API documentationMeta-standard webhooksSwagger / OpenAPIllms.txt for AI

Infraestrutura

What runs underneath when you hit send

Trust is not a slogan, it is architecture. This is the stack that runs our customers' instances in production — from message delivery to billing.

Cloudflare at the edge

Traffic goes through Cloudflare before reaching the application, with edge protection and caching in front.

AWS

The platform runs on AWS. Capacity follows demand instead of depending on a fixed server.

Each instance in its own container

Each instance runs in its own Docker container. One customer's volume or failure never touches another's.

Microservices

Services split by responsibility: each one scales and fails on its own, without taking the whole platform down.

Redis queues

Sending spikes go into a queue instead of overloading processing. Nothing is lost at peak hours.

Google Cloud SQL

A managed database on Google Cloud. Operation, backup and maintenance sit with the provider, not with a loose server.

Dedicated infrastructure

Partners at volume run on infrastructure separate from the shared base, with capacity of their own.

Meta's official Cloud API

The official layer talks straight to the WhatsApp Cloud API, under our approval as a Meta Business Partner.

Payments through Stripe

Billing goes through Stripe. Card data never touches our infrastructure — Stripe processes and stores it.

Don't take our word for it — check. Uptime is public and real time, with no dressed-up metrics.

See live status

Objections

The questions you were going to ask before subscribing

Straight answers — including when the answer is not the one we would like to give.

Will I lose my number?

It depends on which API you use, and it is worth being blunt: on the unofficial API there is a real risk of Meta blocking the number. Nobody can promise otherwise — anyone who does is lying. The risk comes from the number's behaviour (volume, speed, how many people report it), not from the platform. On the official API that risk does not exist, because the number operates inside the rules of Meta's Cloud API. If you already use the unofficial one and want to move, you can take the same number to the official API.

Do I need to be a Meta Tech Provider?

No. WAME is a Meta Business Partner and the official infrastructure — approved app, webhook, token — is ours and maintained by us. You do not need to create an app on Meta for Developers, go through business verification, configure a verify token and HMAC signature, or generate and renew System User tokens by hand. That holds for resellers too: you can connect your customers' official accounts without becoming a Solution Partner.

How long does activation take?

On the unofficial API, as long as it takes to scan a QR code — same as WhatsApp Web. On the official API, you sign in through Embedded Signup, which is Meta's own flow: authorize the business account, pick the number, and it is already sending and receiving over the Cloud API. Minutes, not days — because the slow part, getting the app approved by Meta, was already done by us.

Does it work with my CRM?

Yes. The API is REST and the webhooks follow Meta's envelope format, so any system that speaks HTTP can integrate. There are ready-made integrations with Chatwoot and n8n, official SDKs for TypeScript/Node and PHP, Swagger/OpenAPI documentation, a Postman collection, and an llms.txt for anyone who prefers to integrate with AI help. We also run an MCP server, which connects assistants like Claude straight to your conversations.

Is there a free trial?

We do not offer a free trial period. What we do offer is a monthly subscription with no lock-in: you sign up, use it, and cancel from the dashboard whenever you want, with no penalty and no minimum term. Creating an account costs nothing and asks for no card — payment only comes in when you pick a plan.

How does coexistence with the phone app work?

Coexistence is a Meta feature that lets the same number work on the official API and in the WhatsApp app at the same time. In practice, your team keeps answering from the phone exactly as before, and the API runs in parallel on the same number — automation and human support side by side, with no need to choose one or keep two numbers.

Still have a question? Talk to us — human support, 24/7.

Get started

Start with the channel you need today

WhatsApp, Instagram and Messenger in the same instance — official or unofficial, and you can switch later without rewriting the integration.

Creating an account is free and asks for no card.

Continue with Google
  • No lock-in — cancel from the dashboard whenever you want
  • No credit card to sign up
  • Human support, 24/7