Zetexa eSIM API documentation
What the API does and how an integration runs, end to end.
- One order object
- Sandbox mirrors production
- Webhooks or polling
The Zetexa eSIM API lets partners provision eSIMs, trigger activation, attach ancillary products such as lounge access or eVisa, and pull billing and usage data, all from a single order object. Integrations are built and tested in a sandbox that mirrors production; sandbox credentials and the endpoint reference come from your Zetexa integration contact.
Overview
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 is no second integration to add when you later sell lounge access or travel insurance.
What the API covers
eSIM provisioning and QR/activation code generation across 200+ 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
A sandbox environment that mirrors production for integration testing
How an integration runs
- 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
Core concepts
Order object — one order carries the eSIM and any ancillary line items in the same transaction
Wallet — each agent tier operates through a funded wallet that is debited as it sells; refunds and top-ups use the same system
Agent hierarchy — Master Agent, Sub-Agents and Retail Resellers, with role-based permissions over pricing, refunds and reporting at each tier
Webhooks and polling — subscribe to order and activation events, or poll for status
Sandbox — mirrors production, so ancillary attachment and billing reads can be tested before launch
Typical response times
| Operation | Typical response |
|---|---|
| Provisioning and activation calls | Under 1.5 seconds |
| Status and billing reads | Under 300 ms |
Getting access
Sandbox credentials and the endpoint reference are issued by your Zetexa integration contact, and every API partner works with that contact alongside the documentation. You do not need your own telecom infrastructure: Zetexa operates the underlying network, and your integration only calls the API for provisioning, activation and billing. To start, request a demo.
API questions
Each agent tier operates through a funded wallet. Agents top up their balance, set their own markup on top of wholesale pricing, and the wallet is debited as they sell. Refunds and top-ups run through the same system.
Yes. The API supports a full agent hierarchy — Master Agent, Sub-Agents and Retail Resellers — with role-based permissions, so you control pricing, refunds and reporting at each tier individually.
Provisioning and activation calls typically respond in under 1.5 seconds; status and billing reads are typically under 300 ms.
No. Zetexa operates the underlying network; your integration only needs to call the API for provisioning, activation and billing.
200+ countries today.
The API is self-serve to integrate against, and every partner also gets a dedicated integration contact, so it isn't purely documentation and forums.
¿Aún tienes dudas?
Nuestro equipo puede resolvértelas paso a paso.