Build on top of Flowella, in your own code.
When the no-code tools don’t cover something, the Flowella REST API and outbound webhooks do. Call the API to send WhatsApp messages, manage contacts, opt-outs and WhatsApp Flows, and pull analytics. Subscribe to webhooks to react to messages, deliveries, opt-outs, contacts, and template and Flow status changes as they happen, with no polling.
- Base URL
- api.flowella.io/v1
- Authentication
- A bearer key starting flo_, or OAuth
- Webhook events
- 13, each signed with HMAC-SHA256
- Delivery
- 3 attempts, a 10-second timeout
Call it, and let it call you back.
Two directions, one engine. Your app calls the REST API to make things happen, and Flowella pushes signed webhook events to your endpoint the moment something happens, so you react instead of polling. Send a template, then follow the events back.
Queued in a blink. The events follow.
Send the request, then watch the events come back. Queued in a blink. The events follow. Same key, same job. Nobody gets it twice. A reply brings ids, not the words. No answer? Three tries in all, then I stop.
POSThttps://api.flowella.io/v1/templates/send
Headers
- Authorization
Bearer flo_••••••••••••Your API key, masked- Content-Type
application/json- Idempotency-Key
renewal-2026-10-16-1Repeats of this key within seven days return the same job.
Body
{
"templateId": "cltemplate00000001",
"whatsappChannelId": "clchannel000000001",
"recipients": [
{
"phone": "+447700900123",
"bodyParameters": ["Sam"]
}
]
}
{
"templateId": "cltemplate00000001",
"whatsappChannelId": "clchannel000000001",
"recipients": [
{
"phone": "+447700900123",
"bodyParameters": ["Maximiliana-Wolfgang"]
}
]
}
{
"id": "v1ts-3f9a07c2b1d4e6a8",
"status": "accepted"
}
{
"id": "v1ts-3f9a07c2b1d4e6a8",
"status": "accepted"
}
Queued. Flowella sends it in the background.
Queued. Flowella sends it in the background. Same key, same job: nothing was sent twice. Accepted, but Maximiliana-Wolfgang has opted out on this channel, so Flowella won’t send it.Today
Deliveries
POSThttps://example.com/webhooks/flowella
- Content-Type
application/json- X-Flowella-Signature
5c2e91…a07f3bValid
{
"id": "evt_9a4f1d06c3e84b27a5d9e2b70c6f8d14",
"type": "message.read",
"created_at": "2026-10-16T09:14:21.000Z",
"payload_version": "1",
"data": { … }
}
{
"id": "evt_5b0e2c7d91f64a38b2c6d0e4f7a19c53",
"type": "message.delivered",
"created_at": "2026-10-16T09:14:03.000Z",
"payload_version": "1",
"data": { … }
}
In data: the message’s messageId.
Not in data: the phone number or the message text.
In data: messageId, conversationId, contactId, direction, type and metaMessageId.
Not in data: the phone number or the message text.
In data: the message’s messageId.
In data: the phone number and the reason.
Flowella waits up to 10 seconds for a 2xx and tries each delivery at most 3 times, 1 and 2 seconds apart.
message.sent, message.delivered and message.read reached your endpoint, each one signed.
Change the first name if you like, then send the request. Sending the request. 202 Accepted: Flowella queued the send and returned a job id straight away. message.sent, message.delivered and message.read reached your endpoint, each one signed. Same Idempotency-Key, so Flowella returned the same job and sent nothing twice. Maximiliana-Wolfgang’s reply arrived as message.received: ids, direction and type, not the words. STOP opted Maximiliana-Wolfgang out: message.received arrived, then optout.created with the phone number and the reason. Your endpoint isn’t answering, so Flowella tries again after 1 second, then after 2. Flowella stopped after 3 attempts. Turn your endpoint back on, then send with a new key. Your endpoint answered, so the delivery went through on a retry. 202 Accepted, but Maximiliana-Wolfgang opted out with STOP, so Flowella won’t send the template.Subscribe to any of 13 events.
Pick the events you need in Settings, Webhooks. Each one arrives as a signed POST with its own id, its type, when it happened and its data.
Messages
message.received- An inbound WhatsApp message arrives from a contact
message.sent- Flowella has accepted your message and submitted it to Meta
message.delivered- Meta confirmed delivery to the recipient’s device
message.read- The recipient opened the message
message.failed- Meta returned a failure for the message
Conversations
conversation.opened- A conversation moved into the open state
conversation.closed- A conversation was closed
Opt-outs
optout.created- A contact opted out on a channel
Templates and Flows
template.status_updated- Meta changed a template’s status: approved, rejected, paused or disabled
flow.status_updated- A Flow’s status in Meta changed: published, deprecated, blocked or throttled
Contacts
contact.created- A contact was created
contact.updated- A contact was updated
contact.deleted- A contact was deleted
Plus webhook.test, sent only when you press Send test.
Send, manage and report.
A straightforward v1 REST API at api.flowella.io/v1, with bearer-key or OAuth auth and predictable behaviour.
-
Send messages and templates
Send a WhatsApp text message, or queue one template to many recipients in a single request. Add throttlePerHour and Flowella paces a large send for you.
-
Contacts and opt-outs
Create or update contacts, page through them, and set or clear a contact’s WhatsApp opt-out on a channel.
-
Flows, conversations and analytics
Read a Flow’s screens, fields and live status in Meta, publish or deprecate it, list conversations and templates, and pull outbound message analytics into your own reporting.
-
Keys you control
Owners and Admins create keys in Settings, API keys. Each starts flo_, is shown once and can be limited to the scopes it needs. Partner apps can register for OAuth instead, so each organisation approves them itself.
-
Safe to retry
Send an Idempotency-Key with a template send and a repeat within seven days returns the same job, so a timeout never messages anyone twice.
-
No-code first, code when you need it
HubSpot workflows already send templates with up to 20 variables per contact, no code needed. Reach for the API for what they can’t send, such as one-time codes and per-contact link buttons.
In our customers’ words.
Exceptional engagement platform that transformed our student conversion with 160% increase in same-day applications and 90% WhatsApp response rates.
Peter HudsonDirector of Admissions, Brand & Customer Innovation
Game-changing donation campaign tool that delivers personal WhatsApp engagement with seamless automation and dramatically better completion rates.
Lawrence Tribe-EndtCommercial Director, Countryside Alliance
Straight answers.
The questions developers ask. If yours isn’t here, get in touch.
Read the API referenceAPI and webhooks
How do I authenticate?
With an organisation-scoped bearer key in the Authorization header. Owners and Admins create keys in Settings, API keys. Each starts flo_ and is shown only once, so store it safely and rotate it when teammates leave. Apps you build for other organisations can use OAuth instead.
What can the API do?
Send WhatsApp messages and templates, including one-time codes and per-contact link buttons, create and update contacts, set or clear opt-outs, read, publish and deprecate WhatsApp Flows, list conversations and templates, and pull outbound message analytics. The endpoint list comes from the OpenAPI spec, which drops straight into Postman or a code generator.
Can I send one-time codes or per-contact link buttons?
Yes, through the API, and only there. A copy-code button needs its code on every send, and only the API sets a link button per person: from a HubSpot workflow, everyone gets the template’s one fallback link. To send a per-contact link from HubSpot, put it in a body variable, where WhatsApp makes it tappable. Codes can be up to 15 characters, and the same template to the same number within 15 seconds is dropped. The API answers 202 and sends at once unless you set scheduledAt.
What should I know before my first call?
The base URL is https://api.flowella.io/v1. Lists use cursor pagination with a limit of 1 to 100, errors share one envelope with a stable code, and each organisation is rate limited, with a 429 and a Retry-After header if you go too fast. Pass phone numbers in E.164 form.
Can I do large bulk sends?
Yes. POST /v1/templates/send queues the send and answers 202 Accepted with a job id. Add throttlePerHour and Flowella paces delivery server-side. Add an Idempotency-Key and a repeat within seven days returns the same job instead of sending again.
How do I verify a webhook is genuine?
Each delivery carries X-Flowella-Signature, an HMAC-SHA256 hex digest of the raw body made with your signing secret. Compute the same digest over the raw bytes, before any JSON parsing, and compare. During a secret rotation, X-Flowella-Signature-Previous carries the digest made with the old secret.
What if my endpoint is down?
Flowella waits up to 10 seconds for a 2xx and tries each delivery at most 3 times, 1 and 2 seconds apart, so answer quickly and do the work afterwards. Settings, Webhooks lists each endpoint’s recent deliveries. To fill a gap after an outage, GET /v1/events returns the last 7 days of events, with the same ids, and the deliveries API can replay an event.
How do I avoid processing duplicates?
A retry can deliver the same event twice. Every delivery carries the event’s id at the top level, the same on each retry, so keep a short-lived record of the ids you’ve handled and treat repeats as no-ops.
Does message.received include the message text?
No. It carries ids for the message, the conversation and the contact, with the direction and type, but not the phone number or the words, and the API has no call to read a single message. optout.created does carry the phone number and the reason.
Build on the same engine, your way.
Start with the no-code tools, then reach for the API and webhooks when your stack needs more. Flowella takes about 30 minutes to set up, with a free 14-day trial and no card.
Book a Flowella demo · 30 minutes on Teams