The Sautikit WhatsApp messaging API has two parts. You send a message with POST https://api.sautikit.com/v1/whatsapp/messages, and every customer reply and delivery status arrives on your own webhook as a whatsapp.event.received event. That is enough to build a conversational interface on WhatsApp: a support inbox, an order-status bot, a booking flow or reminders customers can answer, with the logic and the data on your own stack.
You connect your own WhatsApp Business account to a Sautikit number in the console: open the number, go to the WhatsApp tab and complete Meta's Embedded Signup. Your business must pass verification first. A number is KES 500 a month at sautikit.com/numbers.
Then subscribe a workspace webhook to whatsapp.event.received and create an API key with the whatsapp.messages scope.
type names the message, and an object of the same name carries its contents. Pick the sending number with number_id (your Sautikit number id) or connection_id.
The call returns 202 with WhatsApp's message id, the wamid. A 202 means WhatsApp accepted the message; delivery is reported later on your webhook, matched by that wamid.
The same endpoint sends every message type WhatsApp supports, because the typed object is forwarded to WhatsApp unchanged:
type
Use it for
text
Replies inside the 24-hour window
template
Starting a conversation: delivery updates, reminders, receipts
image, document, audio, video
A receipt, an invoice PDF, a voice note
location, contacts
A pickup point, a rider's details
interactive
Reply buttons, lists, a link button, a location request, or a Flow (form)
When a customer writes to your number, or a message you sent changes status, Sautikit delivers whatsapp.event.received to your endpoint. The body is WhatsApp's own payload, passed through unchanged, so WhatsApp's documentation describes every field. Identify the event from the X-Sautikit-Event-Kind header, and check whether the body carries messages (something the customer sent) or statuses (a delivery update).
This Express handler answers order-status questions:
import express from "express";const app = express();app.use(express.json());const seen = new Set(); // use your database in productionapp.post("/webhooks/sautikit", async (req, res) => { res.sendStatus(200); // acknowledge first, then work if (req.get("X-Sautikit-Event-Kind") !== "whatsapp.event.received") return; for (const status of req.body.statuses ?? []) { await markMessage(status.id, status.status); // sent, delivered, read, failed } for (const msg of req.body.messages ?? []) { if (seen.has(msg.id)) continue; // delivery is at-least-once; dedupe on WhatsApp's id seen.add(msg.id); if (msg.type === "interactive" && msg.interactive.button_reply) { await saveSlot(msg.from, msg.interactive.button_reply.id); continue; } if (msg.type !== "text") continue; const order = await findOpenOrder(msg.from); // your database await send({ to: msg.from, type: "text", text: { body: order ? `Order ${order.ref} is ${order.status}. Expected delivery: ${order.eta}.` : "Karibu! Send your order number and we will check on it.", }, }); }});
Verify the signature on every delivery before acting on it. The function is in verify webhook signatures.
Each message you send reports back as sent, delivered and read. "Read but not answered" is a state you can branch on: a collections workflow can follow an unread reminder with a voice call, and a sales follow-up can skip the nudge for someone who read the message two minutes ago.
Your application can also mark a customer's message as read with POST /v1/whatsapp/messages/{wamid}/read, so the customer sees the blue ticks.
WhatsApp allows free-form messages only within 24 hours of the customer's last message. To start a conversation outside that window, send a template Meta has approved. You create templates in WhatsApp Manager and send them by name:
Sautikit does not store WhatsApp messages. Every message is delivered to your webhook as it happens, so the thread lives in your database, in your schema, from the first message. Feed it to your support dashboard or your analytics as you would any other event.
The same connection carries voice. Enable WhatsApp Business calling on the number and customers can call you from the chat; a thread that gets complicated can end with a tap-to-call button. See WhatsApp calling for your Kenyan business.
When you need structured answers such as an address, a booking slot or an application, send a WhatsApp Flow you built in Meta's tools as an interactive message. WhatsApp Forms in chat shows the request and the submission.
A Kenyan number is KES 500 a month with no setup fee, and Sautikit does not charge per WhatsApp message. Any WhatsApp conversation fees are billed by Meta to your WhatsApp Business account. Voice calls on the same number are KES 3.00 a minute, billed per second, and incoming calls are free. Rates are on /pricing.
Claim a number at sautikit.com/numbers, connect your WhatsApp Business account from its WhatsApp tab, and point a webhook at your endpoint. The full request and event reference is in the API reference.