API reference · Conflict Detection
Conflict Detection
Check a proposed event against the user's selected calendars before booking.
★
Aspirational surface. This resource is part of the developer-platform roadmap. The field shapes follow the same conventions as live resources and are stable for prototype integrations.
Endpoints
POST
/v1/events/check_conflicts
Check a proposed event for conflicts
Check conflicts for a proposed event
HTTP
POST /v1/events/check_conflicts
Given a proposed time, returns conflicts across the user's selected calendars plus suggested alternatives from find_slots.
JSON
{
"proposed_event": {
"user_id": "usr_1abc2def3ghi",
"start_time": "2026-05-22T14:00:00-07:00",
"end_time": "2026-05-22T15:00:00-07:00",
"attendees": [{"email":"sarah@example.com"}]
},
"scope": {
"calendar_ids": ["cal_5g2h9j4k", "cal_8m4n7p2q"]
},
"suggest_alternatives": true
}Response:
JSON
{
"object": "conflict_report",
"has_conflicts": true,
"conflicts": [
{
"event_id": "evt_existing01",
"title": "Team standup",
"start_time": "2026-05-22T13:55:00-07:00",
"end_time": "2026-05-22T14:25:00-07:00",
"calendar_id": "cal_5g2h9j4k",
"overlap_minutes": 25
}
],
"alternatives": [
{ "start": "2026-05-22T15:30:00-07:00", "end": "2026-05-22T16:30:00-07:00", "score": 0.92 }
]
}Notes
- Attendee conflicts are only surfaced for attendees who are also ChronaPilot Connect accounts under your platform.
- External attendees with public free/busy enabled (Google "share busy" calendars) are best-effort.