Zetexa
Product

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

eSIM provisioning and QR/activation code generation across 180+ countries
Real-time activation and usage status, by webhook or polling
Ancillary line items — lounge, Fast Track, meet & greet, eVisa, travel insurance — in the same order
Billing and usage data for reconciliation, exportable per partner or per SKU
Sandbox environment that mirrors production for integration testing

Getting integrated

1

Get sandbox API credentials from your Zetexa integration contact

2

Build against the provisioning and activation endpoints

3

Subscribe to webhooks (or poll) for order and activation status

4

Test end-to-end in the sandbox, including ancillary attachment and billing reads

5

Move to production with a phased rollout

Built for production traffic

Bearer-token authentication on every request
Structured JSON responses with consistent error codes
Sandbox environment mirrors production so nothing breaks on go-live
iOS and Android SDKs available alongside the REST API

FAQ

Questions about One API for eSIM, activation, and billing

Do we need our own telecom infrastructure to integrate?

No — Zetexa operates the underlying network; your integration only needs to call the API for provisioning, activation, and billing.

Is there a sandbox environment?

Yes, every partner gets sandbox credentials that mirror production before moving live.

What response times can we expect from the API?

Provisioning and activation calls typically respond in under 1.5 seconds; status and billing reads are typically under 300ms.

Do you support webhooks, or is it poll-only?

Both — subscribe to a webhook for order and activation status changes, or poll the status endpoint directly if that fits your architecture better.

Which regions does the API cover?

180+ countries today — the same footprint behind Zetexa's white-label and USA/Canada MVNO programs.

Can we attach ancillary products in the same order?

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.

Do you provide SDKs, or just raw REST?

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.

Can the same integration serve both our travel eSIM and USA/Canada MVNO products?

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.