A travel insurance API lets a booking platform quote, sell and issue a real insurance policy during checkout, using the trip details it already holds — dates, destination, travellers and trip cost. The insurance comes from a licensed insurer or provider; the trip comes from the platform’s own booking supply. Tripgic supplies that trip side — flights, hotels, transfers and activities through one API — so the booking data a quote needs is already in one format.

This guide explains how a travel insurance API works, which covers you can sell, the licensing and selling rules, how to design the checkout step, how to integrate, and how to choose a provider.

What Is a Travel Insurance API?

A travel insurance API is a connection between a travel platform and an insurance provider that works in real time. It does three jobs:

  1. Quote — price cover plans for a specific trip and set of travellers.
  2. Sell — buy the chosen plan during checkout.
  3. Issue and service — return a policy number and documents, and handle cancellations.

Travel insurance protects against the financial risks of a trip: cancellation, medical costs abroad, lost bags, delays. The API turns that product into data a checkout can show and sell.

Who provides travel insurance APIs

Provider type What it offers
Insurers Their own products, sometimes through a direct API
Brokers and intermediaries Products from several insurers through one connection
Insurtech platforms Embedded insurance APIs built for online checkouts, often across countries
Assistance companies Medical and travel assistance, often bundled with insurance

“Embedded insurance” is the common name for this model: insurance offered inside another company’s purchase flow rather than sold separately.

How a Travel Insurance API Works

Travel insurance API flow: send trip details, get quote, show plans, buy policy, issue cover

1. Send trip details

The platform sends what the quote depends on:

Field Why the insurer needs it
Country of residence Decides which products may be sold and under which rules
Destination Medical costs and risks vary by region
Departure and return dates Length of cover
Traveller ages Risk, especially for medical cover
Trip cost Sets the cancellation cover amount
Booking date Some covers must be bought soon after booking

2. Receive quotes

The API returns one or more plans, each with a price, the covers included, limits, excess and a link to the policy wording.

3. Show the options

The checkout shows the plans in a short, clear form. The traveller chooses one or declines.

4. Buy the policy

The platform sends traveller names, dates of birth, contact details and payment — or confirms that it collected the premium on the insurer’s behalf, depending on the agreement.

5. Receive the policy

The API returns a policy number, documents and the claims contact. The platform stores the policy with the booking and sends the documents to the traveller.

A generic quote request

Most insurance APIs accept JSON over HTTPS. A quote request might carry fields like these (a generic example, not any one provider’s format):

{
  "residence_country": "GB",
  "destination_region": "worldwide_excl_usa",
  "start_date": "2026-12-10",
  "end_date": "2026-12-17",
  "travellers": [{ "age": 41 }, { "age": 38 }],
  "trip_cost": { "amount": 1850, "currency": "GBP" }
}

The fields map directly to the booking your platform has just priced, which is why insurance is easiest to add where the trip data is already clean and complete.

What Cover You Can Sell

Travel insurance cover types: trip cancellation, medical, baggage, trip delay, cancel for any reason

Cover What it pays for
Trip cancellation Non-refundable costs if the traveller must cancel for a covered reason
Trip interruption Unused costs and extra travel if the trip is cut short
Emergency medical Treatment abroad, often the most important cover
Repatriation Bringing the traveller home for medical reasons
Baggage Lost, stolen or damaged luggage and belongings
Travel delay Costs from long delays
Missed connection Extra costs when a delay causes a missed connection
Cancel for any reason A partial refund for cancelling for reasons not otherwise covered

Cancel for any reason

“Cancel for any reason” (CFAR) cover is common in some markets, especially the United States. It usually refunds part of the non-refundable cost — commonly around half to three-quarters — and often must be bought within a short time after the first trip payment. Because the rules differ by provider, show them plainly at checkout.

Plans, not single covers

Most providers sell bundled plans — for example a basic plan with medical and cancellation, and a fuller plan with higher limits and more covers. Two or three plans are easier for a traveller to choose from than a list of single covers.

Why Travel Businesses Add Insurance

  • Revenue without inventory. A commission on each policy, with no stock to buy.
  • Higher value per booking in a checkout the traveller is already completing.
  • Less pressure on support. Insured travellers whose trips go wrong have somewhere to claim.
  • Trust. Offering protection signals that the seller expects to stand behind the trip.
  • Fewer refund disputes. Clear cover helps when a non-refundable booking is cancelled.

The value depends on the trip. A long-haul family holiday benefits more from cover than a short domestic flight, and the checkout should reflect that.

The Rules on Selling Travel Insurance

Insurance is regulated almost everywhere, and the rules shape how a travel platform can sell it.

Who may sell

In the European Union, the Insurance Distribution Directive (EU) 2016/97 governs insurance sales. It allows lighter treatment for some “ancillary” sellers — such as travel companies selling cover linked to the trip they sell — when conditions on the product and premium are met. Other countries have their own versions; many US states, for example, have limited licences for travel retailers.

In practice, most travel platforms sell through a licensed insurer, broker or insurtech that holds the approvals, and act as an introducer or ancillary seller under its arrangements.

How it may be sold

  • No pre-ticked boxes. In the EU, the Consumer Rights Directive does not allow extra paid options to be added by default; the traveller must actively choose.
  • Clear information about what is and is not covered, before purchase.
  • Policy documents and key information in a set form in many markets.
  • Cooling-off rights to cancel the policy within a period in many markets.

Where the traveller lives matters

Insurance is usually regulated by the traveller’s country of residence, not the destination. A platform selling to travellers in ten countries needs a provider that can sell in all ten — which is the honest answer to “can one API cover several countries?”

This section is general information, not legal advice. Confirm the rules for each market with your provider and adviser.

Designing the Insurance Step at Checkout

Where to place it

Placement Effect
After the trip is chosen, before payment The usual and most effective place
On the payment page Works, but competes with payment details
After booking, by email Lower take-up, but useful for travellers who declined

How to show it

  • Two or three plans, side by side, with the price per trip.
  • A one-line summary of each plan’s main covers.
  • A clear “no thanks” option, as visible as the plans.
  • Links to full terms, opened without losing the checkout.
  • The total price updated when a plan is chosen.

What to avoid

  • Pre-selected insurance.
  • Fear-based wording that suggests the trip is unsafe.
  • Hiding the decline option.
  • Long policy text in the checkout itself.

A clear, honest choice keeps both regulators and travellers on side, and tends to produce better long-term results than pressure.

A Worked Example: One Booking, One Policy

A couple living in the UK books a week in Dubai on an online travel agency: return flights and a hotel, with a total trip cost of £1,850.

  1. The trip is priced. The OTA’s booking API confirms the flights and hotel at their final price.
  2. The quote is requested. The OTA sends residence (UK), destination, dates, two travellers’ ages and the £1,850 trip cost to its insurance provider.
  3. Plans come back. The provider returns two plans: a standard plan and a fuller plan with higher medical and cancellation limits.
  4. The traveller chooses. The checkout shows both plans with one-line summaries and a clear “no insurance” option. The couple choose the standard plan.
  5. Payment. The total now includes the premium. Payment is taken once.
  6. The policy is issued. The provider returns a policy number and documents. The OTA stores them with the booking and includes them in the confirmation email.
  7. The trip changes. A month later the couple move the trip by two days. The OTA’s change flow updates the flights and hotel, then calls the provider to update the policy dates.
  8. A claim. A bag is delayed on arrival. The traveller finds the claims contact in their booking and claims directly with the insurer.

Every step depends on clean booking data — the trip cost, dates and travellers — flowing from the booking side to the insurance side without re-typing.

Integrating a Travel Insurance API: Step by Step

  1. Choose a provider that can sell in your travellers’ countries of residence.
  2. Agree the commercial model — commission, who collects the premium, settlement.
  3. Get sandbox access and read the documentation.
  4. Map your booking data to the quote fields: residence, destination, dates, ages, trip cost.
  5. Build the quote call and display.
  6. Build the purchase call, with traveller details and payment handling.
  7. Store the policy with the booking and send documents.
  8. Handle changes — trip date changes, cancellations, policy cancellation within the cooling-off period.
  9. Test failures — quote timeouts, failed purchases, payment declines.
  10. Go live and measure.

When the trip changes

If a flight date changes or the booking is cancelled, the policy may need to change too. Agree with the provider which changes the API supports — date changes, adding travellers, cancellation — and connect them to your booking changes so the two never drift apart.

Choosing a Travel Insurance Provider

Question Why it matters
Which countries of residence can you sell to? Decides where you can offer cover
Which insurers stand behind the products? Claims are paid by the insurer
Who handles claims, and how? The traveller’s experience after a problem
What is the commission and settlement process? Your revenue and cash flow
Is the premium collected by us or by you? Affects payment flow and regulation
What does the API support after sale? Changes, cancellations, documents
Is there a sandbox? Developers can test before signing
What compliance support do you give? Wording, disclosures, training

Matching Cover to the Trip

The same plan does not suit every booking. A good checkout adjusts what it shows:

Booking What travellers usually care about What to show first
Short domestic flight Delay, missed connection A light plan, or none
Long-haul flight Medical abroad, cancellation, baggage A full plan
Hotel only Cancellation of a non-refundable stay Cancellation-focused cover
Package holiday Cancellation, medical, baggage for the whole family A full plan per traveller
Group or school trip Cancellation for many travellers, medical Group plans, if the provider offers them
Business trip Often covered by an employer’s annual policy A clear decline option

Showing a full holiday plan on a one-hour domestic flight wastes the traveller’s attention. Many providers can return different plans for different trip types; use that.

Insurance and Package Travel Are Different Protections

Travellers often confuse two protections that a travel company may be involved in:

Travel insurance Package travel protection
What it covers The traveller’s own risks: illness, cancellation for covered reasons, lost bags The seller’s failure: if the organiser goes bust, travellers are refunded or brought home
Who pays The traveller, as a premium The organiser, as a legal requirement in many markets
Who provides it An insurer Insolvency protection schemes, bonds or insurance taken by the organiser
Optional? Usually optional Required for packages in the EU and UK

If you sell packages, you may need insolvency protection whether or not you sell travel insurance. See our dynamic packaging guide for the package rules, and make sure your checkout does not suggest that travel insurance replaces them.

Insurance in B2B and Agency Platforms

Travel agencies and B2B portals sell insurance too, with a few differences:

  • The agent advises. In many markets an agent who recommends cover takes on advice duties; offering clear options without advice is simpler.
  • Commission sharing. A B2B platform may share insurance commission with the agencies that sell through it.
  • Corporate clients often hold annual policies, so the agent needs a quick way to mark a booking as already covered.
  • Group bookings need cover for many travellers in one purchase.

A B2B insurance flow should let the agent quote, sell and download documents without leaving the booking screen, and show the commission earned.

What Happens When a Traveller Claims

Claims are handled by the insurer or its claims team, not by the travel platform. But travellers often contact the seller first, so plan for it:

  1. Give the claims contact in the confirmation and in the traveller’s account.
  2. Provide booking evidence quickly — invoices, cancellation confirmations, flight change notices.
  3. Do not promise outcomes. Only the insurer decides a claim.
  4. Track complaints and share them with the provider.

The claims experience shapes how travellers feel about the trip and the seller. Ask providers for their claims process and timings before signing.

Personal Data and Privacy

Selling insurance means sharing traveller data with the provider:

  • Share only what the quote and policy need — names, dates of birth, residence, contact details, trip details.
  • Tell travellers in your privacy notice that their data is shared with the insurance provider when they buy cover.
  • Agree data roles with the provider: who is responsible for what under data protection law such as the GDPR.
  • Secure the connection and keys, as with any travel API. Our travel API security guide covers the basics.

Medical information is usually collected by the insurer directly, not by the travel platform — keep it that way.

Key Terms

Term Meaning
Premium The price the traveller pays for the policy
Excess (deductible) The amount the traveller pays towards a claim
Limit The maximum the policy pays for a cover
Policy wording The full terms of the policy
Attach rate Share of bookings that add insurance
Embedded insurance Insurance offered inside another company’s checkout
Cooling-off period Time in which the traveller can cancel the policy
Ancillary insurance intermediary A business, such as a travel seller, that offers insurance linked to its main product

Measuring Results

  • Attach rate — share of bookings that add insurance.
  • Attach rate by trip type — long-haul, family, short domestic.
  • Revenue per booking from insurance.
  • Cancellation rate of policies in the cooling-off period.
  • Complaints and claims experience, from the provider.

A high attach rate with many cooling-off cancellations or complaints suggests the checkout is pushing too hard.

Common Mistakes

  • Selling where the provider is not allowed to sell.
  • Pre-ticking insurance, or making the decline hard to find.
  • Wrong trip data — ages or trip cost — leading to wrong cover.
  • No link between booking changes and the policy.
  • Too many plans that confuse the traveller.
  • Ignoring claims experience, which is what travellers remember.

How Tripgic Fits

An insurance quote is built on the trip. Tripgic supplies that trip through one API:

Every product returns the same JSON envelope, as the API documentation shows, so the dates, destination, travellers and total cost of a booking are in one consistent shape — ready to send to an insurance provider’s quote call. Testing starts in a free sandbox, and the fee model is on the pricing page.

Final Thoughts

A travel insurance API turns the end of a booking into a chance to protect the trip and earn more from it. The integration itself is simple: send trip details, show plans, buy, store the policy. It works best when the booking data behind it is complete and consistent, because every field in the quote comes from the trip. The care goes into choosing a provider licensed for your travellers’ countries, designing an honest checkout step, and keeping the policy in step with the booking.

If you are building the booking side that insurance attaches to, book a demo with Tripgic and test the API in the sandbox first.