event.attendee_responded
Webhook events · Scheduling
An attendee responded to an invitation.
Subscribe
curl
curl https://api.chronapilot.com/v1/webhook_endpoints \ -X POST \ -H "Authorization: Bearer sk_live_…" \ -d '{ "url": "https://your-app.com/webhooks/chronapilot", "events": ["event.attendee_responded"] }'
Delivery payload
JSON
{
"id": "whe_8x9y0z1a2b",
"type": "event.attendee_responded",
"api_version": "2026-05-20",
"created": 1716247200,
"data": {
"object": {
"event_id": "evt_1abc2def3ghi",
"invitation_id": "inv_7stu8vwx9yza",
"attendee_email": "sarah@example.com",
"status": "accepted"
}
},
"livemode": true,
"request_id": "req_1A2b3C4d5E6f"
}When it fires
An attendee responded to an invitation. See the Scheduling concepts for an overview of the surrounding lifecycle.
Handling tips
- Treat the delivery as the latest state. Re-fetch the resource if you need confirmation against the source of truth.
- Dedupe on id — the same event may arrive more than once.
- Respond with 2xx within 8 seconds to avoid retry pressure.