Send messages
Send text, media, templates, interactive messages, and WhatsApp Flows through the official API surface.
Kapso gives developers the API, webhooks, Workflows, CLI, MCP, templates, and inbox tooling needed to build on WhatsApp without rebuilding the WhatsApp operating layer.
The API call is one part. Production WhatsApp products also need events, templates, logs, workflows, and human ownership.
Send text, media, templates, interactive messages, and WhatsApp Flows through the official API surface.
Use webhooks for inbound messages, delivery events, read receipts, failures, and conversation events.
Start from WhatsApp messages, call tools, wait for replies, branch, and hand off to humans.
Use REST APIs, CLI, and Kapso WhatsApp MCP depending on the development surface.
Route sensitive, uncertain, or high-value conversations into inbox ownership.
Track messages, webhook delivery, workflow runs, templates, conversations, and ownership.
Start with one connected number. Add automation only after the event loop is visible.
Create a project and connect a WhatsApp Business number.
Use the phone number ID and a project API key.
Subscribe to replies, statuses, failures, and conversation changes.
Send events to Workflows, agents, CRMs, or the inbox.
Kapso exposes the same WhatsApp foundation through different interfaces.
Backend systems that need direct WhatsApp send, template, media, and conversation operations.
Applications that need inbound replies, delivery status, failures, and workflow events in real time.
Teams that want WhatsApp triggers, AI decisions, tools, waits, branches, and handoff in one builder.
Developers and AI agents that should inspect or operate Kapso from shell or MCP clients.
Use Kapso for the API, webhooks, templates, workflows, CLI, MCP, and human operations around WhatsApp.