Title
Page icon
Create new category
Edit page index title
Edit category
Edit link
Availabilities
Availability objects are used to convey an operator's ability to provide a service at a given time.
Reference can be found here
AvailabilityItem
An AvailabilityItem represents a point or period of time (depending on the parent Product's availabilityType) when the parent Product Option is available for booking.
When placing a booking, the AvailabilityItem ID is used as a reference to the desired reservation time. For this reason, it is important for Operator Booking Systems to have methods in place to resolve these IDs for future reference.
Field Name | Type | Required | Description |
|---|---|---|---|
| string | Yes | Unique identifier for this Availability within the Product Option |
| string | Yes | ID of the Option this availability is under, unique within the Product. |
| string(RFC3339) | Yes | The start time (inclusive) of the availability |
| string(RFC3339) | Yes | The end time (inclusive) of the availability |
| string(AvailabilityStatus) | Yes | Indicates whether the availability is bookable, and provides additional context |
| integer | No | Number of units available for this option at this time. Additional information on Vacancies can be found below |
Examples
Note on DateTimes
localDateTimeStart and localDateTimeEnd must be provided as fully-qualified RFC3339 timestamps, including a UTC offset (or a suffix of Z for an offset of -00:00).
The offset provided MUST match the local timezone of the product option.
AvailabilityStatus
Name | Description |
|---|---|
| Always available |
| Currently available for sale, but has a fixed capacity |
| Currently available for sale, but has a fixed capacity and may be sold out soon |
| Currently sold out, but additional availability may free up |
| Currently not available for sale, but not sold out (e.g. temporarily on stop-sell) and may be available for sale soon |
Note on Vacancies
There are some additional rules and validations on how vacancies should be counted in availabilities.
If the availability has a status of
FREESALE, vacancies should be omitted from the response - theFREESALEstatus implies an unlimited number of vacancies.Vacancies should be considered the total capacity of the product. The number of vacancies returned will be considered available for all unit types returned.
It is recommended that vacancies be drawn from a general pool of vacancies shared among all Unit types within a Product Option.
Vacancies are only available at the Option level, if you need to set availability/vacancies at a traveler type level then an option should be created for each traveler type and the vacancy set there.
Questions? We'd love to hear them. Contact Travel Curious Support.