NexlyFlowHelp Center

API tokens and webhooks

Create an API token so your own systems can call NexlyFlow, and send WhatsApp events to your server with webhooks.

Updated 12 Nov 2026 · 2 min read
On this page1. Open API and webhooks2. Create an API token3. Add a webhook4. Check the signatureNo developer? Use Zapier, Make or Google Sheets

An API token lets your developer, Zapier or Make work with your WhatsApp contacts and messages. A webhook sends events, such as a customer reply, to your own server as they happen.

Who can do this: only the Owner and Admins, because a token or webhook reaches all of the workspace's WhatsApp contacts and messages. Admins who only see their own records can view them but not create them.
Plans: all plans.

1. Open API and webhooks

Open API and webhooks

In WhatsApp, open Integrations and click API and webhooks. You can also get there from Settings → API & webhooks.

2. Create an API token

  1. Under API tokens, give the token a Label so you remember what uses it, for example "Zapier".
  2. Click Create token.
  3. Copy the token straight away and keep it somewhere safe.
  4. Send it with every call as Authorization: Bearer <token>.

You can have up to 10 active tokens. Each token can make 60 calls a minute.

Treat a token like a password. Anyone holding it can read and change your WhatsApp data. If one leaks, revoke it: anything using it stops working at once, and this can't be undone. Create the replacement first.

3. Add a webhook

  1. Under Webhooks, enter the Endpoint address: an HTTPS address on the public internet.
  2. Tick the events you want: Message accepted by WhatsApp (message.sent), Delivered to the phone (message.delivered), Read (message.read), Failed (message.failed) and A contact replied (inbound.received).
  3. Click Add endpoint. You can add up to 5.

4. Check the signature

Each event is sent as JSON, for example:

{"event":"inbound.received","tenant":…,"sent_at":"…","data":{…}}

It comes with these headers: X-Nexly-Signature (sha256= followed by the HMAC-SHA256 of the raw body, made with the endpoint's signing secret), X-Nexly-Event and X-Nexly-Delivery. Work out the same signature on your side and compare it before trusting the event.

Answer with any 2xx status within 8 seconds. A failed delivery is tried again after 1, 5 and 30 minutes.

No developer? Use Zapier, Make or Google Sheets

Under Set up a connection, pick Zapier, Make or Google Sheets (with Zapier) for step-by-step instructions. For example, to get events into Zapier: create a Webhooks by Zapier – Catch Hook, copy its address, and add it above as an endpoint.

Was this article helpful?
Still need help?

Our team replies within one business day.

Contact us