A travel agent API lets a travel agency’s website or booking tool search, price and book live flights, hotels and extras directly from suppliers, instead of re-typing fares from another screen. Tripgic is a B2B travel API that gives agencies one REST integration, a free sandbox and no direct GDS contract.
This guide is written for travel agencies — high-street offices, hybrid agencies with a website, home-based networks and small agencies with or without a developer — not for large online travel agencies. It explains what a travel agent API (also called a travel agency API) does, which agencies need one, how the booking flow works call by call, whether you need a developer, what it costs, who pays whom, and how to judge one. The Tripgic details come from its live pricing page and API documentation.
What Is a Travel Agent API?
A travel agent API is a booking API: a set of calls your software sends to a supplier or an aggregator to get live travel inventory back, then price it, book it, issue it and cancel it. “API” here means application programming interface — not Advance Passenger Information, the passenger data airlines send to border authorities.
The difference for an agency is where the work happens. Without an API, an agent searches in a GDS terminal, a consolidator’s portal or an airline’s agent site, then copies the result into a quote, an email or the agency’s own system. Every step is manual, and every price can change between the search and the payment.
With an API, the same search runs inside the agency’s own website, mid-office or quoting tool. The customer or the agent sees live availability and a price, the booking is created in one flow, and the confirmation comes back as data rather than as a screen to copy.
It is also not the same as an “AI travel agent API”. That phrase describes the supply layer behind an AI assistant that books on a traveller’s behalf — a different reader, covered in our AI travel agent API guide. This guide is for agencies selling to their own customers.
Which Travel Agencies Need an API — and Which Do Not
Not every agency should build on an API. The question is how much of your selling already happens on a screen you control, and whether someone can build around the API.
| Your agency | Where you sell today | Is an API the right step? |
|---|---|---|
| Offline desk agency | Walk-in and phone, booked in a GDS terminal or consolidator portal | Usually not yet. The portal or terminal already fits the way you work |
| Hybrid agency with a website | Enquiry form online, booking done by staff | Yes, once enquiries are steady. Live prices on the site turn an enquiry into a booking |
| Home-based agent network | Many agents, one brand, shared supplier access | Yes, if the network wants one booking tool for all agents instead of shared logins |
| Agency with a developer | Own site, own mid-office | Yes. This is the setup an API is built for |
| Agency with no developer and no budget for one | Website without booking | Ready-made booking software is usually the better first step |
A useful test: count how many times a week your staff copy a fare from one screen into another. If the answer is dozens, the copying is costing you sales — prices expire, mistakes slip in, and customers who want to book at night cannot. That is the work an API removes.
An agency that is building a full consumer booking site with its own marketing, at scale, has different needs — stages, margins and conversion metrics — covered in our travel API for OTAs guide. And an agency that also builds its own packages will find the packaging side in our guide for tour operators.
Four Ways an Agency Gets Live Inventory
There are four common routes to bookable flights and hotels. Each has a different contract, a different wait and a different amount of technical work.
| Route | What you sign | Time to start | Tech needed | Fits |
|---|---|---|---|---|
| Direct GDS (Amadeus, Sabre, Travelport) | A contract, an office ID and certification — per network | Typically 6–12 months per GDS | A developer for the API; a trained agent for the terminal | Larger agencies with volume and their own ticketing |
| Consolidator or host agency | Their terms, often their ticketing | Days to weeks | Their portal; an API only if they offer one | Agencies without their own accreditation |
| Airline NDC agent portals | One agreement per airline | Varies by airline | None for the portal; a developer for a direct NDC API | Agencies that sell a few airlines heavily |
| Aggregator API | One agreement for many sources | Days, after testing | A developer or a platform built on the API | Agencies that want many sources in their own tools |
The first three are not wrong. Many agencies run a GDS terminal and a consolidator side by side for years. The difference is that each one keeps the inventory on someone else’s screen. An aggregator puts it in yours — how Tripgic does this is covered below.
One route has closed: Amadeus shut its Self-Service API portal for small developers in July 2026, so agencies that started there need a replacement. Our Amadeus Self-Service migration guide lists the options.
If you are deciding between these routes for flights in particular, our guide to GDS access for travel agents covers each one in depth, and the flight consolidator guide explains when buying through a consolidator is the better deal.
What an Agency Can Sell Through One API
Selling more than flights is where an API pays back. A customer who books a flight usually needs a hotel, often a transfer, and increasingly an eSIM. When each product lives on a different portal, staff rarely sell all four. When they sit in one search, the extras sell themselves.
| Product | What the agency sells | Tripgic page |
|---|---|---|
| Flights | GDS, NDC and low-cost-carrier fares, with branded fares and extras such as bags and seats | Flights |
| Hotels | 2M+ properties from 50+ suppliers in 190+ countries | Hotels |
| Transfers | Airport and private transfers | Transfers |
| Car rental | Rental cars at the destination | Car rental |
| Activities and tours | Things to do, tours and pre-packaged tour packages | Activities · Tours |
| Trains | Rail tickets | Trains |
| Visa | Travel visa applications | Visa |
| Airport services | Lounges, fast track and meet and greet | Airport services |
| eSIM | Mobile data in 175+ countries | eSIM |
Which products a given plan includes changes over time, so check the current list on the pricing page rather than relying on a blog post.
The point for an agency is not the length of the list. It is that one integration covers all of it, so adding hotels next year means a plan upgrade on the same integration — not a new supplier contract, a new login and a new set of screens for your staff to learn.
Using an API for a Travel Agency: The Booking Flow, Call by Call
A booking API is not one call. It is a short sequence, and knowing it helps you brief a developer and spot gaps in any provider’s documentation. Tripgic’s documentation describes the standard flow like this:
- Search. Your site sends the trip — route and dates, or city and stay — and gets back available options with prices.
- Validate. The customer picks one, and your site checks it again with the supplier. This is the price you can show as final.
- Add travellers. Names and the details the supplier needs are attached to the selection.
- Book. The booking is created and you receive its reference.
- Issue. For flights, the ticket is issued; for other products, the booking is confirmed.
- Cancel, if needed. The same API handles cancellation within the supplier’s rules.
Flights add two optional steps between search and booking: branded fares (the same flight sold as basic, standard or flexible) and ancillaries such as baggage, seats and meals.
Two details decide whether this flow works for a small agency. First, prices returned at validation and booking are final and can be shown to your customer as they are — no surprise change at payment. Second, every Tripgic product is called the same way and answers in the same format, so a developer who has built the flight flow has already learned most of the hotel and transfer flows.
Testing all of this before going live is what a sandbox is for. Our travel API integration timeline shows how long each stage usually takes.
Do You Need a Developer? Three Honest Setups
Yes — an API on its own has no screens. Something has to turn its responses into a search box, a results page and a checkout. Agencies solve that in one of three ways.
| Setup | Who builds | Good fit | Watch out for |
|---|---|---|---|
| In-house developer | Your own staff | Agencies with a website roadmap and steady volume | One person holding all the knowledge |
| Freelancer or web agency | An outside team, on your site | Agencies with a good site but no developer | Agree who maintains the integration after launch |
| Ready-made booking software | A software vendor, already connected to APIs | Agencies that want a branded booking site without code | You use the vendor’s screens and supply choices |
The first two give you the most control: your brand, your pages, your markups and your customer data. The cost is the build and the upkeep. With good documentation and a working sandbox, a focused flight-and-hotel flow can often be built in weeks rather than months, depending on scope.
If your agency wants a branded booking website without writing code, our sister product ReservationHub sells ready-made travel booking software built for OTAs, TMCs and agencies, from a cloud-hosted booking platform for agencies going online for the first time to a white-label source-code edition. That is a software purchase, not an API project, and it suits agencies whose priority is getting online rather than building their own product.
Whichever setup you choose, keep two things in your own hands: the customer relationship and your booking records. They are what let you change suppliers or software later without starting again.
Is There a Free Travel Agent API?
Partly. Most booking APIs give you a free sandbox: test credentials and test data, so a developer can build and try the whole flow without paying. Live bookings are never free, because someone has to pay the supplier and run the connection.
The APIs that really are free are often search or affiliate APIs. They return prices, but when the customer clicks to book, they leave your site and book with someone else. You may earn a small commission, but you do not own the booking, the customer or the margin, which is the opposite of what a travel agency needs.
So the useful question is not “is it free?” but “what does it cost to test, and what does it cost per booking once live?” Tripgic’s sandbox and its Live Rate Check Panel cost nothing; you pay only after you choose a plan and activate.
What a Travel Agent API Costs: The Fee Models
There is no single price for a travel agent API, because providers charge in different ways. Comparing them only makes sense against your own volume and your average booking value.
| Fee model | How it works | Good for | Risk for a small agency |
|---|---|---|---|
| Flat fee per transaction | A fixed amount per passenger, night or booking, on top of the supplier net fare | Agencies that want predictable margins | Low-value bookings carry the same fee as high-value ones |
| Percentage commission | A share of each booking’s value | Very small volumes | The fee grows with every expensive fare you sell |
| Monthly subscription | A fixed amount whether you sell or not | High, steady volume | You pay in quiet months too |
| Per call or look-to-book limits | Charges or caps on searches per booking (“look-to-book” is the number of searches allowed for each booking) | Sites with low search traffic | A busy search page can cost more than it sells |
| Affiliate or commission-back | The supplier pays you a share for sending the traveller | Content sites | You do not own the booking or the customer |
Ask every provider three questions: what you pay before the first booking, what you pay per booking, and what you pay after a booking changes — voids (cancelling a ticket shortly after issue), refunds, reissues (changing a ticket) and name changes. The third is where small agencies are most often surprised.
Tripgic uses the first model: a one-time activation, then a flat fee per transaction on top of the supplier net fare, with no percentage of the booking and no monthly subscription. Search traffic is governed by a look-to-book ratio set by your plan. Upgrading later means paying only the difference, and your integration stays intact. Current amounts are on the pricing page; our guide to travel API pricing models compares the models in more depth.
Settlement: Who Pays Whom
Settlement is the part agencies ask about least and worry about most once they are live. It answers a simple question: when your customer pays for a trip, where does the money go?
In a typical aggregator setup, your agency remains the seller. Your customer pays your agency, at the price you set — the supplier’s net fare plus your own markup. You then pay the aggregator the net fare plus its fee, and the aggregator settles with the airline, hotel or other supplier.
Tripgic runs this through a prepaid e-wallet. You keep a balance on your Tripgic account, and as each booking is created, the supplier net fare plus the flat fee is deducted from the wallet automatically. Your customers never pay Tripgic, and Tripgic stays invisible to them: you collect payment from your own customers, with the payment methods and currencies that suit your market.
Three things follow from that, and they are worth planning for before launch:
- Cash flow. A prepaid wallet means you fund bookings before your customer’s money clears. Size the balance to your busiest week, not your average one, and note that Tripgic wallet top-ups are made by bank transfer.
- Customer support. You remain responsible for support to your own customers — changes, questions and complaints come to you first.
- Post-booking costs. Voids, refunds, reissues and name changes on flights carry their own per-ticket fees. Build them into your own change fees.
Agencies that already work with a consolidator will recognise most of this; the difference is that the booking now happens in your own tools.
How to Judge the Best Travel Agent API for Your Agency
The best travel agent API for an agency is the one that covers its routes and hotels at net rates it can mark up, shows final prices before payment, includes cancellations and changes, charges a fee model that fits its volume, and offers a free sandbox. There is no single winner for every agency; seven questions separate a good fit from a bad one.
| Question | Why it matters to an agency | How to check |
|---|---|---|
| Does it cover what my customers buy? | An API is only as good as its results on your routes and cities | Run your top 20 searches in the sandbox |
| Are the rates competitive? | Coverage means nothing if your current supplier is cheaper | Compare live rates side by side before signing |
| Are prices final before payment? | Price changes at checkout lose customers and margin | Look for a validation step that returns a final price |
| Is after-sales in the API? | Cancellations and changes are a large share of an agency’s work | Check for cancel and post-ticketing calls in the docs |
| Does the fee model suit my volume? | Percentage, flat fee and subscription behave very differently | Model a normal month and a busy month |
| Can I test before I pay? | A sandbox shows how the API really behaves | Ask whether sandbox access needs a contract |
| Is there one agreement for everything? | Each extra contract is extra admin | Count the agreements behind the product list |
Do not choose from a ranked list. A provider that is right for a large OTA can be wrong for a ten-person agency, and the other way round. Our 12-point checklist for choosing a travel API provider goes deeper on each question.
How Tripgic Works for Travel Agencies
Tripgic is a B2B travel API for OTAs, travel agencies, TMCs and booking platforms — not a consumer booking site; its solutions page shows how it serves each kind of business. Its API access form lists “B2B travel agency” as a company type, and the details below come from its live site.
- No direct GDS contract or certification. You integrate one REST API instead of signing with each network. The GDS page contrasts the direct route — contract, office ID, developer onboarding and certification, typically 6–12 months per GDS — with Tripgic’s kick-off call, free sandbox, plan activation and go-live.
- Flights from several sources in one search. Amadeus, Sabre and Travelport content, airline-direct NDC and 100+ low-cost carriers — 800+ airline and low-cost connections in total, with route data covering 51,519 commercial air routes.
- Everything else through the same integration. 2M+ hotel properties, transfers, activities, trains, visas, airport services and eSIM.
- One consistent API. 73 endpoints across 8 product families; every call is a POST with a JSON body and returns one normalized response. The documentation includes code samples in PHP, Node.js and Python.
- Final prices. Prices returned at validation and booking can be shown to your customers as they are.
- A fee model built for margins. A flat fee per transaction, as explained in the cost section above; current amounts are on the pricing page.
- Check before you pay. The Live Rate Check Panel lets you compare Tripgic’s live rates with your current suppliers before any payment.
Tripgic is a technical intermediary and aggregator, not a direct travel operator: bookings are fulfilled by the airlines, hotels and other suppliers behind it. Data travels over TLS/SSL, and Tripgic’s security and compliance page covers GDPR and CCPA.
From Request to First Booking: The Onboarding Steps
The steps from first contact to a live booking are short, and nothing is charged until you choose a plan and activate. Tripgic’s pricing page lists them in this order:
| Step | What happens | What it costs |
|---|---|---|
| 1. Request access | Send the API access form or book a 30-minute demo | Nothing |
| 2. NDA | A short non-disclosure agreement | Nothing |
| 3. Live Rate Check Panel | Compare live rates with your current suppliers | Nothing |
| 4. Free sandbox | Build and test the booking flow with test credentials | Nothing |
| 5. Activation and go-live | Choose a plan; activation usually takes 3–5 business days | The one-time activation, then per transaction |
Sandbox credentials are issued after a short call, with no commitment to start, according to the contact page.
Two practical tips for agencies. Run the rate check before you brief a developer: if the rates do not beat or match your current suppliers on your real routes, no amount of good integration will fix that. And plan your first live month around one product — usually flights or hotels — before you switch on the extras.
If your agency also needs its own IATA number for ticketing in your market, that is a separate decision from the API. IATA’s accreditation page sets out the requirements, and our IATA accreditation guide explains when it matters.
Key Terms for Agency Owners
A few words come up in every conversation with an API provider. Knowing them makes the sandbox, the contract and the developer brief much easier to follow. Tripgic keeps a fuller list in its travel API glossary.
| Term | What it means for your agency |
|---|---|
| GDS | A global distribution system such as Amadeus, Sabre or Travelport, the traditional source of airline fares for agencies |
| NDC | The airline industry’s newer standard for selling fares and extras straight from the airline |
| LCC | A low-cost carrier; many of them sell outside the GDS, so you need a separate source or an aggregator |
| Net rate | The supplier’s price to you, before your own markup |
| Markup | The amount you add to the net rate, which becomes your margin |
| PNR | The passenger name record: the booking file for a flight, with its reference code |
| Void and reissue | Cancelling a ticket shortly after issue, and changing a ticket that has already been issued |
| Sandbox | A test environment with test credentials, where nothing you book is real or charged |
Common Mistakes Agencies Make When Choosing a Travel Agent API
Most problems with a travel agent API come from decisions made before the first line of code. Five come up again and again:
- Building before comparing rates. An agency spends weeks on an integration, then finds the rates on its main routes are worse than its consolidator’s. Compare live rates first.
- Choosing an affiliate API to take bookings. Search and affiliate APIs send the traveller to another site to book. They are useful for content sites, but an agency that wants to own the booking needs bookable net inventory.
- Forgetting after-sales. Search and booking get all the attention, yet cancellations, voids, refunds and name changes can take a large share of an agency’s working week. Check they are in the API and price them in.
- Ignoring cash flow. A prepaid wallet needs a balance that covers your busiest days. An empty wallet stops bookings at the worst moment.
- Handing the customer to the supplier. Keep your own booking records, customer data and invoices. They are what keep the customer coming back to you.
None of these is technical. They are business choices, and getting them right is what makes the integration pay back. If you also run a sub-agent network on your own portal, our guide to the B2B travel platform covers that model.
Next Step: Test It With Your Own Routes
The fastest way to know whether a travel agent API fits your agency is to run your twenty most common searches in a sandbox and compare the rates with what you sell today. With Tripgic that test costs nothing: book a 30-minute demo or request API access to start.
Mehedi Ahsan Ashif





