A B2B travel platform is an online booking system that sells flights, hotels, transfers, activities and other travel products to travel businesses at net rates, not to travellers. Agents log in, search live inventory, book and pay, then resell to their own customers at their own price. The platform is usually run by a wholesaler, consolidator or large agency.

This guide is for travel companies that want to run a B2B platform, and for the developers who will build one. It explains how the B2B side of travel works, the features every agent portal needs, how the money flows, the three ways to get a platform, and how to choose the API that supplies it. The Tripgic details come from our homepage, solutions page, API documentation and pricing page, read on 3 October 2026.

B2B, B2C and Corporate Travel: Three Different Things

Search for “B2B travel” and you get two kinds of answer. One is about selling travel to the travel trade. The other is about booking work trips for employees. They share a name and almost nothing else.

B2B travel platform B2C travel site (OTA) Corporate travel tool
Who books Travel agents and resellers The traveller A company’s employees or travel manager
Price shown Net rate, before the agent’s markup Retail price, all-in Negotiated or retail, inside a policy
How it earns Markup on net rates, sometimes a fee Markup or commission per booking Usually fees paid by the company
Key features Agent accounts, credit limits, markup rules Checkout, reviews, payments Approvals, policy rules, expense reports
Who pays The agency, often on credit or deposit The traveller, by card The company

This guide is about the first column. If you need the third, our guide to the corporate travel API covers it.

Who Uses a B2B Travel Platform

A B2B platform sits in the middle of the travel trade. Products flow from suppliers, through one or more businesses, to the agent who serves the traveller. Each business in that chain may run its own platform, or use someone else’s.

Role What it does Why it needs a B2B platform
Wholesaler Contracts hotels, packages and services in volume To sell that inventory to many agencies at once
Consolidator Holds airline agreements and sells fares to agents To give agents fares they cannot get alone. See our guide to the flight consolidator
Bedbank Aggregates hotel rooms at net rates To distribute rooms to OTAs, agents and tour operators
DMC Runs ground services in one destination To sell transfers, tours and hotels to foreign agents. See travel API for DMCs
Agency network or host agency Supports many small or home-based agents To give every member one place to book
Retail agent Serves the traveller It is the buyer: it logs in and books

The more agents a business supplies, the more a self-service platform saves. Without one, every quote is a phone call or an email, and every booking is typed in by hand.

How a B2B Travel Platform Works

Every B2B platform has two layers. The top layer is the agent portal: what an agent sees and clicks. The bottom layer is supply: the connections to airlines, hotels and other suppliers that return live prices and confirm bookings.

A single booking passes through both layers in a fixed order:

  1. Search. The agent enters a route, a city or dates. The portal sends the search to every connected supplier.
  2. Price. Results come back at net cost. The portal applies the platform’s markup for that agent and shows the agent price.
  3. Validate. When the agent picks an option, the platform re-checks price and availability with the supplier, because fares change between search and booking.
  4. Book. The agent adds traveller details. The platform creates the booking and takes payment from the agent’s credit line or deposit.
  5. Issue. The supplier issues the ticket or voucher, and the portal shows it to the agent.
  6. Service. The agent views the booking later and cancels it if needed, inside the supplier’s rules.

In short, a B2B booking has six steps: search, price, validate, book, issue and service. The portal adds the markup; the supply API confirms the price and makes the booking. The portal decides who sees what price. The supply layer decides what can be sold at all. A good platform needs both, but they are different kinds of work, and most teams are strong at only one of them.

Core Features of a B2B Travel Portal

A B2C site needs a good checkout. A B2B portal needs to manage many businesses, each with its own prices, money and staff. These are the features buyers expect.

Feature What it does
Agent onboarding Registers agencies, checks their documents and approves them before they see net rates
Sub-agents and users Lets one agency add staff or branches, each with its own login and rights
Markup rules Sets the platform’s margin per agent, product, airline, destination or date
Credit limits and deposits Lets agents book on credit up to a limit, or from a prepaid balance
Multi-product search Flights, hotels, transfers and activities from one search box
Booking queue Shows every booking with its status: on hold, confirmed, ticketed, cancelled
Invoices and statements Produces invoices per booking and monthly statements per agent
Agent branding Lets agents print vouchers and itineraries under their own name
Reports Shows sales by agent, product and margin

Most of these features are about control of money: who may book, on what credit, at what margin. That is the real difference between a B2B portal and a consumer booking site. A consumer usually pays at checkout. An agent may book fifty trips this month and pay at the end of it.

Who Does What: Your Portal and the Supply API

When you build on a travel API, the work splits cleanly. The API handles everything that touches a supplier. Your portal handles everything that touches an agent. Knowing the line saves months of building the wrong thing.

Job Your portal The supply API (e.g. Tripgic)
Agent sign-up, approval and users ✅ —
Markup rules per agent and product ✅ —
Credit limits, deposits and agent payments ✅ —
Invoices, statements and reports for agents ✅ —
Support for your agents ✅ —
Search across many suppliers — ✅
Merging duplicate results from different sources — ✅
Re-checking price and availability before booking — ✅
Creating the booking with the supplier — ✅
Issuing the ticket or voucher — ✅
Booking details and cancellation — ✅
Technical support for the API — ✅

The left column is where you compete: it decides how agents feel about your platform. The right column is plumbing that every platform needs and no agent sees. That is the part worth buying rather than building.

How a B2B Travel Platform Makes Money

The basic model is simple. The platform buys at net, sells to the agent at net plus its margin, and the agent sells to the traveller at a higher price again.

Here is an illustrative hotel night, with made-up numbers:

Step Amount Who keeps the difference
Supplier net rate 100 The hotel and its supplier
Price the platform shows the agent 108 The platform keeps 8
Price the agent shows the traveller 120 The agent keeps 12

Real platforms make this more detailed. A large agency that books every day may get a lower markup than a new one. A hard-to-find route may carry a higher margin than a busy one. Some platforms add a monthly fee for the portal itself, and some sell the agent’s branded booking site as an extra.

Two costs eat into the margin. The first is the supply cost: what you pay your API providers or suppliers per booking. The second is credit risk: an agent who books on credit and pays late, or never. Good credit rules matter as much as good markups. Our guide to travel API pricing models explains how supply costs are usually charged.

Why a Flat Supply Fee Suits a B2B Platform

How your supply provider charges you matters more in B2B than in B2C, because your margin is thinner. You share the gap between net and retail with your agents, so every cost has to be predictable.

There are two common ways a supply provider can charge per booking:

Fee type How it behaves What it means for a B2B platform
Percentage of the fare Grows with every rise in the fare A business-class ticket or a long hotel stay costs you much more in fees, though your own markup may not grow
Flat fee per transaction The same amount whatever the fare You know your cost per booking in advance and can set agent markups with confidence

Tripgic uses the second model. Its pricing page states that it “returns supplier net fares and applies a single fixed markup per transaction — always a flat amount … never a percentage commission”. The fee sits on top of the supplier’s net fare, and there is a one-time activation fee when you go live. The current figures are on the pricing page.

The practical result is that a high-value booking does not carry a high-value fee. For a platform selling long-haul and premium fares to agents, that difference adds up quickly.

Three Ways to Get a B2B Travel Platform

There is no single right answer. It depends on whether you want to sell your own inventory to agents, or just book for your own customers.

Option What you get What you control Best for
Rent a login on an existing B2B portal Instant access to someone else’s supply, at their prices Almost nothing; you are their agent A retail agency that only needs to book
License white-label portal software A ready agent portal under your brand Your brand, agents and markups; supply depends on what the software connects to A wholesaler or consolidator that wants to launch quickly
Build your own portal on a travel API Your own portal, connected to supply through an API Everything: features, prices, agent terms and data A business with its own tech team and a clear idea of its agents

Some businesses mix the second and third options. They license the portal and connect it to their own supply through an API, so they are not limited to the software vendor’s suppliers.

If you want your own brand in front of agents, read our guide to the white-label travel API. For the full cost comparison, see build vs buy a travel API.

The Hard Part: Where the Supply Comes From

The portal is software you can plan and build. Supply is harder, because each source comes with its own contract, format and approval process.

Supply route What it takes
Direct GDS (Amadeus, Sabre, Travelport) A contract and certification for each one; 6–12 months per integration
Airline NDC A separate connection per airline, or an NDC aggregator
Low-cost carriers Often not in the GDS at all; each needs its own connection. See our low-cost carrier API guide
Hotel suppliers and bedbanks A contract and integration per bedbank, then room mapping to merge them
Transfers, activities, eSIM More suppliers, more contracts
Travel API aggregator One contract and one integration for many of the above

With 6–12 months for each direct GDS integration, a platform that connects every source one by one can spend its first year on plumbing, not on agents. It also has to merge results: the same hotel from three suppliers must show as one hotel, not three. Our guide to hotel room mapping shows why that is harder than it looks.

This is why it often makes sense to start with an aggregator and add direct contracts later, only where volume justifies them. Our explainer on the travel API aggregator covers how that works.

How Tripgic Fits a B2B Travel Platform

Tripgic is the supply layer, not the agent portal. Its own site lists B2B booking engines and white-label SaaS providers among the businesses it is built for. You build or license the portal; Tripgic gives it inventory through one REST API.

  • One API, many products. 73 endpoints across 8 product families: flights, hotels, activities, tour packages, trains, transfers, eSIM and visas.
  • Flights from three GDS networks (Amadeus, Sabre and Travelport), airline NDC content and 67 low-cost carriers, with 700+ airline and LCC connections in total.
  • Hotels: 2M+ properties from 50+ suppliers, in the same normalized schema as the rest of the inventory.
  • Merged results. Cross-source de-duplication, with the best price ranked first.
  • Final prices. Prices on the validation and booking endpoints are final, so your platform knows its exact cost before it adds its own markup for each agent.
  • One consistent booking flow across products: search, validate, add traveller details, create the booking, then issue it and, where the product allows, cancel it.
  • Prepaid deposit funding with automatic top-ups, which matches the way many B2B platforms already take deposits from their own agents.
  • Enterprise security: encryption, audit logging, IP whitelisting and rotatable API keys, with GDPR and CCPA compliance. See our travel API security guide for what to ask any provider.

Tripgic is a technical intermediary, not a travel operator: suppliers fulfil the bookings, and your platform keeps the relationship with your agents.

What a B2B Platform Can Sell Through Tripgic

Agents earn more when they can sell the whole trip from one place. This is what the Tripgic API documentation covers today, product by product.

Product family Endpoints What your agents can sell
Flight API 15 GDS, NDC and low-cost fares, branded fares, baggage, seats and meals, ticket issue and cancellation
Hotel API 11 Hotel search, room availability, property details, booking, voucher issue and cancellation
Activity API 7 Sightseeing, tours, attractions and experiences
Tour Package API 9 Pre-packaged tours: city suggestions, search, details, ordering and order issue
Train API 8 Rail journeys: search, fare check, booking and cancellation
Transfer API 6 Private and airport transfers
eSIM API 11 Data plans in 175+ countries, top-ups, usage checks and installation steps
Visa API 6 Visa packages: search, check and order

For a B2B platform, the extras matter as much as the flight. An agent who books a flight and a hotel can add a transfer, a tour and an eSIM to the same trip, and earn on each one. Our guides to the dynamic packaging API, the tours and activities API and the eSIM API go deeper on each.

How Your Portal Connects to Tripgic

For the developers on your team, the connection is plain REST. Every endpoint is a POST to one base URL, https://sandbox.api.tripgic.com/v1/, and every call carries two headers: apikey and secretecode. Both are issued during onboarding.

A flight search looks like this, taken from the documentation:

curl -X POST https://sandbox.api.tripgic.com/v1/flight/search \
  -H "apikey: YOUR_API_KEY" \
  -H "secretecode: YOUR_SECRET_CODE" \
  -H "Content-Type: application/json" \
  -d '{ "journey_type": "OneWay", ... }'

Every response uses the same envelope: status, data, message and value. A search returns a tracking_id, which you pass to the validate and booking steps that follow. Common request fields include partner_id and language, and every price carries an explicit currency.

Your markup engine sits between the validated price and the agent’s screen. In plain terms:

agent_price = tripgic_final_price + your_markup(agent, product, route)

Because the validated price is final, the only number your portal has to calculate is its own margin. That keeps the markup engine small, testable and easy to explain to agents.

How to Choose a B2B Travel API

Whether you are a wholesaler building a portal or a startup building a B2B booking engine, the API you choose sets the limits of what your agents can sell. Seven questions separate a good fit from a costly one.

Question What a good answer looks like
Does it cover my markets? Real results for your top 20 routes and cities, not just a large total
How many products? Flights and hotels at least; extras such as transfers, activities and eSIM for higher booking value
How does it charge? A model you can price agents on. A flat fee per booking is easier than a percentage
Are prices final at booking? The validated price should be the price you pay, so agents are not surprised
Can I test before I pay? A sandbox with real flows: search, validate, book, issue, cancel
How fast can I go live? Days or weeks, not 6–12 months
Who answers when it breaks? A named support channel with a stated response time

For Tripgic, the answers are on its own pages: sandbox credentials are issued right after a short kick-off call, with no commitment to start; activation for live use usually takes 3–5 business days; and the contact page gives a technical support response time by email of under 24 hours on business days. Our guide to choosing a travel API provider covers each question in more depth.

How to Launch a B2B Travel Platform in Six Steps

  1. Pick your agents first. Write down who will book: retail agencies in one country, tour operators, corporate agencies. Their needs decide the features and the products.
  2. Choose your products and markets. Flights only, hotels only, or both plus extras. List your top 20 routes and destinations.
  3. Decide build, license or both. Use the table above. Be honest about your team’s size.
  4. Connect supply and test it. Get sandbox access and run your top 20 searches through the full flow, not just search.
  5. Set agent terms. Markup rules, credit limits, deposit rules and cancellation terms. Put them in writing before the first agent signs up.
  6. Start small. Onboard five to ten agents, watch every booking for a month, then open to more.

The supply connection can take days or weeks. The agent side, meaning onboarding, credit and finance, usually takes longer to get right. Our integration timeline guide shows a realistic schedule.

Six Mistakes New B2B Travel Platforms Make

Many problems on a new B2B platform are not technical. They are about rules: who gets credit, what margin, what happens when a booking goes wrong.

  • Giving credit too early. A new agent should start on deposit. Credit is earned with a payment history, not granted at sign-up.
  • One markup for everyone. A single margin is too high for big agents and too low for hard routes. Plan for rules per agent and product from day one.
  • Ignoring re-pricing. Fares change between search and booking. If your portal does not re-check the price before taking payment, someone loses money on every change.
  • Too many products at launch. Start with what your first agents actually sell. Add products when they ask for them.
  • No written cancellation policy. Agents need to know who handles a cancellation, what it costs and how fast money comes back, before the first one happens.
  • Building every supplier connection by hand. Each one adds a contract, a format and a maintenance job. Start with one aggregator and add direct connections only where volume pays for them.

What to Check Before You Choose a B2B Platform or Supplier

Whether you are an agent choosing a portal, or a wholesaler choosing a supply partner, the same questions apply. Ask for the answer in writing, and test with real searches.

Check Why it matters
Real supply for your markets A big total means nothing if your routes and cities are thin
Net price and fee clarity You must know your cost per booking to set a margin
Price at booking matches price at search Repricing at checkout costs agents money and trust
Payment terms Credit, deposit or card, and what happens when a payment fails
Cancellation rules Who handles a cancellation, and how fast the money comes back
Your own markups Whether you can set your own margin per agent and product
Support Who answers when a booking fails, and how quickly

The best B2B portal is not a name on a list. It is the one whose supply, prices and terms fit your agents.

Final Thoughts

A B2B travel platform is two things joined together: an agent portal that controls who books at what price, and a supply layer that makes the bookings real. The portal is where you compete. The supply layer is where most projects lose time.

If you are building a B2B platform, start your supply with one API and spend your effort on the agent experience. Test real searches in a sandbox before you sign anything, and choose a supply fee you can build agent prices on.

Book a Tripgic demo and get sandbox access →