TL;DR: The TelecomsXChange eSIM API is live. Search 150+ countries, provision eSIMs in under a second, and manage top-ups—all through three simple API endpoints. No contracts, no minimums, pay-as-you-go.

The eSIM Exchange is officially open for business. If you’re building travel apps, IoT platforms, or mobile-first products, you can now integrate wholesale eSIM provisioning. This is ideal for anything that needs global data connectivity. Integrate it directly into your stack.

Here’s what that looks like in practice.

The API: Three Endpoints, Global Coverage

We designed this API for developers who want to ship fast. No SDKs to install, no complex authentication flows, just standard API calls with JSON responses.

1. Search Available Packages

Query the marketplace by country, data size, or provider:

curl --location 'https://apiv2.telecomsxchange.com/buyers/esim/market' \
  --form 'country="Germany"' \
  --form 'pager="10"' \
  --form 'off="0"'

The response includes real-time pricing from multiple providers, coverage details, validity periods, and package specifications. You’re not locked into a single vendor—compare rates across the entire marketplace programmatically.

2. Purchase and Provision

Once you’ve selected a package, provision it instantly:

curl --location 'https://apiv2.telecomsxchange.com/buyers/esim/purchase' \
  --form 'package_id="pkg_abc123"' \
  --form 'quantity="1"'

The response returns the eSIM profile data, including the QR code for activation. Provisioning typically completes in under one second.

3. Top-Up and Extend

Need to add data or extend validity on an active eSIM? One more endpoint:

curl --location 'https://apiv2.telecomsxchange.com/buyers/esim/topup' \
  --form 'esim_id="esim_xyz789"' \
  --form 'package_id="pkg_topup_5gb"'

That’s the complete lifecycle: search, buy, extend. Three endpoints.

Why This Matters for Your Product

Multi-provider access through one integration. The traditional approach to eSIM integration involves negotiating contracts with individual providers. It also requires maintaining separate API integrations for each. You must also manage multiple billing relationships. With the exchange model, you integrate once and access every provider on the marketplace.

Real-time inventory and pricing. The API returns live data. When you query for packages in Japan, you’re seeing current availability and current wholesale rates from all connected providers. No stale catalogs, no surprise out-of-stock errors at provisioning time.

Sub-second provisioning. eSIM profiles are delivered programmatically the moment you call the purchase endpoint. Your users can be connected in the time it takes to scan a QR code.

No minimums, no commitments. Buy one eSIM or ten thousand. The API doesn’t care. This makes it practical to start small, test your integration, and scale when you’re ready.

Use Cases We’re Seeing

• Travel apps are the obvious one. Let users buy data for their destination directly in your app. Provision it before they land. Allow them to top up if they run low. No hunting for local SIM cards, no roaming bill surprises.
• IoT deployments benefit from the multi-provider model. Different providers excel in different regions. You can programmatically select the best option for each device’s location. This is better than forcing everything through a single global provider.
• Enterprise mobility platforms can offer eSIM provisioning as a feature. This allows IT teams to equip traveling employees with data plans on demand.
• MVNOs and CSPs building their own consumer products have an option. They can white-label the entire flow. They access wholesale rates without building provider relationships from scratch.

A Note on the MCP Server

Teams using AI assistants in their workflow can benefit from our latest feature. We’ve shipped an MCP (Model Context Protocol) server. It wraps these same endpoints. You can drop a travel itinerary into Claude, or another MCP-compatible assistant. It can search providers. It can also compare rates and provision eSIMs conversationally.

It’s the same three endpoints under the hood, just with a natural language interface on top. Details at telecomsxchange.com/mcp-server.

Getting Started

1. Sign up for a buyer account here
2. Fund your wallet (the same wallet works for voice, SMS, numbers, and eSIMs)
3. Grab your API credentials from the dashboard
4. Start making calls to the endpoints above

Full API documentation

What’s Next

We’re actively onboarding new eSIM providers to expand coverage and drive competition on pricing. The exchange model means more providers equals better options for everyone building on the platform.

If you’re an eSIM provider looking for distribution, the seller onboarding process is straightforward. A single integration gets you in front of hundreds of CSPs and developers.

Questions? Reach out or check the eSIM Exchange page for the full platform overview.