
One API for eSIM, activation, and billing
Built for partners embedding connectivity into their own product — not a developer sandbox nobody outside engineering ever ships.
The Zetexa eSIM API lets partners provision eSIMs, trigger activation, attach ancillary products like lounge access or eVisa, and pull billing data — all from a single order object, with a sandbox environment that mirrors production.
Built to embed, not just integrate
Every Zetexa product — white-label travel eSIM, USA/Canada MVNO plans, ancillary add-ons — runs on the same core API. Partners use it to provision SIMs, trigger activation, attach ancillary line items, and reconcile billing without touching Zetexa's own consumer surfaces. One order object carries the whole transaction, so there's no second integration to bolt on when you add lounge access or travel insurance later.
What the API covers
Getting integrated
Get sandbox API credentials from your Zetexa integration contact
Build against the provisioning and activation endpoints
Subscribe to webhooks (or poll) for order and activation status
Test end-to-end in the sandbox, including ancillary attachment and billing reads
Move to production with a phased rollout
Built for production traffic
FAQ
Questions about One API for eSIM, activation, and billing
No — Zetexa operates the underlying network; your integration only needs to call the API for provisioning, activation, and billing.
Yes, every partner gets sandbox credentials that mirror production before moving live.
Provisioning and activation calls typically respond in under 1.5 seconds; status and billing reads are typically under 300ms.
Both — subscribe to a webhook for order and activation status changes, or poll the status endpoint directly if that fits your architecture better.
180+ countries today — the same footprint behind Zetexa's white-label and USA/Canada MVNO programs.
Yes — lounge access, Fast Track, meet & greet, eVisa and travel insurance can all be included as line items in the same /v1/esim/orders call, so there's no separate integration for ancillaries.
iOS and Android SDKs are available alongside the REST API — useful if you're building the connectivity flow directly into a native app rather than calling the API from your own backend.
Yes — it's the same API and order object across Zetexa's travel eSIM, USA/Canada MVNO, and ancillary product lines, so one integration covers all three rather than needing separate ones.
Still have questions? Our team can walk you through it.