Last updated: March 29, 2026

One eSIM Reseller API. Ten Ways to Win.

The Bappy eSIM Reseller API plugs into any business — travel apps, hotels, rental cars, MVNOs, eSIM resellers. One integration, 210+ countries of coverage, clean JSON. Pick your industry below.

In short: The Bappy eSIM Reseller API is a multi-tenant REST/JSON interface for B2B partners to sell and manage eSIM and physical SIM data packages across 210+ countries. Authentication is OAuth 2.0 Client Credentials via OmaxTelecom ID. Core endpoints: POST /links (create eSIM or SIM), GET /plans, GET /plans/{id}/coverage, POST /sms, GET /organization/balance, GET /transactions/analytics. eSIM creation returns ICCID, LPA profile, and Apple/Android activation URLs. Wallet-based billing with auto-refund on provider failure. Operated by Omax Telecom (UK Company No: 16125244, Ofcom PECN registered). EUR 500 setup, EUR 500 match credit, zero monthly minimums, zero revenue share. Full docs at developer.omaxtelecom.com/bundle-sim.

Everything a reseller platform needs

Straight from the docs. No hand-wavy "coming soon".

🔗

Links (eSIM + SIM)

Create, suspend, reactivate, and query Links. LPA profile + Apple/Android activation URLs on creation.

📱

Top-ups

Fetch compatible top-up plans per Link. Upsell more data without re-issuing eSIMs.

SMS delivery

Send SMS to any Link. Queued async delivery. List historical messages.

📶

Network status

Live network-status check per Link. Debug connectivity before the customer emails support.

📈

Analytics + transactions

Organization-wide transaction stats, per-Link history, and date-range analytics.

💰

Wallet billing

Prepaid balance per organization. Auto-refund on provider failure. No surprise invoices.

🌐

Plans + coverage

Browse the full plan catalogue, regional bundles, and per-plan coverage details in real time.

📄

Install instructions

Step-by-step iOS + Android activation guides returned by the API. Render them in your app.

REST. JSON. No surprises.

OAuth2 Client Credentials via OmaxTelecom ID, wallet-based billing, LPA profiles + Apple/Android activation URLs returned on creation. Most developers integrate in an afternoon.

Full docs at developer.omaxtelecom.com/bundle-sim ↗

REST / JSON OAuth2 (Client Credentials) eSIM + Physical SIM Multi-tenant
# 1. Get an access token from OmaxTelecom ID
curl -X POST https://id.omaxtelecom.com/oauth/token \
  -d "grant_type=client_credentials" \
  -d "client_id=$CLIENT_ID" \
  -d "client_secret=$CLIENT_SECRET"

# 2. Create a Link (activate an eSIM or SIM)
curl -X POST https://api.omaxtelecom.com/bappy/v1/links \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "plan_id": "de-10gb-30d",
    "type": "esim"
  }'

# Response includes ICCID, LPA profile,
# Apple + Android activation URLs,
# and step-by-step install instructions.
Tier-1 carrier backbone | Ofcom regulated (UK) | UK GDPR compliant | Multi-tenant architecture | 210+ countries

Questions you probably have

Straight answers. No sales-deck theatre.

OAuth 2.0 Client Credentials via OmaxTelecom ID. You exchange a client_id and client_secret for an access token, then send Authorization: Bearer <token> on every request to the Bappy API.
Create and manage Links (active eSIM or physical SIM subscriptions), fetch compatible top-up plans, send SMS to a Link, check live network status, browse plans and coverage, manage wallet balance, and pull transaction analytics. Every Link returns ICCID, LPA profile, and Apple/Android activation URLs.
Both. The same POST /v1/links endpoint handles eSIM (returns LPA + activation URLs) and physical SIM provisioning. One integration covers both.
Wallet-based. Your organization holds a prepaid balance. Each Link creation and top-up debits the wallet at the plan price. If provisioning fails on the provider side, the amount is auto-refunded to your wallet.
Six regions: Europe, Africa, Asia, Latin America, North America, and Oceania — with 210+ countries and regional bundles available. Query GET /v1/plans or GET /v1/plans/regions for the live catalogue.
Full REST/JSON documentation at developer.omaxtelecom.com/bundle-sim. Interactive reference with request/response schemas, endpoint explorer, and install instructions for iOS + Android.

Don't see your industry? Doesn't matter.

The API is the same for everyone. Tell me what you're building — I'll reply within 4 business hours with sandbox access and next steps.

Please enter your name
Please enter a valid email
Please enter your company
Please select a use case
No contract Cancel anytime 4-hour response No credit card

I reply within 4 business hours (CET). No Gary involved.

Rather talk first? Book a 15-min demo →