eSIM API and MCP Integration | ZIM Skip to content
Talk to us

eSIM API & MCP Server for Brands

The eSIM API and MCP Built
for Brands and Resellers

ZIM is an eSIM API and MCP server that lets you add eSIM plans to your product with a single REST API, native SDK, or AI agent. Search, price and provision connectivity across 200+ destinations.

View API Doc
Tablet showing a purple eSIM store with a London photo
eSIM API-first

A single, clean eSIM API (with native Android and iOS SDKs) exposes the full eSIM catalogue, provisioning, activation and usage data.

Reseller margins, your way

As an eSIM API reseller, you set your own retail pricing on top of ZIM's competitive wholesale rates, per plan and per market. You define the margin.

Full eSIM API lifecycle

One eSIM API integration covers the whole journey: purchase, instant provisioning, installation, activation, real-time usage tracking, top-ups and expiry.

No redirects, one API call

The entire experience stays inside your app or site via the eSIM API, from browse to checkout to active eSIM. Customers never leave your brand.

eSIM API and MCP support

Technical and operational support, covering the eSIM API, SDK and MCP server. ZIM handles Level 2 support, carrier relationships and compatibility.

Every Plan Attribute, Under Your Control

eSIM type, network, coverage, data, voice, text, period and price: set through the eSIM API, SDK or the MCP server, and the eSIM lands inside your own products.

eSIM
type: "digital_esim"
physical: false
// eSIM provisioned via API
Network
carrier: "AT&T"
roaming: true
// vodafone | orange
Coverage
countries: ["US"]
regional: true
// + CA, UK, DE, 200+
Data
data: 10
unit: "GB"
throttled: true
Voice
voice: "unlimited"
minutes: null
Text
sms: "unlimited"
limit: null
Period
period: "1_month"
recurring: true
Price
retail: 40
currency: "USD"
White 3D phone with an eSIM chip on screen

Explore the eSIM
API Documentation

Everything your team needs to build against the ZIM eSIM API sits in one reference: destinations, plans, orders, eSIMs and subscriptions, each with real request and response payloads. Authentication is a single key, resources are versioned, and every endpoint below is the same one running in production.

eSIM API Documentation

API Docs
Look Up Any Destination the eSIM API Covers

Ask the eSIM API what a country supports before you show it in your store. Every destination returns its display name, ISO code and the scopes it can be sold under: local, regional or global, so your catalogue only ever offers plans that really exist.

Response 200
{
  "name": "France",
  "isoAlpha3": "FRA",
  "scopes": {
    "local": true,
    "regional": true,
    "global": true
  }
}

ZIM eSIM API Stack

  • DestinationsGET /destinationsCoverage, networks and eSIM API pricing across 200+ markets.
  • PlansGET /plansData, voice and texts you resell under your brand via the API.
  • OrdersPOST /ordersCreate a purchase and get the eSIM back in one eSIM API call.
  • eSIMsGET /esimsProfiles, QR codes, install links and activation status.
  • SubscriptionsPOST /subscriptionsRecurring plans with renewals, changes and cancellation.
  • Usage & top-upsGET /usage · POST /topupsLive consumption, and extra data added to an active plan.
  • Phone numbersGET /numbersUK and international numbers for voice and SMS.
  • WebhooksPOST /webhooksActivation, usage and expiry events pushed to your systems.

MCP Connectivity: eSIM Infrastructure for
AI Agents

Describe the perfect trip and let the AI agent handle connectivity, so any AI assistant like Claude or ChatGPT can search plans, price them and provision an eSIM on your behalf.

API and MCP

Leverage ZIM's public APIs to search, price and provision eSIMs from your own product. Every endpoint your store needs sits behind one authenticated key, documented and versioned.

Agents talk to ZIM directly through an MCP server to buy eSIMs on a user's behalf. Try it: ask for a destination, buy a plan, top up. The same tools your own agent would call, running in an interactive demo with simulated data, so you can see the whole flow before writing a line of code.

Simulated tool calls mirror the real MCP tools.

Interactive demo, simulated data Watch an AI agent find, buy and top up an eSIM through ZIM's MCP tools.

How it works

One eSIM API, One MCP Connectivity
Layer, Every eSIM

A single eSIM API for search, pricing, provisioning and usage across 200+ destinations, plus MCP connectivity so your AI agents can build and run the store themselves. Native iOS and Android SDKs on request.

Connect With ZIM

Connect once to the ZIM eSIM API or MCP server. ZIM holds the carrier deals, the eSIM profiles and the provisioning, so your product simply delivers connectivity to the traveller in 200+ destinations, with no operator negotiations and no telecom stack to build.

Global Connectivity PoolWholesale connectivity in 200+ destinations.
ZIM APIOne REST API for catalogue, pricing, orders, provisioning and usage via the eSIM API.
ZIM MCP ServerSame stack, exposed as MCP tools, so AI agents can manage eSIMs for their users.
ZIM Partner DashboardOrders, activations, usage and support in one place, across every market you sell in, through the ZIM eSIM API.
Your Own AppEmbed plans and activation straight into your app using the ZIM eSIM API.
Your Own WebsiteEmbed plans and activation straight into your website using the ZIM eSIM API.
eSIM DeliveredThe traveller installs in one tap and is connected in under 30 seconds.

How Allianz Integrated eSIM
in Their Product

Case Study

122M+ Customers Reached

Allianz used the ZIM eSIM API to add connectivity to its travel platform. Allianz is a global leader in insurance and financial services, headquartered in Munich, Germany. With more than 122 million customers worldwide, it provides services across travel, health and insurance. As part of its digital strategy, Allianz integrated the ZIM eSIM API to add value added services that improve the customer experience, and connectivity was a natural fit for its travelling customers.

Don't Just Take Our Word for It

Ask ChatGPT, Claude or Perplexity how the ZIM eSIM API and MCP let brands embed eSIM connectivity in their own product.

Ask ChatGPT Ask Claude Ask Perplexity

Partner Integration Workflow

  • 3D compass icon in whiteExplore ExploreDocs and a sandbox to see how the eSIM API and MCP server fit your product.
  • 3D code brackets icon in whiteBuild BuildIntegrate via eSIM API, a native eSIM SDK, or the MCP server on your stack.
  • 3D lab flask icon in whiteTest TestValidate the full eSIM API flow end to end in sandbox.
  • 3D rocket icon in whiteGo live Go liveLaunch to production in two to four weeks.
  • 3D speed gauge icon in whiteOperate OperateSell, manage and track from the dashboard.

End-User Journey:
Powered by the ZIM eSIM API

Offer Your Customers
the Best Experience
in Two Clicks

We built the ultimate customer experience in just two clicks, powered by the ZIM eSIM API. Inside your app or website, your users can seamlessly browse tailored data plans and instantly activate their connection. This frictionless, fully native journey, eliminates all user drop-off and keeps your brand at the centre of their mobile experience.

Phone showing the eSIM app home screen with destinations

Market Overview

eSIM API and MCP Use Cases

How four kinds of product are already embedding connectivity through the eSIM API, the play, the flow and what each side gets out of it.

Segment

FinTechs

Banking, payments and travel-money apps

The play

Connectivity as a daily engagement and loyalty lever inside a financial product, delivered through the ZIM eSIM API.

Flow

  1. Detect trip or FX activity
  2. Show a matched plan in-app via the eSIM API
  3. One-tap buy, stored payment
  4. Instant eSIM activation

Why it works for you

A daily reason to open the app beyond financial events. OTP and SMS verification built in for secure authentication through the eSIM API, and a new ancillary revenue line with minimal setup.

What your customer gets

Free or discounted data as a loyalty reward, a local number tied to their financial identity, and international calling and travel data in one place, provisioned through the eSIM API.

Logos of ZIM investors and press coverage in grey, including Y Combinator, BTS, The Times, The Guardian, El País and the BBC

FAQ

Frequently Asked Questions

What is the ZIM API and SDK?

The ZIM eSIM API is a REST API that lets developers search, price, order and provision travel eSIMs from their own app or site, with SDKs for iOS and Android. Our MCP server gives AI agents the same tools.

How long does integration take?

Most teams complete an eSIM API integration in about 2 weeks, from sandbox to first live order.

Is there a sandbox and documentation?

Yes. Developers get full eSIM API documentation and a live sandbox to test eSIM provisioning, orders and webhooks before launch.

What support do you provide?

Our team supports your eSIM API integration from setup to launch, then provides Level 2 support for provisioning and connectivity once you’re live.

What does it cost, and how do we earn?

The API is free to integrate; you pay only for activations at ZIM’s wholesale rates and set your own retail margin, invoiced monthly on actual usage.

Is there a minimum volume commitment?

No. You pay per eSIM sold, with no minimum volume to start.

Is the eSIM API secure and GDPR compliant?

Yes. Every eSIM API call runs on an authenticated, versioned key, and personal data is handled in line with GDPR.

Build It Into Your Product

Tell us about your stack and markets, and we'll scope the integration with you.

  • A 30-minute call to scope the right model for your roadmap
  • A tailored pricing and margin breakdown for your markets
  • A clear launch timeline, from one day to a few weeks