How to Test Crisp Webhooks
Crisp Chat webhook events fire for incoming messages, conversation state changes, and user-typing signals — letting you build CRM sync, automated routing, and reporting on top of live chat.
Crisp Official Webhook Docs1. Crisp Webhook Events
Crisp can send the following webhook events to your endpoint:
message:sendmessage:receivedmessage:updatedmessage:readconversation:createdconversation:stateconversation:assigneduser:typing2. Set Up a Test Endpoint with HookRay
Follow these steps to start receiving Crisp webhooks for testing:
- Go to HookRay and click "Start Testing — Free" to get your unique webhook URL.
- Copy the URL (e.g.,
https://h.hookray.com/abc123). - In your Crisp dashboard, navigate to the webhook settings and paste the HookRay URL as your endpoint.
- Select the events you want to receive (see list above).
- Trigger a test event — HookRay will show the incoming webhook in real-time.
3. Sample Crisp Webhook Payload
Here's an example of what a Crisp webhook payload looks like:
{
"website_id": "1234abcd-5678-90ef-1234-567890abcdef",
"event": "message:send",
"data": {
"type": "text",
"from": "user",
"origin": "chat",
"content": "Hi — does HookRay support custom response codes?",
"session_id": "session_abcdef1234",
"fingerprint": 17454260000000
},
"timestamp": 1745420600
}4. Frequently Asked Questions
How do I test Crisp webhooks without deploying?
Use HookRay to get an instant public webhook URL. Paste it into your Crisp dashboard's webhook configuration, trigger an event, and watch the payload arrive in real time. No code, no ngrok, no deployment. The free tier captures 100 requests per month and works for all Crisp event types.
Why aren't my Crisp webhooks arriving?
Four common causes: (1) the endpoint URL isn't publicly accessible — Crisp can't reach localhost; (2) the wrong events are subscribed in your dashboard; (3) signature verification is rejecting the request before your handler runs; (4) a firewall, expired SSL certificate, or DNS misconfiguration is blocking Crisp's requests. Use HookRay's URL to isolate which of these four is failing.
Why am I getting 400 or 500 errors from my Crisp webhook?
Crisp reports the status code your endpoint returned. HookRay accepts any payload and returns 200 OK by default, so if you see 400/500 while pointing at HookRay, the issue is in Crisp's configuration. If you point at your own endpoint and get 400/500, capture the request with HookRay, replay it locally, and debug from the captured payload.
How do I verify Crisp webhook signatures?
Crisp signs each request with a shared secret. Capture the raw headers and body using HookRay, then verify the signature in your application using Crisp's SDK or a standard HMAC library. Once verification works against HookRay-captured data, you can safely deploy.
Can I replay a captured Crisp webhook?
Yes — HookRay's replay feature re-sends any captured webhook with one click. This is the fastest way to fix a buggy handler: capture the payload once, fix your code, replay until it works. No need to re-trigger events in Crisp.
5. Next Steps
- Use HookRay's webhook replay feature to re-send captured webhooks while building your handler
- Enable smart parsing (Pro plan) to see Crisp-specific fields highlighted automatically
- Check the Crisp webhook documentation for the complete event reference
Ready to test Crisp webhooks?
Get a free webhook URL in 5 seconds. No signup required.
Start Testing Crisp Webhooks — FreeFree PDF: Webhook Testing Cheat Sheet 2026
One-page reference for 50+ APIs — canonical events, signing methods, sample payloads. Print it, pin it, share it.
📄 Download the cheat sheet (PDF, 180KB)