B2B eSIM Reseller API: Integrate Travel Data Sales in Your Platform

Travel brands, MVNO partners, and software platforms increasingly sell mobile data as a digital add-on. A B2B eSIM reseller API lets you list plans, charge your wallet, place orders programmatically, and deliver QR codes to end customers — without managing carrier contracts or SM-DP+ infrastructure yourself.

What is a B2B eSIM reseller API?

A reseller API is a REST interface between your product (website, app, CRM, or checkout flow) and a wholesale eSIM supplier. Your backend authenticates with an API key, reads the B2B catalog and your account balance, creates orders, and retrieves activation payloads (LPA strings, ICCID, SM-DP+ address) for delivery to travellers.

Unlike consumer apps such as Airalo or Holafly — where end users buy directly — a reseller API is built for businesses that want their own brand, pricing layer, and customer experience while the supplier handles inventory and provisioning.

Who should use an eSIM Partner API?

• Travel agencies and OTAs bundling data with flights or packages
• Resellers and distributors adding eSIM to an existing telecom or travel catalog
• SaaS platforms (expense, HR, relocation) offering connectivity to mobile users
• Marketplaces and affiliate sites automating fulfillment after payment
• Developers building niche travel apps for digital nomads or corporate travellers

Typical API workflow

1. Authentication

Most B2B eSIM APIs use Bearer token authentication. Production keys fund real orders; sandbox keys (often prefixed differently) let you test catalog reads and simulated orders without debiting a live wallet.

2. Catalog sync

GET /plans returns plan IDs, coverage labels, validity, and your wholesale price in EUR. Sync this into your database or cache on a schedule (e.g. every hour) so your storefront stays accurate without hitting the API on every page view.

3. Balance check

GET /wallet shows available balance before checkout. B2B models usually pre-fund a wallet (card, bank transfer, or Wise/Revolut) rather than charging per order by card — simpler for high volume and instant fulfillment.

4. Place order

POST /orders with planId, optional deliveryEmail for the end traveller, and an idempotencyKey. The same idempotency key must return the same order if retried — critical for payment webhooks and unreliable networks.

5. Retrieve eSIM

Poll GET /orders/{id} until fulfillmentStatus is delivered, then GET /orders/{id}/esim for qrCodeData (LPA), activationCode, iccid, and smdpAddress. Alternatively, configure webhooks (e.g. order.delivered) to push activation data to your server.

Integration best practices

• Use idempotency keys on every order creation tied to your internal payment or cart ID
• Never expose API keys in frontend JavaScript — call the supplier from your backend
• Store activation codes encrypted; treat them like credentials
• Handle 404 esim_not_ready with exponential backoff, not tight loops
• Log orderId and supplier references for support tickets
• Test sandbox end-to-end before switching to live keys

MegaEsim Partner API

MegaEsim offers a REST Partner API v1 for approved B2B accounts: catalog across 190+ destinations, wallet-funded orders, instant QR delivery, optional branded emails to end customers, sandbox keys for development, and webhooks for order.delivered events.

Base URL for server-side integration: https://api.megaesim.us/api/v1. Documentation and API keys are available in the partner Developers section after commercial onboarding.