Selling with the Airalo Partner API

What the Partner API actually is

The Airalo Partner API is a REST API that lets your own software buy and manage Airalo eSIMs programmatically. It is the supply side of a reseller business and nothing else — which is both its strength and the thing most people misunderstand about it.

It is not a storefront, not a checkout, and not a business. It is a supplier you can call from code, on commercial terms you agree with Airalo directly. That last part is the reason it matters: the rate you pay is between you and them, and nobody sits in the middle adding an unpublished margin.

Access is a commercial relationship, not a signup form. You apply through Airalo Partners, and approval and rates depend on who you are and what volume you expect. Budget time for that rather than assuming you can integrate this afternoon.

What you get

The documented feature set covers the lifecycle of an eSIM as a product: discovering what is available, ordering it, delivering it, and knowing what happens to it afterwards.

• A package catalogue you can query — destinations, data sizes, durations and your rates for them.
• Order placement, which is the actual purchase of an eSIM against your account.
• Installation details for the eSIM you bought, in the formats a customer needs to get connected.
• The ability to share an eSIM with an end user, so delivery does not have to run through you manually.
• Real-time usage notifications, including when a traveller’s data is running low — which is the hook for top-up revenue that most resellers never build.

Sandbox and production, in one environment

As documented in June 2026, the API runs as a single environment with a configuration setting that switches between Sandbox and Production modes. There are no separate base URLs and no second set of credentials. Sandbox requests use the real production packages but do not provision anything or touch live data.

This is genuinely convenient and it has one sharp edge: the difference between a test order and a real purchase is a setting, not a URL. Whatever you build around this, make the current mode impossible to be wrong about by accident.

A forward-compatibility clause worth reading

Airalo reserves the right to add new attributes to requests and responses, and treats those additions as backward-compatible. That is a normal and reasonable API policy, and it puts a real obligation on you: a parser that rejects unknown fields, or a strict schema validator, will break on a change Airalo is entitled to make without warning you.

What it does not give you

This is the part no supplier documentation covers, and the reason integrations take three months rather than the weekend people budget. Everything below sits between the API and a customer with money.

None of it is exotic. All of it is real work, and most of it is work you will still be doing in year two, because a storefront is never finished.

Integrating it yourself, or not

There are three honest ways to sell Airalo eSIMs under your own brand, and the right one depends on what you already have rather than on which is technically purest.

Build the whole thing

Correct when eSIMs are one product inside a larger system you already run — a travel booking platform, an airline app, an existing marketplace. You have the checkout and the customer already; the API is a supplier you plug into a machine that exists.

Use a wholesaler’s ready-made store

Correct when you want to be selling this week and do not want a provider relationship at all. You give up control of your cost of goods in exchange for having none of the above to build.

Bring your own keys to a platform

The middle path, and the one Esimbit exists to serve: you hold the Airalo account and the rate you negotiated, and the storefront, checkout, catalogue, delivery and order records are software you rent. Your keys stay yours, so does your gateway, and the platform takes no cut of a sale.

The honest test between the first and the third: if you would not otherwise employ someone to maintain a storefront, do not acquire one as a side effect of an API integration. If you already do, buying the layer twice is waste.

• What bring-your-own-keys means in practice →
• How Esimbit works →

Getting started, in order

Whichever route you pick, the first three steps are identical, and they are worth doing before you write any code or subscribe to anything.

1. Apply for a partner account with Airalo Partners and get to the point where you can see real rates. Everything downstream depends on numbers you do not have yet.
2. Pick the five packages you actually expect to sell — usually one region and a handful of popular destinations — and write down their partner rates.
3. Set a retail price for each and carry it down past the gateway fee to a contribution figure, so you know the business works before you build it.
4. Only then choose between building, renting or buying the layer above the API.
5. Connect in sandbox mode first, place test orders, and verify that your integration tolerates response fields it has never seen.
6. Switch the mode setting to production, place one real low-value order, and check the eSIM installs on an actual phone before you sell one to a stranger.

The fifth and sixth steps are the ones people skip. An eSIM that provisions correctly in an API response and fails to install on a real handset is a support ticket you will get at two in the morning, in a language you do not speak, from someone standing in an airport.

• Connecting a provider account →
• Using the Esimbit API →