Provider configurations
List the supplier connections configured on your microsite. Check it first when a destination or a hotel search returns nothing.
What you can search and book depends on the suppliers connected to your microsite, not on the API itself. This endpoint lists those connections.
Not every API user can call this endpoint. One enabled only for the hotel booking flow gets 401 with User … not allowed to access here; ask your Nava account manager if you need it.
When a search returns nothing
Work through these checks in order:
Dates. Searches need future dates. Sample dates copied from old docs are in the past, and a search for past dates returns nothing.
Suppliers. Call this endpoint to see which supplier connections your microsite has. If you expected one that isn't listed, ask your Nava account manager.
Per-supplier errors. Read providerTraces[] in the Quote response. Each entry has provider, providerDescription, its timing (start, end, processTime), error and quoteResults.
Stale hotel codes. A hotel code that has left the accommodation list returns nothing. This happens when its supplier is disconnected.
Related fields
- Booked hotel services read through
getBookingscarryprovider,providerDescriptionandproviderConfigurationId, which name the connection that sold them.providerConfigurationIdprobably matches anidfrom this list. - Which hotels appear in the accommodation list also depends on these connections, so two microsites can see different hotel sets.
Related
- Quote:
providerTraces[] - Accommodation list
- Destinations
- Reading bookings
Destinations
List the destinations and countries your microsite sells, and read one destination in detail. A destination code is what Quote expects in destinationId.
Shared schemas
Objects that appear across many endpoints, such as auditData, money, meal plans, cancellation policies, pagination, rooms and passengers. Field names, types and validation patterns come from the OpenAPI spec.