Webhooks
Push careCycle events to your systems, and debug every delivery from the message log.
Webhooks push events from careCycle to your endpoints as they happen, at Settings > Developer > Webhooks (developer settings permission required).
Creating an Endpoint
Add an endpoint with its HTTPS Endpoint URL and an optional description, then choose which events it receives: the picker groups event types by category and is searchable. Selecting nothing means the endpoint receives all events, which is a sensible default while you are exploring.
For the event catalog and payload shapes, see the webhook events reference.
The Delivery Log
Every message to an endpoint is logged, and this is where webhook debugging happens. Open a message to see:
- The message content (formatted or raw JSON, copyable).
- Every delivery attempt, filterable by All, Succeeded, Failed, or
Canceled, each expanding to the HTTP response code, the response body your
server returned, and the signed headers (
svix-id,svix-signature,svix-timestamp) for verifying authenticity. - A Replay button to resend a message after you have fixed your endpoint.
Verify signatures on your side using the svix headers so you only trust events careCycle actually sent.