Skip to main content

Availability

AvailabilityOutcome

AvailabilityCode

When availability.isAvailable is false, code is the field to branch on. The detail beside it is a sentence written for a person and localized to the request language — show it, never parse it. Codes are listed here under the outcome they arrive with, because the outcome is what decides the fallbackOptions you are offered. One code can arrive under more than one outcome.

Codes you will never receive

Five codes are rewritten to NO_AVAILABILITY before the response leaves Restoo, because saying why would leak something about the venue or another customer: a banned customer, a duplicate-booking check, and the venue’s internal limits on children. NO_AVAILABILITY is not a catch-all for unknown failures — it means there is a reason and it is deliberately not disclosed. Do not look for something to change.

SHIFT_CONFLICT

The largest group, and the one worth branching on: most of these are the request disagreeing with the shift’s rules, and many are fixed by sending something different.

SHIFT_FULL and SHIFT_SHOULD_CONTACT

Capacity has run out. These arrive as SHIFT_SHOULD_CONTACT when the shift still takes bookings by phone, and as SHIFT_FULL when it does not — the same code, two outcomes, decided by the venue’s configuration.

The remaining outcomes

AvailabilityFallbackOption

Indicates the action suggested to the customer when the request has no availability.

ChildrenSeatingAvailabilityType

Booking

BookingCancelReason

BookingChannel

BookingSpecialOccasion

BookingStatus

CancellationPolicy

CancellationPolicyAmountType

CancellationPolicyConditionsLine

CancellationPolicyStatus

CancellationPolicyType

Customer

CustomerLanguage

Shared

Country

Currency

ImageType

Shift

ShiftAvailabilityStatus

ShiftType