reservation_superseded (409)
reservation_superseded
HTTP status: 409
Retryable: No. Retrying without changes will fail the same way.
The reservation changed, or its live session belongs to a different tenant partition, while a session was being started for it, so that session was not created.
When it fires
Only the connected-system integration that starts sessions for reservations receives this code. A request made with an API key never receives it. The reservation changed after the integration decided to start the session: its guest changed, so the reservation now has a new verification link, or the reservation was canceled. It also fires when the integration starts a session for a reservation that already has a verification link of its own, and when a partition-scoped integration mint races an earlier mint for the same connection reference and the live session the earlier mint created belongs to a different tenant partition (details.reason: tenant_partition_mismatch). No session, applicant, or event is created.
How to handle it
No action is necessary when the reservation changed: the integration acts on the current state of the reservation, starting a session for the current guest when one is due and starting none for a canceled reservation. For details.reason: tenant_partition_mismatch, check that the connection's tenant partition matches the one the live session was created under; the same connection reference cannot start a second session in a different partition.
Example response
{
"error": {
"type": "https://docs-dev.autohost-dev.uk/api/errors/reservation_superseded",
"code": "reservation_superseded",
"message": "The reservation changed while this session was being started, so the session was not created.",
"request_id": "req_01HEXAMPLE0000000000000000",
"doc_url": "https://docs-dev.autohost-dev.uk/api/errors/reservation_superseded",
"details": {
"reason": "cancelled"
}
}
}