Endpoints & Capabilities
Last updated
Was this helpful?
Last updated
Was this helpful?
OCTO defines a number of that are applicable to most use cases and are required for the implementation.
Since not all use cases can be fulfilled with just the core endpoints, OCTO provides a concept of , allowing for enhancement to the integrations based on specific needs. Capabilities are optional for implementation and to enhance integration by, for example, adding additional information about pricing, content, pickups, etc.
GET
Returns a single Supplier and associated details for a given Supplier ID.
GET
Returns a list of Products and associated details.
GET
Returns a single Product and associated details for a given Product ID.
POST
Returns availability for a given Product & Option as a single object per day. Optimized to be queried for large date ranges and to populate an availability calendar.
POST
POST
POST
PATCH
Updates/changes your booking before and after it has been confirmed as long as it hasn't yet been redeemed or within the cancellation cutoff window.
POST
Cancels your booking. You can only cancel a booking if booking.cancellable
is TRUE
, and is within the booking cancellation cut-off window.
POST
GET
Returns the status and details of your existing booking.
GET
Returns the list of the bookings you made for the given filters.
octo/pricing
Adds pricing to most endpoints giving you advanced static and dynamic pricing capabilities.
octo/content
Extends the core product, option, and unit schemas to provide rich content and images.
octo/pickups
Adds hotel pickup options to the booking allowing the guest to be picked up and set which pickup location they want to be picked up from.
octo/webhooks
It's also possible to use the _capabilities
query parameter if you're unable to use headers:
You can list all the capabilities with a comma to separate each one.
Returns availability for a given Product & Option as a single object per start time (or day). You have to perform this step to retrieve an availabilityId
required for .
Creates a booking that reserves the availability (e.g. while you collect payment and contact information from the customer) for a given availabilityId
. The booking will remain with the status ON_HOLD
until or when the reservation hold expires.
Confirms previously placed , finalizing the booking and making it ready to be used.
Extends the availability hold if the booking status is ON_HOLD
.
Note the Capabilities listed on this page are NOT yet part of the official and are provided for reference only.
This is a draft / unofficial capability, proposed by , , and currently supporting this in their OCTO implementations.
This is a draft / unofficial capability, proposed by and currently supporting this in their OCTO implementations.
This is a draft / unofficial capability, proposed by and currently supporting this in their OCTO implementations.
Allows you to programmatically create webhooks in Supplier's Ventrata system in order to listen out for booking updates or availability updates. This is a draft / unofficial capability, proposed by and currently supporting this in their OCTO implementations.
You control which capabilities you want to enable by using the Octo-Capabilities
. For example: