- Home
- Blog
- API & Integration
- Best eSIM API for Developers and Platforms in 2026
Best eSIM API for Developers and Platforms in 2026
The best eSIM API gives you a live catalogue, one-call ordering that returns a ready-to-install eSIM, top-ups, usage and refunds, webhooks for status changes, a full sandbox and solid security such as scoped keys and IP allowlists. Fully Signal's REST API covers all of these and returns a white-label install page with every eSIM.
In this article
If you're building a travel app, a booking platform or an eSIM store, the API you choose decides how fast you ship and how much support you'll handle later. Here's what to look for in an eSIM API — and how Fully Signal's API approaches each part.
1. A clean, live catalogue
You need to list what you can sell. A good eSIM API exposes:
- Destinations — countries and regions
- Packages per destination with data size, validity and price
- Stable package IDs you can store in your own database
Fully Signal exposes endpoints for countries, regions, destinations and packages, and refreshes the catalogue continuously so your prices and availability stay current.
2. One call to a ready eSIM
Ordering should be a single request that returns everything your customer needs:
POST /api/v1/orders
Authorization: Bearer fsk_live_…
{ "package_id": "IT_5GB_30D_FIXED", "customer_ref": "booking-4821" }The response includes the order ID, status, price and the eSIM itself — ICCID and an install_page_url your customer can open to install it. Your own reference (customer_ref) travels with the order, so you can match it to a booking.
3. Top-ups, usage and refunds
Selling the first eSIM is only half the product. Look for:
- Top-ups on an existing eSIM, so customers don't need a new QR code (why it matters)
- eSIM status and remaining data, to show in your app or support desk
- Refunds for eSIMs that were never used (refund rules)
4. Webhooks
Polling is slow and wasteful. Webhooks tell your system when something happens — an order completes or fails, an eSIM is activated or expires, an order is refunded — so you can email the customer or update your dashboard instantly. See eSIM webhooks explained.
5. A real sandbox
You should be able to build the whole integration before spending anything. Fully Signal gives every new account a test API key with sample destinations and prices, and the sandbox can simulate outcomes so you can test your error handling. More in sandbox testing for eSIM APIs.
6. Security
An API that spends money needs strong controls:
| Control | What it prevents |
|---|---|
| Scoped API keys | A catalogue-only key can't place orders |
| IP allowlists | A leaked key is useless from another server |
| Two-step sign-in | Account takeover through a stolen password |
| Separate test and live keys | Test traffic never spends real balance |
| Prepaid balance | No surprise invoices; spending is capped by your balance |
Fully Signal supports all of these, plus team access with roles so developers and finance staff each see what they need.
7. Clear errors and limits
Good APIs return predictable error codes, explain what went wrong and send Retry-After when you hit a limit. This turns a 2 a.m. incident into a log line.
Comparing eSIM APIs: a checklist
| Feature | Must have | Nice to have |
|---|---|---|
| Catalogue endpoints | ✔ | Regional and global plans |
| Single-call ordering | ✔ | Your own reference on the order |
| Install link / QR | ✔ | Branded with your logo |
| Top-ups | ✔ | Top-up history per eSIM |
| Usage and status | ✔ | Webhooks on changes |
| Refunds | ✔ | Automatic for unused eSIMs |
| Sandbox | ✔ | Simulated error scenarios |
| Security | ✔ | Scopes, IP allowlists, 2FA |
FAQ
What is an eSIM API?
An eSIM API lets your software list eSIM plans, buy them and deliver them to customers automatically. It's how a website or app sells eSIMs without anyone doing it by hand.
Is the Fully Signal API RESTful?
Yes. It's a JSON REST API authenticated with bearer keys, with webhooks for events and a sandbox for testing.
Can I test the API without paying?
Yes. Every Fully Signal account can create a test key with sample data; sandbox orders are never charged.
How long does an eSIM API integration take?
A basic integration — list packages, create orders, show the install link — can take a developer a few days. Top-ups, webhooks and refunds add a little more. See how to integrate an eSIM API.
