An airline ticketing API turns a flight booking into a real, valid ticket — and then looks after that ticket for the rest of its life. Booking a seat is only half the job. The airline has to be paid, the fare rules have to be applied, and the passenger needs an issued e-ticket before they can fly. If plans change, the same ticket may later be voided, refunded or reissued. Tripgic, for example, issues tickets for a validated booking through a single API call, alongside booking look-up and cancellation.
This guide explains airline ticketing from the travel seller’s side: what an “airline ticketing system” means, how booking differs from ticketing, what happens call by call, who is allowed to issue tickets, how time limits and EMDs work, the life of a ticket after issue, ticketing APIs versus ticketing software, and how to choose. It ends with how Tripgic handles ticketing, from its API documentation and pricing page.
What Is an Airline Ticketing System?
The phrase is used for three different things, and search results mix them:
| Meaning | Who uses it | What it does |
|---|---|---|
| The airline’s ticketing platform | Airlines | Issues, stores and changes the airline’s tickets; Amadeus, for example, sells a ticketing platform for airlines with an e-ticket server and ticket-change products |
| Agency ticketing software or portal | Travel agents | A screen where agents search, book and issue tickets, often sold as a B2B portal |
| A ticketing API | Travel platforms and developers | Lets your own website, app or portal issue and manage tickets automatically |
The airline’s platform is where the ticket lives — the airline reservation system holds the booking and the issued ticket. The other two are the seller’s ways of reaching it. This guide is about those: the software and APIs that travel agencies, OTAs and booking platforms use to issue tickets.
Booking vs Ticketing: The Difference That Matters
| Booking | Ticketing | |
|---|---|---|
| What it creates | A record (PNR) holding seats for named passengers | An e-ticket, with a ticket number, for each passenger |
| Money | Usually none yet | The fare is committed and settled |
| Can the passenger fly? | No | Yes |
| Deadline | Must be ticketed before the time limit | — |
| Changes | Usually free before ticketing | Governed by fare rules: void, refund, reissue |
Many problems in flight selling come from treating these as one step. A confirmed booking looks like a sale on your screen, but until the ticket is issued, the seats can disappear — and once it is issued, money has moved and changes cost something. Your system must know exactly which state every booking is in.
How Airline Ticketing Works, Step by Step
- Search and choose. The traveller picks a flight and a fare.
- Validate the price. Your platform re-checks the fare with the source, because fares change between search and payment.
- Create the booking. A PNR is created with the passengers’ names exactly as on their passports, and a ticketing time limit is set.
- Add extras. Bags, seats and meals, where the fare and the airline allow them.
- Take payment. You collect from your customer. Separately, you settle with your supplier — directly with the airline’s settlement system, through a consolidator, or through your API provider.
- Issue the ticket. The ticketing call converts the booking into e-tickets. Each passenger receives a ticket number; paid extras may be issued as EMDs.
- Send the documents. The itinerary and ticket numbers go to the traveller.
- Watch the booking. Schedule changes, cancellations and requests continue until the trip is over.
Steps 2 and 6 are the ones that cost money if they go wrong, and step 8 is the one most often forgotten. Validate before taking payment, and never issue a ticket you have not been paid for — or that the traveller has not confirmed.
What the e-ticket number tells you
An electronic ticket number is usually 13 digits: a three-digit airline code followed by a ten-digit serial number. It is the key the airline, your support team and the traveller all use. Store it against every passenger, show it on every document, and use it — not your own booking ID — when you talk to an airline.
What a ticketing response should contain
Whatever API you use, the booking and ticketing responses should give your system everything it needs to serve the traveller later:
| Field | Why you need it |
|---|---|
| Booking reference (PNR) | To find the booking with the airline and the provider |
| Ticket number per passenger | The key for changes, refunds and airport problems |
| EMD numbers for paid extras | Extras are changed and refunded separately |
| Ticketing time limit (before issue) | To ticket or cancel in time |
| Fare basis and fare brand | To apply the right change and refund rules |
| Baggage allowance per passenger | The most common question at the airport |
| Amounts and currency | To reconcile against what you were charged |
| Status | Booked, ticketed, voided, refunded, changed |
If a provider cannot return these clearly, your support team will end up looking them up by hand.
Who Is Allowed to Issue Tickets?
A ticket can only be issued by someone with authority to issue it. For most airlines that means an agency accredited through the industry’s settlement systems — IATA’s BSP in most countries, or ARC in the United States — or someone issuing on your behalf.
| Setup | Who issues | What it means for you |
|---|---|---|
| You are accredited | You, under your own accreditation | Full control; financial guarantees and reporting obligations |
| A consolidator tickets for you | An accredited wholesale agency | You sell; they ticket and settle. See our flight consolidator guide |
| The API provider issues for you | The provider, through its own arrangements | One API for booking and ticketing; you settle with the provider |
Ask every provider in plain words: when I call the ticketing endpoint, whose ticket is it, and who settles with the airline? The answer decides your paperwork, your cash flow and who handles the airline when something goes wrong. For accreditation in more depth, see our guide to the flight booking system.
Ticketing Time Limits
Every booking carries a ticketing time limit — the deadline by which it must be ticketed. Airlines set it, and it can be short: sometimes days, sometimes hours, and close to departure it can be very short indeed.
If the limit passes without a ticket, the airline cancels the seats. The fare may not come back, and the traveller who thought they had a booking does not.
Three rules keep you safe:
- Read the limit from the booking response, not from a general rule. It varies by airline, fare and how close departure is.
- Track it automatically. A job that checks every unticketed booking and raises an alert well before its limit — not a person remembering.
- Decide what happens at the limit. Either ticket (if paid), or cancel cleanly and tell the traveller. Never let a booking lapse silently.
EMDs: Documents for Extras
Not everything a passenger pays for is part of the fare. Airlines use the Electronic Miscellaneous Document (EMD) for many paid extras — some checked bags, seat selection, fees and services. An EMD sits beside the e-ticket in the booking and has its own number.
For your platform, that means:
- A booking can hold several documents — one e-ticket per passenger plus EMDs for extras.
- Refunds and changes treat them separately. A refundable fare does not make a paid seat refundable.
- Show extras clearly on the traveller’s documents, so the airport desk and your support team see the same thing.
Airlines moving to NDC are also moving toward “orders”, where the offer, the fare and the extras live in one record. The direction of travel is simpler documents; the reality for most platforms today is that both models exist side by side, which is one more reason to let an API normalise them.
The Life of a Ticket After Issue
| Action | What it means | What usually applies |
|---|---|---|
| Void | Cancel a ticket very soon after issue, usually the same day | Often no airline penalty inside the void window; after it closes, refund rules apply |
| Refund | Return a ticket for money back | The fare rules decide how much, if anything, comes back |
| Reissue (exchange) | Change dates, times or route on an issued ticket | Airline change fee plus any fare difference |
| Name correction or change | Fix or change the passenger’s name | Many airlines allow small corrections only; some allow none |
| Involuntary change | The airline changes the schedule or cancels | The airline’s rules for disruption; often free rebooking or refund |
Two costs can apply to each voluntary change: the airline’s penalty or fare difference, and the provider’s service fee, if any. Ask about both before you launch. And show the airline’s rules to the traveller before they buy — most after-sales disputes start with a rule nobody showed them.
A Worked Example: Ticketed, Then Changed
Follow one booking through its life.
- Booking. A family of three — two adults and an infant — books a return flight. The booking response includes a PNR and a ticketing time limit of the next day.
- Payment and ticketing. The family pays that evening. Your platform issues the tickets: two adult tickets and an infant ticket, each with its own number. A paid seat for one adult is issued as an EMD.
- A change. A week later, the family moves the return flight by two days. Your platform asks for a reissue. The airline’s fare rules allow it for a change fee plus the fare difference; your provider adds its own service fee for the reissue. The family sees all three amounts before confirming.
- A partial cancellation. One adult can no longer travel. Their ticket is refunded under the fare rules — a non-refundable fare may return only some taxes. The paid seat on their EMD follows its own rule.
- Reconciliation. At the end of the month, every ticket, reissue, refund and fee matches what your provider charged your wallet or account.
Every step used the ticket numbers stored at issue. Without them, step 3 and step 4 become support calls.
Settlement: How the Money Moves
Ticketing is also where money moves, and there are three common models:
- Accredited agencies report their sales and settle with airlines through the industry settlement systems (BSP or ARC) on a regular cycle.
- Agencies using a consolidator pay the consolidator, which settles with the airlines.
- Platforms using an API provider pay the provider — often from a deposit or prepaid wallet — and the provider settles with its sources.
Whichever model you use, keep your own record of every ticket number and amount, and reconcile it against your statement regularly. Differences usually come from refunds and reissues, not from the first sale.
Special Cases to Plan For
- Infants and children. Infants usually travel on an adult’s lap with their own ticket; children’s fares and rules differ by airline.
- Unaccompanied minors and special assistance. These need airline-specific requests and are often handled outside a standard API flow.
- Groups. Large group bookings often follow different fare and ticketing rules from individual bookings.
- Split tickets. A journey on two airlines may need two tickets, with different rules and no protection between them if one flight is late.
Know which of these your platform will sell, and test them in the sandbox before you advertise them.
Ticketing API vs Ticketing Software
Travel agencies often ask whether they need a ticketing API or ticketing software. They solve different problems:
| Ticketing software or portal | Ticketing API | |
|---|---|---|
| Who uses it | Agents, on a screen | Your own platform, in code |
| Best for | Agencies booking for customers by hand | OTAs, apps, B2B portals and automated flows |
| Speed to start | Fast: log in and book | Needs development, then scales without extra staff |
| Branding | The vendor’s screens, sometimes white-labelled | Entirely yours |
| Automation | Limited | Full: time limits, alerts, documents, reporting |
Many businesses end up with both: a portal for agents and an API underneath it. If you are building your own portal for agents, see our B2B travel platform guide; if you want a ready-made, branded front end, see our white-label travel API guide.
Common Ticketing Challenges
- Missed time limits. The most expensive mistake, and the most preventable. Automate it.
- Name mismatches. A name that does not match the passport can block boarding and cost a name-change fee. Validate names before booking.
- Fare changes at validation. Show the new price and ask the traveller to accept it before payment.
- Timeouts on the ticketing call. A ticket may have been issued even if your request timed out. Look the booking up before you retry — a blind retry can issue two tickets.
- Mixed sources. GDS, NDC and low-cost content handle tickets, EMDs and orders differently. One normalised API hides most of that.
- Schedule changes. Airlines move flights after ticketing. Your system must notice, tell the traveller, and offer the airline’s options.
- Reconciliation. Every ticket, refund and fee must match what you were charged. Keep ticket numbers and amounts in your own records.
How to Test an Airline Ticketing Integration
- Book and ticket end to end in the sandbox, for adults, children and infants.
- Let a booking reach its time limit without ticketing, and confirm your alert fires first.
- Void a ticket inside the void window and check the result.
- Request a refund and a reissue and compare the amounts with the fare rules.
- Add paid extras and confirm they appear on the documents.
- Force a timeout on the ticketing call and confirm your code looks the booking up before retrying.
- Reconcile a test day’s tickets against your wallet or invoice.
How to Choose an Airline Ticketing API
| Question | What a good answer looks like |
|---|---|
| Whose ticket is it, and who settles with the airline? | A clear answer in writing |
| Which content can I ticket — GDS, NDC, low-cost? | All the sources you sell, through one call pattern |
| Are prices final at validation? | Yes — the validated price is what you pay |
| Can I void, refund and reissue through the API? | Yes, with documented calls |
| What do post-ticketing actions cost? | A published fee per action, plus the airline’s own penalties |
| How do I pay you? | Deposit, wallet or credit terms you can plan around |
| How do I see time limits and ticket numbers? | Returned in the booking response, every time |
For a broader checklist, see how to choose a travel API provider, and for the full booking flow, our flight booking API guide.
How Tripgic Handles Airline Ticketing
Tripgic is a B2B travel API aggregator. For ticketing, here is what its own pages state:
- Ticketing as an API call. The flight endpoints include a call that issues tickets for a validated booking, alongside booking creation, booking look-up and cancellation — fifteen flight endpoints from search to ticket.
- Final prices. Prices returned at validation and booking are final: the supplier net fare plus a flat Tripgic amount per passenger, never a percentage, so the price you show is the price you pay.
- Extras before the ticket. Baggage, seat and meal options can be read and added to the booking through their own calls.
- Several sources, one pattern. GDS content from Amadeus, Sabre and Travelport, NDC, and 100+ low-cost carriers — 800+ airline and LCC connections — booked and ticketed through the same flow.
- Prepaid settlement. The supplier net fare plus the flat amount is deducted from your Tripgic wallet as each booking or ticket is processed; you collect from your own customers.
- Post-ticketing fees, stated openly. A flat service fee per ticket for each void, refund, reissue or name-change request processed through the API, in addition to any airline penalty or fare difference. The amounts are on the pricing page.
- Test first. Sandbox credentials at no charge after a short call; activation for live use usually takes 3–5 business days.
Final Thoughts
Airline ticketing is where a flight sale becomes real — and where most of the risk in flight selling lives. Separate booking from ticketing in your system, track every time limit automatically, store ticket numbers and EMDs against every passenger, and know what each change will cost before a traveller asks for it.
Choose an API that handles the whole life of the ticket, not just the first issue, and be clear from the start about whose ticket it is. Then test the awkward paths — a lapsed time limit, a void, a reissue, a timeout on the ticketing call — until they are routine. A platform that handles those calmly is the one travellers and agents come back to.
Want to issue and manage tickets through one API? Book a demo and get Tripgic sandbox credentials after a short call.
Akhirul Islam





