Thanks to Nezasa’s powerful APIs, our travel itinerary planner TripBuilder can be easily and quickly integrated into your existing system. While the information flow is guaranteed, this ensures you maximum customisation.
API Overview
| APIs | Description | Article |
| Discovery API |
The Nezasa Discovery API provides RESTful services for all entities available with the service. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features which are understood by off-the-shelf HTTP clients. JSON is returned by all API responses, including errors. |
Read more |
| Itinerary API |
The Nezasa Itinerary API provides RESTful services for creating Nezasa itineraries based on templates. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features which are understood by off-the-shelf HTTP clients. JSON is returned by all API responses, including errors. |
Read more |
| Planner API |
The Planner API provides RESTful endpoints for all components and itineraries available within our system. JSON is returned by all API responses including errors. |
Read more |
| Location API |
The Location API provides RESTful endpoints for locations available within our system. JSON is returned by all API responses including errors. |
Read more |
| Booking API |
The Nezasa Booking API provides RESTful services for all entities available with the service. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features which are understood by off-the-shelf HTTP clients. JSON is returned by all API responses, including errors. |
|
| Booking API Webhooks |
The Webhooks API described below provides RESTful endpoints for the management of webhooks. JSON is returned by all API responses including errors. The Webhook feature allows external parties to get asynchronous notification about certain events (such as when a booking has been created, when a booking has been cancelled etc.) from TripBuilder. |
API Versions
Do we guarantee backward compatibility on our APIs or do we freely change them anytime?
We aim to support 2 versions of our API in parallel for breaking changes: the old one before the breaking change and the new one. There is a time window for customers to migrate to the new version which is 3-months.
Comments
0 comments
Please sign in to leave a comment.