From search to ticket in three calls
A look inside the Skye Partner API: how an assistant goes from a traveller's request to an issued e-ticket, and what Skye handles so the assistant does not have to.
NEW DELHI

Travel APIs have a reputation. Weeks of certification, a deposit before the first test booking, and a ticketing step that is somehow the partner's problem. The Skye Partner API was designed by working backwards from one question: what is the least an assistant should have to build to book a real flight?
The answer is three calls.
# 1. Swap your key for an access token
POST /v1/token
# 2. Search live fares
POST /v1/search
{"origin":"BLR","destination":"DEL","departDate":"2026-12-24"}
# 3. Start a booking, send the traveller checkoutUrl
POST /v1/bookings/session
{"offerId":"off_test_..."}Search
An API key is swapped for a short lived access token, and search takes an origin, a destination and dates. One way, round trip and multi city all come back as live fares with a stable offer id the assistant can hold on to. Assistants built on MCP skip the REST layer entirely and plug the Skye MCP server straight into their agent.
Book and pay
Starting a booking session returns a checkout link. The simplest integration sends that link to the traveller, who adds traveller details, pays, and gets the e-ticket in their inbox. Card data and passports never touch the assistant.
Teams that want payment to feel native have two more options. They can open the payment inside their own app against an order Skye creates for the exact fare, then confirm in one call. Or, for chat first assistants, they can show a UPI QR or share a payment link right in the conversation, and the booking completes on its own once the traveller pays.
After the booking
Signed webhooks report when a booking is ticketed, pending or failed, so the assistant can tell the traveller the moment something changes. Cancellations and changes have their own endpoints. Because Skye is Merchant of Record, refunds and airline support sit with Skye, not with the partner.
Test before money moves
Test keys come from the partner console the moment a team signs in with a work email. They return realistic fares and simulate payment, so the whole flow, search to ticket, can be built and demoed with no money moving. The console shows every booking, webhook delivery and API call, and includes a playground for sending requests by hand.
“We wanted a developer to have a booked test ticket before their coffee goes cold. Everything that makes travel hard, the payment, the ticketing, the refund, we kept on our side of the API.”
The full reference lives in the Skye API docs.