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 / START ON THE DEVELOPER PLATFORM

Start building in the sandbox.

01

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 docs
02

Try it in your browser

Search, price and book in the playground. You don’t need an account.

Open the playground
03

Create a sandbox account

The sandbox is free and you can sign up yourself. Create credentials and call the API from your own code.

Create a sandbox account

Sandbox 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

Think beyond the first request.

03 / BEFORE YOU GO LIVE

Agree the integration boundaries.

01

Products and scope

Confirm the inventory, markets, and booking flows available for your integration. Supplier coverage and payment options can vary between African markets.

02

Access and environments

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.

03

Operations and support

Agree payment handling, incident contacts, and the scope of post-booking support.

04 / READY FOR A TECHNICAL CONVERSATION

Bring a focused brief.

Where can I get the API documentation?

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.

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.