Before you start
- An HTTPS endpoint you control
- A backend or queue that can process webhook deliveries
- A signing secret if you want request verification
Webhook endpoints should acknowledge quickly and move heavier work into your own background job or queue.
Supported events
conversation.createdconversation.resolvedconversation.assignedmessage.receivedcontact.createdcontact.updatedtag.added
Add the webhook endpoint
- Open
Settings → Integrations → Webhooksin Chatting - Add an HTTPS endpoint URL
- Choose which events to send
- Optionally add a signing secret
- Save the endpoint and run a test delivery
Choose only the events your endpoint actually needs so the delivery stream stays easier to review.
Verify signatures
If you save a secret, Chatting signs payloads so your backend can verify each request before processing it.
Use the X-Chatting-Signature header and compare it with a signature you compute using the same secret.
POST /webhooks/chatting
X-Chatting-Signature: <computed-signature>
Content-Type: application/jsonTest deliveries
- Use the Test button after saving the endpoint
- Check the last response summary in Chatting
- Open the saved response body when a test fails
- Verify your endpoint returns quickly
FAQ
Can we send webhooks to any URL?
Only to HTTPS endpoints. Chatting blocks insecure URLs during setup.
Do we have to use a signing secret?
No, but you should if the endpoint does anything important with customer or conversation data.
What should we do if a webhook test fails?
Use the saved response details in Chatting first, then confirm the endpoint URL, event selection, and signature verification logic.
Need raw events in your backend?
Open the Webhooks page in Chatting and add one HTTPS endpoint first.
Open Chatting