Subscribe to CATS ATS webhooks for candidate and pipeline events

Steps

1. Create a webhook either through the CATS Administrative UI or via the API's own webhook endpoints (list/get/create/delete), authenticated the same way as any other call with 'Authorization: Token <Your API Key>'.
2. Subscribe to specific <resource>.<action> style events, e.g. candidate.created or pipeline.status_changed; mass updates in the UI fire one individual webhook per affected record, which can produce a large burst of calls.
3. Each payload includes an event key, an id field named after the resource that fired it (e.g. candidate_id, job_id), and HAL _links/_embedded blocks with the full related resource already inlined.
4. Status-change webhooks (like pipeline.status_changed) carry extra fields beyond the standard payload: pipeline_id, previous_status_id, and new_status_id.
5. Webhook embeds are more generous than normal API responses: up to 1000 of each embedded type instead of the usual 25-item embed cap.
6. Handle delivery failures: CATS tracks 5xx/timeout errors to your endpoint and disables the webhook (emailing you) after 50 consecutive failures within a 30-minute window; a webhook keeps firing until you delete it or your endpoint responds with HTTP 410 Gone.