GDS integration for travel agencies: Amadeus, Sabre, Travelport explained

How to get airline content into your booking system: direct GDS, a consolidator's API or NDC, what each needs, and how tickets should reach your accounts.

GDS integration for travel agencies means connecting your booking system to a global distribution system, so fares, seats and tickets flow into your own software instead of living only in a separate terminal. It is how most agencies get airline content in front of counter staff, B2B agents and online customers from one search.

There is more than one way to do it. You can sign your own contract with a GDS, buy content through a consolidator or aggregator's API, or connect to airlines directly through NDC and low-cost carrier APIs. Each route has a different mix of control, cost structure, paperwork and time to start.

This guide is written for agency owners in Bangladesh, the Gulf, Malaysia and similar markets who are deciding which route to take. It explains the main GDS providers in plain words, compares the three routes, lists what you need before a direct connection, and walks through a typical path in Bangladesh. It finishes with a project plan, a testing checklist, common mistakes and questions to ask a software vendor.

Related guideTravel agency software: the complete buyer's guide for 2027

What GDS integration for travel agencies actually means

A global distribution system is a large network that airlines use to publish schedules, seat availability and fares to travel sellers. Agencies search it, create bookings and issue tickets through it. Before booking software existed, this was done almost entirely through a text terminal with its own commands.

Integration is the step that connects that network to your own software through an API. Your system sends a search request, receives fares back, creates a booking record and asks for the ticket to be issued. The GDS stays the source of the booking, but your staff and agents work in your screens, with your markup and your accounts.

The practical difference is large. Without integration, staff look up a fare in the terminal, copy it into a quotation, then retype the ticket into an invoice and a ledger. With integration, the booking, the ticket and the money records come from the same data, so there is less retyping and fewer mismatches at month-end.

Key terms you will hear

• PNR: the passenger name record, the booking file that holds names, flights, contact details and the ticketing time limit.
• Fare rules: the conditions attached to a fare, such as change fees, refund rules, minimum stay and baggage.
• PCC or office ID: the code that identifies your agency's branch inside a GDS. Sabre and Travelport use pseudo city codes; Amadeus uses office IDs.
• Ticketing authority: the right to issue tickets on an airline's behalf, usually through IATA accreditation and a settlement plan.
• BSP: IATA's Billing and Settlement Plan, which bills accredited agencies for the tickets they issue and pays the airlines.
• NDC: IATA's New Distribution Capability, a standard that lets airlines sell their own offers, bundles and extras through APIs.

The main GDS providers in plain words

Three companies run the GDS networks most agencies use. Each covers a wide range of airlines, but their strength varies by region, and the airline mix and local support in your market matter more than global reputation.

Amadeus. One of the largest GDS providers, widely used by agencies across Europe, the Middle East, Asia and other regions. Your agency is identified by an office ID, and the provider offers both a terminal and APIs for booking software.

Sabre. A major GDS with a long history in North America and a strong presence in many other markets, including parts of the Middle East and Asia. Agencies are identified by a pseudo city code, usually shortened to PCC.

Travelport. The third major provider. Its systems include the Galileo, Apollo and Worldspan brands, which agencies in different countries know by those names. Many agencies in South Asia and the Middle East still refer to their Travelport connection as Galileo.

Most agencies start with the GDS that their local market, their consolidator or their main airlines favour. Larger agencies and consolidators often connect more than one, either to compare fares or to keep selling if one source has a problem. The right choice depends on local office support, the airlines you sell most and the commercial terms you are offered, so compare the providers that are active in your country.

Three ways to get flight content into your booking system

Before you choose software, decide how airline content will reach it. The three routes below are not exclusive. Many agencies combine them, for example a consolidator's API at the start, then a direct GDS connection later, with NDC and low-cost airlines added alongside.

Direct GDS connection with your own contract

You sign an agreement with a GDS provider, receive your own office ID or PCC and API credentials, and your software connects to the GDS on your behalf. You see the full schedules, fare rules and booking controls the GDS offers. In return you take on the contract terms, the certification work and, usually, your own ticketing authority.

A consolidator or aggregator's API

A consolidator is a larger agency or wholesaler that already holds GDS contracts and ticketing authority, and sells fares to smaller agencies. An aggregator brings together content from several sources, including GDS, NDC and low-cost airlines. Either can give you an API, so you can sell flights without your own GDS contract or IATA accreditation while they handle ticketing.

Airline NDC and low-cost carrier APIs

Some airlines sell branded fares, bundles, seats and extra baggage through NDC, and many low-cost carriers sell mainly through their own websites and APIs. Connecting these sources gives you offers that may not appear in a standard GDS search. Each airline has its own onboarding, terms and payment method, so this route usually grows one airline at a time.

General comparison only. Commercial terms, content and timelines depend on the provider, the airline and your country, so confirm them in writing before you sign.

For a new or small agency, the consolidator route is usually the quickest way to start selling. For an agency with steady ticket volume, a direct GDS contract can bring more control and better commercial terms. NDC and low-cost connections are worth adding once you know which airlines your customers ask for most.

What you need before a direct GDS integration

A direct connection is part commercial deal, part technical project. Gather these items before you set dates, because the slowest one sets your go-live.

1. Ticketing authority: either your own IATA accreditation, which lets you issue tickets through BSP in your country, or a ticketing partner who issues tickets for you. Accreditation has financial criteria, which may include a bank guarantee or other security.
2. A GDS agreement: the commercial contract with the provider, covering access, support and the terms that apply to your bookings.
3. Office ID or PCC: the branch identity in the GDS that your bookings and tickets are tied to, with the settings your ticketing needs.
4. API credentials: separate from your terminal login, issued for software access, usually first for a test environment and then for production.
5. Segment targets or fees: many GDS agreements link the commercial terms to the number of flight segments you book. Understand how targets, incentives or fees work before you sign, and what happens if you book less than planned.
6. Testing and certification: the provider or your software vendor runs test bookings, ticketing and after-sales scenarios before production credentials are switched on.

Ask the GDS for the full list of documents and checks in your country, and ask your software vendor which of those steps they handle. A clear owner for each item saves weeks of waiting on emails.

Related guideVendor Management

GDS integration in Bangladesh: the usual path

Agencies in Bangladesh tend to follow a similar path into flight ticketing, though the details change over time and depend on your agency's size and finances. Treat the steps below as general guidance, not a set of rules.

1. Register and license the agency: complete your agency's registration and trade licence with the relevant authorities, and consider joining your national travel agents' association, which is ATAB in Bangladesh.
2. Start through a consolidator: most new agencies sell tickets through an established consolidator or ticketing partner, using its portal or API, while they build volume and a track record.
3. Apply for IATA accreditation: once volume and finances allow, apply to IATA to issue tickets through BSP Bangladesh. Expect financial checks and a guarantee or similar security.
4. Sign with a GDS: talk to the local offices of the GDS providers about an agreement, office ID or PCC, training and API access.
5. Move direct in stages: connect your own GDS credentials to your booking software, keep the consolidator for airlines or routes where its terms are better, and add NDC or low-cost airlines as needed.

Two points matter in this market. First, many agencies sell tickets for labour, student and Umrah travellers, so passport details, group bookings and part payments need to be handled cleanly from the start. Second, prices are often quoted in BDT while some supplier costs are in USD, so your software must record both and show the margin in taka.

General information only, not legal or regulatory advice. Requirements, fees and processes change. Confirm the current rules with IATA, the local office of your chosen GDS and your trade association before you apply or sign.

Agencies in Saudi Arabia, the UAE and Malaysia follow a broadly similar pattern: start with a partner, build volume, then move to direct contracts. The licensing bodies, settlement plans and payment methods differ by country, so check locally.

How multi-GDS search, ticketing and after-sales should work

Getting fares on screen is only the first part of flight booking software. The real test is what happens after the search: holding, ticketing, changing and refunding, and how each step reaches your accounts.

Multi-GDS search and fallback

If you connect more than one source, decide how they are searched. Some agencies search all sources and show the cheapest fare. Others set a priority order, so the preferred GDS is searched first and the next one takes over if the first does not respond. A clear fallback keeps your counter and your agents selling during a timeout or outage.

Fare rules, pricing and the PNR

Staff should see fare rules, baggage and refundability before they hold a seat, and the fare should be re-priced before payment so the customer sees the final amount. When the PNR is created, the ticketing time limit should be visible and tracked, because a missed time limit can mean a cancelled booking and an unhappy customer.

Ticketing, reissue, refund and void

• Issue: the ticket number comes back from the GDS or partner and is stored on the booking, with the e-ticket sent to the customer.
• Void: cancelling a ticket within the short window the airline or settlement plan allows, so it is not billed. The window and rules vary, so check them for your market.
• Reissue: changing dates or routes on an issued ticket, with the fare difference and penalty collected and recorded.
• Refund: returning money under the fare rules, with airline penalties and your own service fee deducted and shown clearly.

How each ticket should update your accounts

Every ticket event should update the money side automatically. An issued ticket should create the customer invoice, the supplier or BSP payable and, for a sub-agent, a debit to that agent's balance. A refund or void should reverse the right amounts, and a reissue should add only the difference and the fees.

This is what makes BSP reconciliation manageable. If ticket sales, refunds and airline debit memos are recorded per airline and billing period, the month-end check becomes a comparison between your report and the BSP billing statement, rather than days of matching ticket numbers by hand.

Related guideB2B travel agent commission: tracking sales from booking to payout

GDS integration for travel agencies: project plan and testing

A GDS or partner integration is easier to manage when it is run as a short project with clear steps and one owner. The plan below works for a first direct connection and for adding a second source.

Testing checklist

• One-way, return and multi-city searches on your main routes.
• Fares with and without baggage, and fares with different refund rules.
• Holding a PNR and watching the ticketing time limit alert.
• Ticket issue for a single passenger, a family and a group.
• Child and infant passengers with correct passport details.
• Void within the allowed window, and the matching reversal in accounts.
• Reissue with a fare difference and a penalty.
• Full and partial refunds with service fees.
• A sub-agent booking against a wallet or credit limit.
• Fallback when the first source does not respond.
• Invoice, ledger and BSP report figures for every test ticket.

Common mistakes to avoid

• Signing before you understand the terms: segment targets and fees can cost more than expected if your volume is lower than planned.
• Testing only the happy path: searches and new tickets work first time; voids, reissues and refunds are where problems hide.
• Leaving accounts until later: if tickets do not post to invoices and ledgers from day one, you rebuild the old spreadsheets.
• Showing every fare to every agent: decide which airlines, fares and markups each sub-agent or channel sees before you open the portal.
• No fallback plan: a single source with no backup means no sales during an outage.
• Sharing credentials loosely: API and terminal logins should be held by named people and changed when staff leave.

Related guideSales are not profit: how to read your travel agency profit and loss

Questions to ask a flight booking software vendor

When you compare flight booking software, ask each vendor the same questions and ask to see the answer in a live demo rather than a slide.

1. Which GDS providers can you connect, and can we use our own credentials?
2. Can we start through a consolidator or ticketing partner and add our own GDS later without changing systems?
3. Do NDC and low-cost fares appear in the same search as GDS fares?
4. How do you handle priority order and fallback between sources?
5. Can you show a void, a reissue and a refund, and the accounting entries each one creates?
6. How are sub-agent markups, commissions and credit limits set?
7. Which report do we use for BSP reconciliation?
8. Who handles certification with the GDS, and how long does it usually take?
9. Which plan includes GDS API integration, and what does it cost?
10. What happens to our data and connections if we leave?

Write the answers down in one place. A vendor who can show voids, refunds and the ledger impact in a demo is usually a safer choice than one with a longer feature list.

Where TravelSuite ERP fits

TravelSuite ERP includes a flight module built for agencies, OTAs and B2B consolidators. It brings GDS, NDC and low-cost carrier fares into one search, so counter staff, online customers and sub-agents book from the same content, with your markup applied.

• Your own GDS credentials: connect Amadeus, Sabre, Travelport and Galileo with your own PCC or office ID, one or all four.
• Priority search with fallback: choose the order sources are searched in; if one GDS does not respond, the next one is searched automatically.
• NDC and low-cost fares: shown in the same search as GDS fares, depending on the airlines and suppliers you connect.
• Start with a partner: sell through a consolidator or ticketing partner's API, then add direct IATA and GDS credentials later.
• After-sales on the booking: PNR creation, ticket issue, reissue, void and refund, with penalties and service fees posted to accounts.
• Accounts and BSP: each ticket updates the passenger file, the agent's balance and your accounts, and sales, refunds and ADMs are recorded per airline and billing period for BSP reconciliation.

GDS API integration is part of the Enterprise plan, which is a tailored contract for consolidators and groups. The flights page notes that most agencies go live with flights in two to four weeks, and the main factor is how quickly supplier credentials and certification are ready.

If you are deciding between a consolidator API and a direct GDS contract, talk to our team. We can walk through your routes, suppliers and agent network, and show the flight module and the Enterprise plan in a demo.

Frequently asked questions