Documentation
Authentication
Every WhatSyncs API request is authenticated with a bearer token over HTTPS. Webhook deliveries use a separate signing secret, so verifying an inbound event never involves your write credential.
API keys
Create an API key in the WhatSyncs dashboard. Keys are scoped to one workspace and carry the permissions of that workspace — they can read conversations, send messages and manage connections within it, and nothing outside it.
Rotating a key
- Create a second key in the dashboard.
- Deploy it to your service, replacing the old value.
- Confirm traffic is flowing with the new key.
- Revoke the old key. Revocation takes effect immediately.
Because more than one key can be active at a time, rotation does not require downtime.
Webhook signing secret
The signing secret is different from your API key and has one job: proving that an inbound webhook request genuinely came from WhatSyncs. See webhooks for the verification procedure.
Errors
Everything on this page works on the Free plan, including webhooks and full API access.
Start Free