eSIM API
Design connectivity around the traveler’s whole journey.
Plan an eSIM integration for a travel product, connectivity reseller or embedded marketplace. APISMA reviews private access for your intended business use, markets and expected volume.
Before choosing a plan
Check the device, the destination and the time of use.
A destination label alone does not tell a traveler whether a plan fits. Present the confirmed conditions that affect purchase, installation and arrival.
| Decision | What the traveler needs to understand | What to confirm for the scope |
|---|---|---|
| Device compatibility | Whether their specific device can use the intended eSIM service. | Device and software requirements, regional variants and any carrier-lock limitations. |
| Destination | Where the plan applies, including relevant multi-country travel. | The actual coverage scope and restrictions; do not infer a regional plan from one destination. |
| Allowance and validity | What is included and how long it can be used. | The allowance, expiry conditions and event that starts validity. |
| Installation and activation | What to do before departure and what to do on arrival. | The approved setup instructions and whether connectivity is needed for installation. |
Three distinct moments
Installed is not the same as connected.
Separate the stages in your product so a traveler can understand what is complete and what remains. Use the actual plan instructions; this is a customer-experience model, not an APISMA API state machine.
- 01
Choose the plan
Help the traveler compare the destination, allowance and validity against their trip. Put compatibility checks before commitment.
- 02
Install the eSIM
Provide the applicable setup instructions and a safe way to find them again. Do not expose activation data in public screenshots or support threads.
- 03
Connect at the destination
Explain the relevant device settings and activation conditions. Give a support route that does not assume the traveler already has working mobile data.
Travel support
Design help for someone who may be offline.
The traveler’s problem can arise before installation, during setup or after arrival. A single “activation failed” message cannot distinguish those situations.
- Before departure
Make the confirmed instructions accessible and explain what must be completed while an internet connection is available. Avoid guessing the best installation time.
- On arrival
Help distinguish setup steps from coverage and plan conditions. Ask for safe device and error context, not publicly shared activation secrets.
- Plan changes
Do not assume every plan supports top-ups, reinstallations or device transfers. Confirm those behaviors before putting related controls in the interface.
A travel marketplace adding connectivity
Place the connectivity decision where the traveler knows the destination and trip length. Keep plan restrictions visible even when the eSIM is sold alongside a booking.
The marketplace still needs an owner for traveler support. A private API relationship does not automatically answer every device-specific question.
Common questions
Questions about eSIM integration.
Does this page confirm destination coverage?
No. It explains the planning decisions for an eSIM integration. Coverage, plan inventory, allowances and commercial conditions require confirmation for the approved scope.
When does plan validity start?
That depends on the actual plan conditions. Confirm the event that starts validity and explain it clearly; do not assume that purchase, installation and first connection are equivalent.
Can customers reinstall or move an eSIM?
Do not assume that every plan allows it. Verify the applicable behavior and support procedure privately before offering a reinstall or transfer action.
What should a travel or white-label team include?
Describe the traveler journey, customer relationship, intended destinations and volume range. Identify the team responsible for setup and post-arrival support.
Describe where connectivity fits your travel product.
Select eSIM plans in the form and share your company, work contact and expected volume. Prepare the traveler journey and plan questions for the follow-up; do not submit activation data or device identifiers.
Submitting a request does not create an account or guarantee approval.