Authentication Guide
Workspace admins create keys in Settings → Developers. Send x-api-key: wp_... on every request. Keys act with agent permissions and can be revoked at any time; create a new key before revoking an old one.
JSON API endpoints with workspace API keys, plus HTTP request steps in automations, so your systems can send messages and react to conversations.
curl -s https://zaploom.beenait.com/api/messages/send \
-H "x-api-key: wp_live_..." \
-H "Content-Type: application/json" \
-d '{
"to": "+15555550123",
"channelId": "ch_abc123",
"message": { "type": "text", "body": "Hello from Zaploom!" }
}'Jump to the topic you need. API keys are created inside the workspace under Settings → Developers.
Send messages, manage contacts, templates, and campaigns via JSON API endpoints authenticated with workspace API keys.
/api/*Official SDK libraries are in development. In the meantime, use the REST API with API key authentication to integrate with Zaploom programmatically.
Zaploom receives WhatsApp webhooks from Meta for inbound messages and delivery receipts. To notify your own systems, add an HTTP request step to an automation: it calls your URL when the automation runs.
The essentials for calling the API today.
Workspace admins create keys in Settings → Developers. Send x-api-key: wp_... on every request. Keys act with agent permissions and can be revoked at any time; create a new key before revoking an old one.
Zaploom does not publish its own API rate limits yet. WhatsApp sending is subject to Meta's messaging limits for your number, and campaigns are sent in batches.
Errors return a standard HTTP status with JSON like { "error": "..." }. A failed WhatsApp send returns 502 with Meta's reason.
Launch unified messaging in days with templates, automation, and analytics included.