Cancel after a failed capture
POST/bookings/:bookingId/cancel
If the provider approved and you cannot capture the hold, report capture_failed, then cancel the booking
so the provider does not expect a guest who has not paid. The answer is the booking, now
bookingStatus: cancelled with nextAction: release_hold. Release the hold, then report hold_released.
Never capture a booking you have cancelled.
Allowed only when all three are true: the booking is approved, its paymentStatus is
capture_failed, and the activity has not started. Anything else is 409 CANCELLATION_NOT_ALLOWED.
Repeating the call returns the cancelled booking and changes nothing.
This is the only cancellation you make through the API. For every other cancellation or change of time, contact All Out.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 429
- 503
The cancelled booking.
A field is missing or wrong. The message names it. Fix the request.
No token, an expired token, or wrong credentials (UNAUTHORIZED). Get a new token.
Your account is suspended (PARTNER_DISABLED), whatever token you hold. Contact All Out.
Not yours, not assigned to you, or does not exist (NOT_FOUND). Also a path or method that does not exist.
A conflict with the current state. error.code is one of REFERENCE_CONFLICT, AVAILABILITY_NOT_CONFIRMED,
AVAILABILITY_EXPIRED, PAYMENT_REFERENCE_CONFLICT, IDEMPOTENCY_CONFLICT, INVALID_PAYMENT_TRANSITION or
CANCELLATION_NOT_ALLOWED. See the error codes guide.
Too many requests (RATE_LIMITED). Wait the seconds in the Retry-After header.
Response Headers
Seconds to wait.
The service did not answer (UNAVAILABLE). The outcome may be unknown. Retry with the same Idempotency-Key, or read the booking.