The public API and webhooks
Server-to-server access with an API key: send messages, sync contacts, record conversions.
Your own systems can talk to WABridge with an API key instead of a user login. The key names exactly one workspace, and every endpoint checks the scopes you gave that key. The API needs a Live workspace and a plan that includes Integrations.
What it can do
- Create or update a contact from your CRM.
- Send an approved template, or a free-form reply inside the 24-hour window.
- Read your account, your templates and your leads.
- Record a conversion, so revenue your systems see gets attributed back to the conversation that caused it.
- Enrol a contact in a journey.
- Subscribe to webhook events, including from Zapier.
Reference
Full API referenceEvery endpoint, parameter and response, with examples.Postman collectionImport it, set your key, and send a real request in a minute.Things worth knowing before you build
- Keys carry scopes. A key without messages:send cannot send, whatever the request says.
- Send endpoints accept an idempotency key, so a retry after a timeout does not send the message twice.
- Rate limits are per key, not per IP, so one office behind one address is not throttled as a whole.
- Outgoing webhooks are signed with the same X-WABridge-Signature scheme as the lead webhook.
More in API and data
- Your data and privacy — Where your data lives, who can see it, and how to get it out or delete it.