Does OCTO certify my API?

No. There is no official OCTO certification. We do provide a validation tool that can be used to ensure compliance. The tool is available at https://validator.octo.travel

How often is the specification updated?

OCTO has three development cycles. If there are changes to the specification, they will get updated at the end of each cycle which is April 30, August 31, and December 31.

What technologies does OCTO support?

The OCTO specification is based on JSON and REST. As new technologies become available, OCTO will consider supporting them as well.

Do I have to pay to use the OCTO spec?

No. The OCTO specification is free and open source. There is no fee for cost associated with using the specification.

Do I have to be a member to use the specification?

No. The OCTO specification is open source and available for anyone to use. In fact we encourage everyone to use the OCTO specification regardless of member status.

Is OCTO an API?

No. The OCTO specification is a guide for how to create an API. If you do not have an API yet, the OCTO specification can be used as a blueprint for building your own API.

Does OCTO charge per booking?

No. OCTO is not a booking or distribution service and does not charge per booking fees.

How does OCTO make money?

OCTO is a not for profit organization and makes money from membership fees. Those fees are used to pay for staff and resources to manage and maintain the specification.

How do I connect to the OCTO server?

OCTO does not have a server you can connect to. When you use the specification to build your API, you can connect to an OCTO compliant partner. Alternatively, you can use the OCTO validator tool to test whether your API is coded correctly. The validator tool is available at https://validator.octo.travel