Products and scope
Confirm the inventory, markets, and booking flows available for your integration. Supplier coverage and payment options can vary between African markets.
Build your experience.
Connect the travel.
Plan an Intraverse Travel API integration around your customer journey, from search through booking and the work that follows.
01 / THE INTEGRATION JOURNEY
Think beyond the first request.
Help customers find their options.
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
Make the offer understandable.
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
Treat confirmation as a workflow.
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. Stay close after the booking.
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.
02 / BEFORE YOU BUILD
Agree the integration boundaries.
Access and environments
Request the current documentation, credentials, and testing process through the team.
Operations and support
Agree payment handling, incident contacts, and the scope of post-booking support.
03 / READY FOR A TECHNICAL CONVERSATION
Bring a focused brief.
Where can I get the API documentation?
Contact the team for the current documentation and onboarding process. The samples on this site explain concepts and are not executable API documentation.
Can I integrate only the products I need?
Discuss your desired products and customer journey so the team can confirm supported scope and commercial terms.
What should my technical brief include?
Include your application, customer markets, desired travel products, expected flow, payment model, and operational support requirements.
YOUR NEXT STEP
Make travel part of what you’re building.
Start with your use case. We’ll discuss the technical path.