Stable REST + XML
Versioned endpoints with OpenAPI 3.1 specs, plus legacy XML where suppliers require it. We absorb supplier breaking-changes so your code doesn’t.
APIs & Developer Platform
Build with adivaha Travel APIs.
RESTful, well-documented, production-grade APIs for flights, hotels, transfers, activities, holiday packages, bookings and payments. Run in sandbox or live, with SDKs in 5 languages and 24x7 developer support.
Aspects of Travel APIs
Production-grade APIs for every travel product.
Plug in flights, hotels, transfers, holidays, activities and payments through a single, consistent interface - sandbox first, then live, with detailed error envelopes and webhook events.
Sandbox first
Every account gets sandbox keys with realistic test data so you can build and verify the full booking flow before going live.
Sub-second latency
Multi-supplier search results streamed back in under one second on the median, with parallel calls and smart caching.
Per-key observability
Dashboards for logs, traces, latency, error rates and rate-limit usage - per API key, per environment.
Endpoints by product
Eight APIs, one consistent contract.
Each product has its own dedicated endpoints with full search, hold, confirm, void and refund flows.
Flight API
GDS & LCC content, fare rules, ticketing, voids and refunds.
v1Hotel API
Multi-supplier inventory, real-time rates and instant confirmation.
v1Bus API
Search, seat selection, fare checks, cancellations and webhooks.
v1Activities API
Tours, attractions and ticket vouchers with QR codes.
v1Transfer API
Airport, point-to-point and chauffeur transfers in 100+ countries.
v1Insurance API
Policy search, quotes, booking and claim submissions.
v1Payment API
Cards, UPI, wallets, BNPL, FX and reconciliation built in.
v1Booking API
Hold, confirm, void and retrieve - shared across all products.
v1
Why engineers pick us
Read the Docs
Battle-tested at scale.
Stable contracts, predictable rate limits and per-key observability - so your team ships in days and doesn’t spend nights firefighting supplier flakiness.
Sandbox first
Every account gets sandbox keys within 24 hours with realistic test data so you can build and verify the full booking flow before going live.
Stable contracts & versioning
Versioned at the path level (/v1/, /v2/). Breaking changes go to a new major version with at least 12 months of overlap - non-breaking additions land in the current version with release notes.
Webhooks with HMAC
Booking events, supplier confirmations and refunds pushed to your endpoint with HMAC-signed payloads for verification.
24x7 developer support
Dedicated Slack channel for Enterprise teams, plus email support with under-4-hour response on all paid plans.
SDKs & tooling
Five SDKs, one consistent API.
Official client libraries for the most common stacks. Plus an OpenAPI spec so you can generate clients in any other language.
PHPcomposer require adivaha/sdk
Node.jsnpm i @adivaha/sdk
Pythonpip install adivaha
Gogo get adivaha/go-sdk
.NETdotnet add package Adivaha
OpenAPI 3.1Generate any-language client
Questions & Answers
Developer questions.
How fast can I get sandbox access?
Sandbox keys are issued within 24 hours of request - usually the same business day. The sandbox runs on the same code as production with realistic test data, so what you build there works in production unchanged.
What rate limits apply?
Default plans get 60 RPS with bursting up to 200 RPS. Enterprise plans negotiate dedicated capacity. All limits are visible per-key in your dashboard with real-time usage.
Do you support NDC and LCC content?
Yes. The flight API surfaces GDS (Amadeus / Sabre / Travelport), NDC offers from supported airlines, and LCC content via partner aggregators - all in a normalized response.
How are API versioning and breaking changes handled?
We version at the path level (e.g. /v1/, /v2/). Breaking changes go to a new major version with at least 12 months of overlap. Non-breaking additions land in the current version with release notes.
Can I plug in my own supplier contracts?
Yes - bring your own GDS PCC, hotel contract or activity supplier and we will wire it in alongside our pre-integrated suppliers, with markups and rules per supplier.
How does authentication work?
Bearer token authentication using API keys issued from your dashboard. Each key has scopes (read, write, admin) and environment (sandbox / live). Webhook payloads are HMAC-signed for verification.
Interested? Have any questions?
Get sandbox keys today and start building. Your team can be live on production endpoints within a week. Talk to a Solutions Engineer or jump straight to the docs.
Explore the platform
Browse all adivaha solutions
Eight products on one connected platform - pick where to start.