Introduction
The Nava Hotels API lets your agency search, price and book hotels from the suppliers connected to your microsite, manage those bookings and build a hotel catalogue.
What the API is
The Nava Hotels API is a hotel supplier hub. It resells hotels from the providers connected to your microsite: third-party suppliers and directly contracted hotels. You search, price and book all of them through one JSON API at https://nava.travel/resources.
What you can search and book depends on your microsite's provider setup, not on the API itself, so two microsites can return different hotels for the same search. GET /providers/configurations/{micrositeId} lists the suppliers connected to yours.
The platform behind the API is TravelCompositor. You will see its name in one place only: the Travelc-Trace-Id response header. Everything else on this site calls it "the API" or "the platform".
The three parts
| Part | What it does | Main endpoints | Start here |
|---|---|---|---|
| Booking flow | Search, lock the price, collect guest details, book | POST /booking/accommodations/quote, then /{accommodationId}/confirm, /prebook and /book | The booking flow |
| Post-booking | Read a booked hotel, re-read it from the supplier, price a cancellation, cancel | GET, PUT and DELETE /booking/{bookingReference}/accommodations/{accommodationBookingReference}, plus /cancellation-fee | Cancellations |
| Static content | Hotel catalogue for your UI: names, images, facilities, destinations | GET /accommodations, /accommodations/datasheet, /facilites/* (sic), /mealplan/{micrositeId}, /destination/{micrositeId} | Hotel catalogue |
Around these three sit:
- Authentication: one token per booking flow.
- Reading bookings: the generic Bookings API for back-office and accounting sync.
- Webhooks: a signal when a booking changes.
- Hotel contracts: for suppliers loading their own contracts.
Before you start
You need three things.
- Credentials. A username, password and
micrositeIdfrom your Nava account manager: test credentials first, production credentials after certification. There is no self-registration. See Environments and credentials. - A valid GIATA licence. The documentation requires one to use the API. Talk to your Nava account manager before you launch a hotel catalogue (static content).
- A test account. You build and test with your test credentials before you get production credentials. It has its own base URL,
https://sandbox.nava.travel/resources, and its microsite only has test suppliers.
Before you go live, your integration is certified: the request and response of every call you use is reviewed, and you make three test bookings. See Certification.
How to read the evidence badges
Every important claim on this site carries a badge that says where it comes from. Where the documentation and the spec disagree, the page says so and tells you what to send.
| Badge | Means | How to use it |
|---|---|---|
| Stated in the official API documentation. | Build on it. | |
| Defined in the OpenAPI specification: field names, required flags, validation patterns and enums. | Build on it, and validate your requests against it. | |
| Confirmed in writing by the API owner's support team, usually to settle a gap or contradiction in the documentation. | Build on it. | |
| Confirmed by a live call to the API in a test environment. | Build on it. Test suppliers can differ from real suppliers, so keep handling the other outcomes. | |
| Observed on live production traffic, whether or not the documentation mentions it. | Design for it: it has happened. | |
| Our recommendation or reasoning. The API owner has not confirmed it. | Test it in your test account before you rely on it. |
Plain explanations of what a field is for carry no badge.
Where to go next
Quickstart
Make a booking in your test account with cURL, from token to cancellation.
The booking flow
Quote, Confirm, Prebook and Book, and the key that changes at every step.
API reference
Every endpoint, field, required flag and enum.
Pitfalls
The mistakes that break integrations, and how to avoid them.
Certification
What is reviewed before you get production credentials.