Mohammad Fahim
An eSIM API lets a travel business sell mobile data plans inside its own booking flow. Your platform calls the API to search plans by country and trip length, check the traveller’s phone, place the order and receive the activation details, usually a QR code. The traveller installs it before departure and has data the moment they land.
Most pages that rank for “eSIM API” are product pages from eSIM wholesalers. They tell you coverage and brand options, but not how an eSIM sale actually works inside a travel checkout, what to check before you sell, or what goes wrong after. This guide is for OTAs, travel agencies, tour operators and travel apps adding eSIM as an extra product. The market figures come from GSMA, Juniper Research and Apple, and every Tripgic detail comes from our eSIM page and API documentation, checked this month.
What Is an eSIM API?
An eSIM is a SIM card that lives in software. Instead of a plastic card, the phone downloads a mobile profile and connects to a local network. An eSIM API is the web service that sells and delivers those profiles on your behalf.
For a travel business, the API does four jobs:
| Job | What it means |
|---|---|
| Find plans | Search data plans by destination country, trip length and data allowance |
| Check the device | Confirm the traveller’s phone can use an eSIM before they pay |
| Place the order | Buy the plan and receive the activation details |
| Serve the traveller | Show installation steps, data usage and top-up options after the sale |
The activation details can reach the traveller in more than one way. Apple’s own setup guide lists three: scanning a QR code, tapping a carrier link (on iOS 17.4 or later), or entering the details manually. Your API response decides which of these you can offer.
You do not need to run a mobile network or sign roaming agreements. A licensed provider does that. The API is what lets you sell the result under your name, in the same flow where the traveller booked the flight.
Why Travel Businesses Are Adding eSIM Now
eSIM has moved from early adopters to the mainstream, and the numbers show why travel companies are paying attention.
| Signal | Figure | Source |
|---|---|---|
| eSIM share of smartphones | 5% at the end of 2025, 10% by the end of 2026, doubling again in 2027 | GSMA Intelligence, via GSMA |
| The long view | By 2030, eSIM smartphone connections will outnumber removable SIMs | GSMA Intelligence, via GSMA |
| Operators on board | 73% of mobile operators have launched commercial eSIM for smartphones | GSMA |
| Travel eSIM revenue | $1.8 billion by the end of 2025, up 85% from $989 million in 2024 | Juniper Research |
| Devices | iPhone Air is eSIM-only; Apple says eSIM is supported by 500+ carriers | Apple |
GSMA puts the travel point plainly: connectivity decisions now happen before the traveller leaves home, which “creates space for MVNOs, fintechs, and digital-native travel brands to embed connectivity directly into their products.”
That is the opening for a travel business. You already know the destination, the dates and the traveller’s email. An eSIM seller with no booking data has to find that customer; you already have them. It is the same logic that makes seats and bags sell well inside a flight booking: the extra is relevant, timely and one tap away.
Three Ways to Sell eSIM: Reseller API, White Label, or Your Travel API
When you look for an eSIM provider, you will find three models. They suit different businesses.
| Reseller API | White-label store or app | eSIM through your travel API | |
|---|---|---|---|
| What you get | A direct API from an eSIM wholesaler | A branded web store or app the vendor runs | eSIM as one more product in the travel API you already use |
| Where it appears | Anywhere in your product, if you build it | In the vendor’s store, under your brand | In your own checkout, next to flights and hotels |
| Build effort | Medium — a new integration and data format | Low — little or no code | Low if you already use that API |
| Contracts | One more supplier | One more supplier | None extra |
| Data format | The eSIM vendor’s own | Not your concern | The same format as your other travel products |
| Best for | Telecom-focused apps and resellers | Businesses without developers | OTAs, travel agencies and travel apps |
The reseller API gives the most control, but it is a separate integration with its own format, support contact and invoice.
A white-label store is quick. The trade-off is that the eSIM sits outside your booking flow, so the traveller leaves your checkout to buy it.
The travel API route is the one most pages never mention. If your flight and hotel supplier also carries eSIM, it arrives in the same format as the rest of the trip. That is how Tripgic delivers it: eSIM “returns through the same normalized JSON schema as flights, hotels, cars, activities, lounge access, fast track, and meet & greet — so it drops straight into checkout.”
How an eSIM API Order Works, Step by Step
Every eSIM sale follows the same order. Here it is using the call names from Tripgic’s eSIM API, which has 11 endpoints.
- Search plans. Find plans for the destination and trip length (
/esim/search). - Show one plan. Load the full details of the plan the traveller picked (
/esim/single-esim-package). - Check the phone. Confirm the device supports eSIM (
/esim/compatible-devices). - Add the customer. Attach the traveller’s details (
/esim/update-customer). - Place the order. Buy the plan (
/esim/create-booking). - Deliver the install steps. Send the traveller clear instructions for their phone (
/esim/installation-instructions). - Serve the trip. Show data usage, offer top-ups and record them (
/esim/data-usage,/esim/topup-packages,/esim/topup-booking,/esim/topup-history), and read the order status (/esim/booking-details).
A plan in the response is described by a few plain fields. This abbreviated example is from our eSIM page, for a 10 GB, seven-day plan in France:
{
"destination_country": "FR",
"plan_type": "data_only",
"data_allowance_gb": 10,
"duration_days": 7,
"network": "Orange",
"speed": "5G",
"activation": "qr_code",
"confirmation": "instant"
}The field names are illustrative, as the page itself notes, so build against the production spec in the documentation. The shape is what matters: country, plan type, data, days, network, speed and how it activates. Those are exactly the things a traveller compares before choosing.
Check the Device Before You Sell
The most common eSIM refund is a plan sold to a phone that cannot use it. Two checks prevent most of them.
Is the phone eSIM-capable? Not every phone supports eSIM, and support varies by model and region. For iPhone, Apple’s guide to using eSIM abroad lists “an iPhone XS, iPhone XS Max, iPhone XR, or later.” Android support differs by manufacturer and model.
Is the phone unlocked? Apple is explicit: “To use your iPhone with another carrier when traveling internationally, your iPhone cannot be locked to a carrier.” A traveller on a carrier-locked phone can buy a plan and never be able to use it.
Build both checks into the flow, before payment:
- Ask for the phone model with a short picker, and check it against the provider’s compatible-device list.
- Ask one yes/no question about whether the phone is locked to a carrier, with a link that explains how to check.
- Show a clear message when a device is not supported, and hide the eSIM offer instead of selling it anyway.
It costs a few seconds of checkout. It saves a support ticket, a refund and, more importantly, a traveller who lands abroad with no data and blames your brand for it.
Where eSIM Fits in the Travel Checkout
An eSIM sells best when it is offered at the moment the traveller thinks about their trip. There are five natural places, and most businesses use more than one.
| Moment | Why it works | What to show |
|---|---|---|
| Booking add-on | The destination and dates are known, and the traveller is already paying | One recommended plan for the trip length, added with one tap |
| Confirmation email | The traveller reads it closely, and it is a calm moment | “Stay connected in [country]” with the plan and a buy link |
| Trip page or app | The traveller returns to it before departure | The plan, its status and the install steps |
| Pre-departure reminder | A few days before travel is when people think about data | A reminder to buy or install before leaving home |
| During the trip | Data runs out | Usage and a one-tap top-up |
Keep the offer tied to the booking. A traveller flying to France for seven days should see a plan for France for about seven days, not a list of 150 countries. Tripgic’s eSIM API can go further and recommend a plan from the itinerary: it lists “AI plan recommendation from a shared itinerary” among its features, so the traveller’s trip picks the plan.
Send the eSIM before departure, and say why. Installing needs an internet connection — Apple’s setup guide begins with “Connect your new iPhone to a Wi-Fi network or hotspot” — so a traveller who waits until landing may have no way to install it.
Choosing the Right Plans to Sell
A long plan list confuses buyers. Most travel businesses do better with a short, clear set chosen for their routes.
The main choices a plan varies on:
| Choice | Options | What travellers usually want |
|---|---|---|
| Type | Data-only, or talk and text | Data-only for most leisure trips; messaging apps cover calls |
| Duration | Daily, weekly or monthly | Matched to the trip length |
| Data allowance | A fixed amount, or a daily allowance | Enough for maps, messaging and photos |
| Network and speed | The local network the plan uses, up to 5G | A strong local network matters more than the headline speed |
| Coverage | One country, or a region | Regional plans for multi-country trips |
Tripgic’s eSIM covers 175+ countries on premium local networks with speeds up to 5G, with data-only or talk-and-text plans in daily, weekly or monthly durations.
Two details are worth explaining to travellers, because they decide whether the eSIM feels good. First, an eSIM works alongside their normal SIM. Our eSIM page puts it simply: the home number “stays active for calls, banking, and OTPs.” Second, read any fair-usage rules on daily plans before you sell them. If a plan slows down after a daily limit, say so on the offer. Travellers forgive a limit they were told about; they do not forgive one they discover abroad.
Pricing and Margin: Treat eSIM as an Ancillary
eSIM is not a big-ticket product. It works like airline seats and bags: a small amount per sale, earned on a large share of bookings.
That also means margin is under pressure. Juniper Research expects average revenue per gigabyte of travel eSIM data to reach $2.78 in 2025, down from $3.20 in 2023, and it advises providers to “increase their package value by bundling additional services.” For a travel business, that is good news. You already have the other services.
Three pricing habits work well:
- Bundle it with the trip. An eSIM offered inside a flight or package booking converts better than the same plan sold alone on a store page.
- Price by trip, not by gigabyte. “7 days in France” is easier to buy than “10 GB for 7 days.”
- Know your cost structure. Ask each provider whether their fee is a flat amount per booking or a percentage of the plan price. A flat fee keeps your margin predictable as plan prices move.
On Tripgic, fees are a flat amount per transaction, never a percentage, and eSIM is part of the plan built for platforms selling travel extras without flights or hotels. See the current figures on our pricing page.
Top-Ups, Usage and After-Sale Support
The sale is not the end of an eSIM order. The traveller uses it for days, and your system has to support that.
Usage. Show remaining data in your trip page or app. A traveller who can see they have 2 GB left does not open a support ticket asking why their data stopped.
Top-ups. Offer more data on the same eSIM before it runs out. A top-up is the easiest second sale in travel: the customer is already abroad, already installed and already trusts the plan.
Support. Most eSIM tickets fall into a few groups:
| Problem | Usual cause | Prevention |
|---|---|---|
| “It won’t install” | No internet, or a typo in manual entry | Send before departure; offer QR and manual options |
| “It installed but no data” | Data roaming off, or the eSIM line not selected | Clear, device-specific install steps |
| “My phone can’t use it” | Unsupported or carrier-locked phone | Device and lock checks before payment |
| “Data ran out” | Small plan for a long trip | Recommend by trip length; offer top-ups |
| “I want a refund” | Plan not used, or trip cancelled | Agree the refund rules with your provider first |
Refunds deserve their own question before launch. Ask each provider what happens to a plan that was bought but not installed, one that was installed but not used, and one bought for a trip that was cancelled. Put the answers in your terms, so your support team is not deciding case by case.
Local Rules: Identity Checks
Mobile connectivity is regulated country by country, and some destinations ask for identity before a plan can be used. Apple’s guide notes that “depending on local regulations, you might be asked to show identification (like your passport) to purchase.”
For a travel business, this has two consequences. First, ask your provider which destinations need identity checks and how they are handled, whether in the order, in the provider’s app, or not at all. Second, tell the traveller at the point of sale if their destination needs it. A traveller who is asked for a passport photo at checkout accepts it; one who is asked after landing, with no data, does not.
This is also a reason to prefer providers who carry the regulatory work themselves. A reseller who has to collect and store passport data for each market takes on a compliance job, not just a sales one.
What to Look For in an eSIM API: 10 Questions
Every eSIM provider claims wide coverage and easy integration. These questions separate them.
- Coverage: which countries and regions, on which local networks?
- Speed: which plans include 5G, and what is the fallback?
- Delivery: QR code, carrier link, manual entry — which does the API return?
- Devices: is there a compatible-device check in the API?
- Confirmation: is the order confirmed instantly, or can it take time?
- Top-ups: can travellers add data to the same eSIM?
- Usage: can you show remaining data inside your product?
- Refunds: what are the rules for unused and uninstalled plans?
- Identity: which destinations need identity checks, and who handles them?
- Format and fees: is the data format the same as your other travel products, and is the fee flat or a percentage?
Answer them in writing for each provider. For the broader view of choosing suppliers, see our guide on how to choose a travel API provider.
eSIM Next to Your Other Travel Extras
eSIM is one of several products a travel business can add to a booking. The logic is the same for all of them: sell what the traveller needs, when they need it, in one checkout.
On Tripgic, eSIM sits alongside activities and tours, car rental, airport transfers, and three airport services: business lounges, fast track and meet and greet. Because they share one data format, a platform that has connected one can add the next without learning a new integration.
That changes what an ancillary strategy looks like. Instead of a separate supplier for each extra, each with its own contract and format, a travel business can build one “add to your trip” step and fill it with the products that suit its customers. A business traveller might see lounge access and eSIM; a family might see a transfer and an activity. The checkout stays the same; only the offer changes. If you also sell packages, our dynamic packaging guide covers how bundles lift order value.
How Tripgic’s eSIM API Fits
Tripgic is a travel API aggregator. We are a technical intermediary, not a mobile operator: the connectivity is provided by the underlying networks, and we provide the connection, the normalized data and the developer experience.
What our eSIM API includes today, from our eSIM page and documentation:
- Plans in 175+ countries on premium local networks, with speeds up to 5G.
- Instant QR-code activation, with data-only or talk-and-text plans in daily, weekly or monthly durations.
- AI plan recommendation from a shared itinerary.
- 11 endpoints covering plan search, device compatibility, orders, installation instructions, data usage and top-ups.
- The same JSON format as our flight, hotel, car, activity and airport-service APIs, so eSIM drops into the checkout you already have.
- A free sandbox, built against the same schema you will use in production.
Our eSIM page puts the traveller’s saving at around 8× less than standard roaming. For your business, the point is simpler: an extra product your customers need, sold at the moment they book.
