Read the documentation
Flights and hotels: find airports and places, search, confirm the price, book and look the booking up again. Test scenarios cover empty searches, expired offers, rejected bookings and temporary outages.
Read the docsPlan an Intraverse Travel API integration around your customer journey, from search through booking and the work that follows.
01 / START ON THE DEVELOPER PLATFORM
Flights and hotels: find airports and places, search, confirm the price, book and look the booking up again. Test scenarios cover empty searches, expired offers, rejected bookings and temporary outages.
Read the docsSearch, price and book in the playground. You don’t need an account.
Open the playgroundThe sandbox is free and you can sign up yourself. Create credentials and call the API from your own code.
Create a sandbox accountSandbox bookings are for testing only: nobody is charged and no tickets are issued. To take real bookings, you go through a short review with our team.
02 / THE INTEGRATION JOURNEY
Define the itinerary and traveller requirements. Design for loading, no results, and errors as well as a successful response.
Conceptual integration flow. This is not an API contract or a live request.
search inputs origin LOS destination ACC travellers 1 adult experience states loading → results | no results | error
Show the fare, included services, applicable conditions, and any changes that require the customer to review again.
Conceptual integration flow. This is not an API contract or a live request.
before confirmation trip details traveller information price and currency fare conditions decision continue | revise selection
Coordinate the booking and payment journey with the integration team. Show clear pending, successful, and failed states.
Conceptual integration flow. This is not an API contract or a live request.
customer experience
review → submit → pending
↓
confirmed | action needed
Avoid implying success before confirmation. Plan how travellers see their bookings, receive updates, and request support when their plans change.
Conceptual integration flow. This is not an API contract or a live request.
after booking booking reference current status customer communication service request routing Confirm supported operations with the team.
03 / BEFORE YOU GO LIVE
Confirm the inventory, markets, and booking flows available for your integration. Supplier coverage and payment options can vary between African markets.
Documentation, the playground and sandbox credentials are on the developer platform. Going live includes a short review in which we look at your business, agree pricing and check your integration.
Agree payment handling, incident contacts, and the scope of post-booking support.
04 / READY FOR A TECHNICAL CONVERSATION
On the Intraverse developer platform. You can also try requests in the playground without an account and sign up for free sandbox credentials. The samples on this page explain concepts and are not API documentation.
Discuss your desired products and customer journey so the team can confirm supported scope and commercial terms.
Include your application, customer markets, desired travel products, expected flow, payment model, and operational support requirements.
YOUR NEXT STEP
Start with your use case. We’ll discuss the technical path.