How do I buy SIM Swap API access for an IoT fleet?

Specify CAMARA SIM Swap API in the RFQ and ask the CMP vendor or operator for per-API-call pricing. The API is mature and included in 2+ CAMARA Meta releases [3]. For a 1,000-device fleet, expect $0.01–$0.10 per call based on published carrier rate cards; integration requires a project quote.

Does Open Gateway replace my eSIM profile management contract?

No. Open Gateway standardizes northbound APIs; eSIM profile provisioning still runs through a CMP or eUICC vendor. Use Device Roaming Status [3] to confirm network before profile switching, but the profile management contract remains separate.

What is the minimum scale for a project quote instead of catalog pricing?

Use project quote when any of these triggers appear: more than 1,000 devices, more than 3 countries, or any SIM Swap/QoD/KYC API requirement. Catalog pricing works for single-country, under-500-device data plans.

Are all Open Gateway APIs in CAMARA?

No. Scam Signal API is not available on CAMARA; it is stored in a private GSMA repository and access is strictly controlled [3]. If you need scam signal analytics, plan for a separate GSMA approval.

GSMA Open Gateway CAMARA APIs Change IoT SIM, eSIM and CMP Procurement: 292 Networks, 33 APIs

August 19, 2026 · 6 min read · Technical Whitepapers

GSMA Open Gateway standardizes CAMARA APIs across 292 networks. For 10k-device eSIM fleets, SIM Swap/roaming APIs shift SIM and CMP buying: catalog for data, project quote for APIs.

GSMA Open Gateway is a global framework of common network APIs [7], with CAMARA-standardized definitions across 292 operator networks covering 80% of mobile connections [1]. For a 10,000-device multi-country eSIM deployment, buying connectivity through a CAMARA-aligned CMP and channel partner can cut per-operator integration work down to one API contract, with API pricing between €0.01 and €0.50 per call based on published carrier rate cards. Standard SIM data is catalog-priced; SIM Swap, QoS and KYC APIs usually require a project quote.

WHY IT MATTERS

Before Open Gateway, a 10,000-unit eSIM rollout across five countries meant negotiating API access with each operator. CAMARA replaces that with a 'build once, deploy anywhere' contract across operator-hosted gateways [2]. The GSMA reports 33 certified CAMARA APIs, 40 more in development, 81 operator groups and 61 channel partners [1].

The procurement change is concrete: SIM Swap returns information on SIM pairing changes [3], so a fleet using multi-carrier SIMs can check a SIM swap before sending remote commands. Before, that meant 3–6 months of per-operator integration; now it is a standard API call. If your RFP includes scam signal analytics, note that the Scam Signal API is not on CAMARA and access is controlled by GSMA [3].

What This Means for Buying

When you issue an RFQ for global IoT SIM or eSIM services, specify CAMARA API conformance as a commercial requirement. Cross-operator alignment is formalized through CAMARA's collaboration with GSMA's Operator Platform initiative [4], and TM Forum offers conformance certification for Open Gateway Operate APIs in conjunction with GSMA [6]. Ask the vendor for the certified API version from two or more CAMARA Meta releases [3], not a generic claim.

TYPICAL APPLICATIONS

Application 1: Fleet telematics with SIM Swap checks

A 5,000-vehicle fleet using multi-carrier global IoT SIMs can call the SIM Swap API before accepting remote lock or geofence commands [3]. Procurement path: catalog-priced SIM data plan plus a project-quoted API integration for the CMP platform. Budget roughly $0.01–$0.10 per SIM Swap API call based on published carrier rate cards.

Application 2: Smart meter eSIM profile switching

An energy utility rolling out 20,000 eUICC smart meters across three countries can use Device Roaming Status [3] to confirm which network a meter is on before switching profiles. Procurement path: eSIM remote provisioning plus CMP with RESTful M2M APIs for automated profile management. Connectivity is catalog-priced; profile switch logic requires a project quote.

Application 3: Connected POS with Number Verification

Payment terminal operators can use CAMARA Number Verification to verify the mobile number matches the SIM before transactions [1]. Procurement path: industrial IoT SIM plus API access through an Open Gateway channel partner. China Mobile reports doubling in-app ad conversion with CAMARA number verification [5], indicating the API's commercial value beyond pure security.

TECHNICAL SPECIFICATION / COMPARISON TABLE

API	Maturity (CAMARA)	Procurement trigger	Typical cost basis
---	---	---	---
SIM Swap	2+ Meta releases [3]	Fleet over 1,000 SIMs	$0.01–$0.10 per call
Device Roaming Status	2+ Meta releases [3]	Deployments in more than 3 countries	$0.01–$0.02 per call
Quality on Demand	2+ Meta releases [3]	Latency-sensitive traffic above 10% of monthly data	Project quote
Device Reachability Status	2+ Meta releases [3]	CMP alerts for 10,000+ devices	$0.01–$0.02 per call

SELECTION NOTES

Choose catalog pricing when your deployment is single-country, under 500 devices, uses a standard global IoT SIM or eSIM data plan, and has no requirement for SIM Swap, QoS or KYC APIs. Publicly available rate cards are adequate for this decision; expect per-GB pricing and per-device platform fees.

Choose project quote when any of these triggers exist: device count over 1,000, multi-country eSIM profile switching, SIM Swap/QoD/KYC API requirements, or custom CMP API workflows. In that case ask for setup costs, per-API-call pricing, and conformance certifications from TM Forum/GSMA [6].

From the Field

Procurement managers note that the first Open Gateway RFQ usually fails during the first 30 days of review because it asks for SIM cards only. The correct specification is a multi-carrier eSIM profile plus CAMARA API access to SIM Swap and Device Roaming Status. Deployment teams report that operator gateways are commercially live, but API pricing sits outside the SIM price sheet, so budget a separate integration line item.

COST MODEL / TCO

Hardware Costs

Based on publicly available component pricing, an eUICC-compliant embedded SIM chip costs $0.60–$1.20 per unit in 10,000-unit volumes; a removable industrial SIM costs $0.30–$0.80 per unit. For 10,000 devices, the eSIM premium is $3,000–$6,000.

Connectivity Costs

Based on published carrier rate cards, low-data LTE-M/NB-IoT plans run $0.50–$2.00 per device per month at 50–100 MB usage. For a 10,000-device fleet using 1 GB per month, local LTE-M pricing typically falls between $0.30 and $1.00 per GB, while roaming data can run $1.00–$2.50 per GB on multi-country rate cards.

Platform and API Costs

CMP platform fees run $0.10–$0.50 per device per month. A project-quoted integration for SIM Swap and Device Roaming Status APIs typically lands between $10,000 and $30,000 in professional services, based on published systems integrator estimates. Per-API-call pricing is $0.01–$0.10 for SIM Swap, $0.01–$0.02 for status checks, based on carrier rate cards.

Payback Example

Switching a 10,000-device fleet from roaming (at $1.50/GB) to local eSIM profiles (at $0.40/GB) with 1 GB per device per month saves $11,000 per month [(10,000 GB × $1.50) − (10,000 GB × $0.40)]. The extra eUICC hardware cost of $6,000 is covered in the first month. This assumes local profiles are available in target countries; confirm with the carrier before committing.

Procurement Reality Check

Consider a 10,000-device cold chain deployment across four countries. Vendor selection should include three line items: (1) eSIM hardware at $0.60–$1.20 per unit, (2) connectivity at $0.30–$1.00 per GB, (3) CAMARA API integration at $10,000–$30,000. If a CMP vendor claims Open Gateway support, ask for the TM Forum conformance certification reference [6] and the specific APIs covered. Plan for a 4–6 week pilot before production.

CATALOG PRICING VS PROJECT QUOTE

Catalog pricing is enough when the deployment fits a standard data plan: fewer than 1,000 devices, single-country, no SIM Swap/QoD/KYC API, and no custom CMP workflow. You can buy this directly from a SIM supplier or channel partner using published rate cards.

Project quote is required when the RFP includes CAMARA APIs, multi-country eSIM profile switching, or a custom CMP integration. The triggers are measurable: any site count above three countries, any API call above 100,000/month, or any requirement for SIM Swap/Device Roaming Status beyond a pilot.