CandidateResource webhooks
Register a URL using POST /rest/webhooks to receive JSON POST requests for all company webhook events.
Events
| Event | Trigger |
|---|---|
CandidateResource_created | A candidate is created. |
CandidateResource_updated | A candidate changes brand, first/last name, email, job, phone (landline) or CV file. |
CandidateResource_status_updated | A candidate changes hiring stage or job and has a previous stage-history entry. |
Payload
Example with shortened data. See the CandidateResource schema for the full payload fields.
{
"meta": {
"resource_type": "CandidateResource",
"event_name": "CandidateResource_updated"
},
"data": {
"uuid": "c8af1869-9d17-4be1-be17-f4627f23737a",
"first_name": "Alex",
"last_name": "Taylor",
"email": "alex@example.com",
"landline": "+35315550100",
"job_uuid": "e7b05385-309c-4fc0-8575-98889b757592",
"hiring_flow_step": {
"uuid": "d184e612-a5cf-4b7f-9c06-2dfee3df1d32",
"name": "Interview"
},
"source_type": "CareersPage",
"tags": ["Engineering"],
"created_at": "2026-10-15T09:00:00Z",
...
}
}Delivery and limitations
- Adding forms/documents or changing tags, scores or custom fields alone does not trigger a candidate update.
- Delivery is asynchronous; data reflects the resource when processed.
- Requests have no signature/authentication header. Failed HTTP deliveries are recorded but not automatically retried.
- List webhooks to check
last_successandlast_failure.