How to Test the WhatsApp Cloud API With Postman

To test the WhatsApp Cloud API in Postman, save your phone number ID and access token as environment variables, set Bearer Token auth, and POST a JSON body to https://graph.facebook.com/v27.0/{{phone_number_id}}/messages. Meta also publishes an official Postman workspace you can start from, so you don’t have to build every request by hand.

This guide sets up a small, reusable Postman setup: variables, auth, a request that proves your token works, a first template message, and how to read what comes back. It also explains how to test the webhook side, because an ordinary Postman request can’t receive anything.

Is there an official WhatsApp API Postman collection?

Yes. Meta’s About the WhatsApp Business Platform page calls it “the official Postman collection” and links to Meta’s WhatsApp Business Platform workspace on Postman. Other collections you’ll find on GitHub or vendor sites are copies or cover someone else’s API, so check who publishes one before you paste a token into it.

Even if you import Meta’s collection, the steps below still apply: you need the same IDs and token, and you read responses the same way.

What you need before opening Postman

• A phone number ID and access token from API Setup in your Meta app. The ID isn’t the phone number itself; see how to find your WhatsApp Business Account ID and phone number ID.
• A number to send from. Meta’s sample number is fine for this. Its rules and problems are in how to use the WhatsApp API test number.
• Your own phone as the recipient. Don’t test on customers.

Set up your Postman environment

An environment keeps your values in one place, so requests stay clean and you can switch between a test number and a live one. In Postman, add an environment, name it something like WhatsApp test, add these variables, and select it in the environment selector at the top right.

• Keep the token as a local value. Postman doesn’t sync a local value to its cloud or share it with teammates. A shared value does sync, so leave that empty for the token.
• Keep the version in one variable. Meta’s pages don’t all show the same one: the overview page’s example still says v17.0, while the Send messages example uses v27.0. Check the Graph API changelog and change one value to upgrade.

Set authentication once

Create a collection called WhatsApp Cloud API, open its Authorization tab, choose Bearer Token and type {{access_token}} in the Token field. Postman adds it to the Authorization header after the word Bearer, so don’t type Bearer yourself.

Requests inside the collection inherit this by default. To confirm, open a request’s Authorization tab: the parent’s type appears under Inherited in the Auth type list. For POST requests, choose Body › raw › JSON, which sets Content-Type: application/json for you.

Send your first requests

Build these in order. Each one rules out a different kind of mistake.

The third body assumes an approved template called order_update with the text “Hi {{1}}, your order {{2}} has shipped.” Swap in your own name, language code and values, and if hello_world fails on its language, use the code shown in the sample request in API Setup. Headers, buttons and named parameters are in how to send a WhatsApp template message with the API, and those JSON bodies paste straight into this request.

Read the response

A successful send returns JSON like this, shown here as fields:

To stop copying IDs by hand, add this under the request’s Scripts › Post-response tab. Each row is one line:

Common errors in Postman, and what to change

A failed call returns an error object. Look at code and error_data.details first: Meta says error titles will eventually be deprecated. Keep fbtrace_id in case you need Meta’s support.

• {{variable}} shows up literally in an error. No environment is selected, or the variable name is misspelled.
• You used the phone number in the URL. The path needs the phone number ID.
• Body sent as Text. Choose JSON in the raw dropdown.

The full list, including template and throughput errors, is in WhatsApp API error codes.

Testing webhooks: what a Postman request can’t do

A normal Postman request only sends: it gives Meta no address to call back. Postman’s separate webhook listeners (on its Solo, Team and Enterprise plans) do give you a public URL that logs events or forwards them to localhost, but Postman’s page doesn’t cover Meta specifically, so test it before relying on it. Customer replies and delivery updates are pushed by Meta to a callback URL you own, which must be public HTTPS with a valid certificate; Meta doesn’t support self-signed ones. So a send you tested in Postman can still fail later, and you’d only see that in a webhook. Meta notes that errors can arrive in the response, by webhook, or both.

Once you have an endpoint, Postman is still handy for testing your side of it:

1. Verification: send GET https://your-domain.example/webhook?hub.mode=subscribe&hub.verify_token=YOUR_TOKEN&hub.challenge=12345. It should return 200 and 12345. With a wrong token, it should return an error status.
2. Signature: POST any JSON without a valid X-Hub-Signature-256 header. Your endpoint should reject it. If it accepts it, anyone can fake events.

Neither step proves Meta can reach you. For that, save the callback URL under WhatsApp › Configuration in your app, subscribe to messages, and send a real message. Payloads and retries are in WhatsApp Cloud API webhooks. If you’d rather test in code than in a tool, see how to send WhatsApp messages with Python.

Postman with Automate AI

If you use Automate AI, you don’t call Meta directly. Open the app’s Developer page and press Download Postman collection. Import the file and paste your API key into the collection’s api_key variable; the key isn’t stored in the file. It lists the same requests the Developer page documents, for Automate AI’s own REST API.

Automate AI hosts Meta’s webhooks for you, so replies and delivery statuses show up in your campaign reports and inbox without you running an endpoint. The API and developer webhooks are included on the AI + Automation Plan and Series 4; see pricing and the WhatsApp Business API page.