Introduction to Palisis OCTO API

Blanca Castillo
Blanca Castillo
  • Updated

What does it mean?

Palisis now provides the first version of the Palisis Supplier API V1, based on the OCTO standard. This API allows authorised third-party systems to retrieve booking information from Palisis and receive booking update notifications without needing to work directly in the Palisis back office.

For tour operators, this means booking data can be shared more efficiently with external reporting, finance or operational tools, such as an ERP, BI platform, data warehouse or internal dashboard. For developers, it provides a structured way to connect to Palisis using API key authentication, booking endpoints and webhook notifications.

The integration is designed to support reporting and data synchronisation use cases. For example, your BI tool can request booking details by UUID, while your ERP can be notified when a booking is created, cancelled, refunded, checked in or when a voucher is redeemed.

Webhook notifications are processed asynchronously. This means Palisis sends booking updates to the configured external endpoint without interrupting the booking process for your customers or staff.

Good to know: this is the first version of the API. Palisis will continue to extend the integration in future releases.

 

What should I do?

To use the Palisis Supplier API V1, please contact the Palisis support team here and request API access. Include your Palisis account name, the system you want to connect to, and the purpose of the integration, for example reporting, ERP reconciliation or BI dashboards.

Palisis will provide the relevant documentation and support resources for your implementation. Access is controlled through an API key, which is created for an authorised user and used as bearer authentication by the connecting system.

Once access is available, your developer or integration partner can:

  • Generate and manage the API key in line with the provided instructions.
  • Use the booking endpoint to retrieve supported booking information by UUID.
  • Configure webhooks to receive booking update notifications.
  • Map the Palisis booking data to the target system, such as your ERP, BI tool or data warehouse.

Please keep in mind that Palisis does not build or maintain the integration in your external system. We provide the API access, documentation and support needed for your technical team or integration partner to implement it.

 

FAQs

Who is this API intended for?
The Palisis Supplier API V1 is intended for tour operators and their developers or integration partners who want to connect Palisis booking data to another system. Typical examples include ERP systems, BI tools, data warehouses, finance platforms and internal reporting dashboards.
What can I use the API for?
You can use the API to retrieve booking information and synchronise it with other business systems. For example, a BI platform could collect booking data for revenue dashboards, an ERP could reconcile bookings and refunds, or an operations dashboard could monitor check-ins and voucher redemptions.
How are booking updates shared with my system?
Palisis can send webhook notifications for supported booking changes. These include new confirmed bookings, voucher redemption, cancellations, refunds and check-ins. Your external system receives the notification at the endpoint you configure, then decides how to process or store the update.
Does the API replace the Palisis back office?
No. The API is intended to help external systems consume Palisis booking data for integration and reporting purposes. You should continue to manage your products, operations and bookings in Palisis as usual, unless your integration has been specifically designed for a different workflow.
Can Palisis build the integration for us?
Palisis provides the API, documentation and support resources. The implementation in your ERP, BI tool or other third-party system needs to be completed by your own technical team, your software provider or an integration partner.