Airhub’s eSIM API lets you sell eSIMs in 190+ countries under your own brand. Here’s what the API does, how integration works, how it’s secured, and how to get access.
Adding eSIM connectivity to your product really comes down to one decision. You can go the hard way negotiate with carriers one country at a time, each with its own contract, billing, and provisioning quirks or you can plug into a single eSIM API that has already done that aggregating for you. The Airhub eSIM API is the second route: one integration, 190+ countries, sold under your own brand rather than ours. What follows is the part that actually matters when you’re evaluating a provider what the API does, how you integrate it, how it’s secured, and how the money works rather than a list of reasons we think we’re great.
What Is an eSIM API? (and How Reselling Works)
An eSIM API is a set of endpoints that let your platform buy and provision eSIM data plans in code no physical SIMs, no carrier negotiations. Strip reselling down to its mechanics and it’s really just four moves your system makes:
- Browse the catalogue — pull the available plans (by country, region, or operator), each with its data, validity, and wholesale price.
- Create an order — buy a plan for a customer. The API hands back an eSIM profile, identified by its ICCID.
- Deliver activation — retrieve the QR code / activation code (an SM-DP+ profile) and pass it to your customer, who scans it to go live.
- Track status — take webhook callbacks for events like install, activation, and usage, so your app always knows where each eSIM stands.
That’s the entire loop. Your customer sees your brand and your prices; the carrier relationships and the provisioning all happen out of sight on Airhub’s side.
How the Airhub eSIM API Works Integration in a Few Steps
None of this will feel exotic to anyone who’s worked with a REST API it follows the standard reseller pattern:
- Get API access. Request partner/API access and you’ll get credentials for a sandbox to build against.
- Authenticate. Every request is authenticated using your API credentials.
- Build against the sandbox. Run the whole flow catalogue → order → QR → webhooks on test credentials, with no real money moving.
- Fetch the catalogue, create orders, retrieve QR codes through the API’s endpoints.
- Wire up webhooks for real-time status.
- Go live. Swap to production credentials and start selling.
Coverage, Operators & Plans
The catalogue spans 190+ countries local, regional, and global plans your customers can buy in whatever shape fits the trip, from a short data pack to a multi-week bundle, data-only or with voice and SMS.
Security & Compliance
If you’re pushing customer data through someone else’s API, security isn’t a footnote it’s usually the question that decides the deal. So here’s how Airhub handles it, plainly:
- Authenticated requests : every call is authenticated with your credentials.
- Verified webhooks : status callbacks help your system track updates in real time.
- Data handling : customer and transaction data is handled in line with applicable privacy law.
Provisioning runs on the GSMA Remote SIM Provisioning standards that underpin eSIM everywhere.
White-Label & Business Models
Here’s a thing almost no partner wants: “powered by Airhub” sitting in front of their customers. They want their own brand and the API is built for exactly that. White-label selling means your name, your prices, your checkout, with Airhub kept firmly in the background. Where that lands depends on what you’re building:
- Travel & OTA platforms / airlines :drop an eSIM into the booking flow as an add-on.
- Telcos & MVNOs : extend coverage abroad without signing new carrier deals.
- Super-apps & fintechs : add connectivity as one more service in the app.
- Agencies & niche resellers : stand up a dedicated eSIM store of your own.
And the money? In most setups you buy plans at wholesale and set your own retail margin on top.
Why Businesses Build on Airhub
Set the sales adjectives aside here’s what genuinely moves the needle when you’re picking an eSIM API provider, and where Airhub actually stands:
- One integration, 190+ countries — one build instead of a stack of carrier contracts.
- Fast provisioning — profiles activate quickly, so customers are online not long after they pay.
- White-label by default — your brand out front, ours out of sight.
- Sandbox plus real support — test the whole thing before you commit a line of production code, with a partnerships team on hand for the launch.
- Room to scale — start small, grow, and never re-platform to do it.
FAQs
1. What is an eSIM API?
A set of endpoints that let your platform buy and provision eSIM data plans in code browse a catalogue, create an order, deliver the QR/activation code, and track status via webhooks so you can resell eSIMs under your own brand without touching physical SIMs or carrier contracts.
2. How do I integrate the Airhub eSIM API?
Request access, build and test on the sandbox with your credentials, wire up the catalogue/order/QR/webhook flow, then flip to production. The API documentation has the full detail.
3. Do I need to be a developer to use it?
Integrating the API is a development job no way around that but it’s a standard REST pattern, and the partnerships team walks you through onboarding.
4. How does pricing work?
You buy plans at wholesale and set your own retail price.
5. How fast can I launch?
Once you’re through sandbox testing and integrated, you flip to production and start selling.
6. Is customer data secure?
Requests are authenticated, webhooks are signed and verified, and data is handled per applicable privacy law.
7. Which countries and operators are covered?
190+ countries, across local, regional, and global plans.
Get Started
Ready to build? Get API access to start in the sandbox, read the API docs, or book a demo with the partnerships team to talk through your use case and pricing.

Leave a Reply