Getting started with Incidents¶
What does it do?¶
The incident endpoint retrieves complaint and incident data within a date range. Incidents are raised by customers or partners after a completed booking and tracked through investigation to resolution.
Why use it?¶
By integrating the Incident API, you can:
- Monitor complaints and address them promptly
- Track which incidents are attributed to your service (
responsibleParty: SUPPLIER) - Maintain performance against the quality target of incident rate below 1.5%
- Identify patterns (e.g. repeated driver no-shows at specific locations)
Note
For real-time incident notifications, also consider the Incident Webhook. The polling endpoint here is useful as a backup or for historical retrieval.
Authentication¶
All incident endpoints require an OAuth 2.0 access token. See Authentication to get started.
Further reading¶
- Incident endpoint references — Full request/response specification
- Quality Metrics APIs — Overview of survey and incident APIs
- How does Booking.com investigate a customer complaint? — Incident lifecycle, evidence requirements