eSIM is the GSMA's remote SIM provisioning architecture, in which the subscriber identity is a profile downloaded onto an embedded universal integrated circuit card (eUICC) rather than a plastic card someone physically inserts. The specifications define how profiles are prepared, delivered, enabled, disabled and deleted over the air.
eSIM
eSIM turned the most physical object in telecom into a software resource, and in doing so created one of the few genuinely programmable network primitives.
- Profiles, not cards - A subscription becomes a downloadable artifact with a lifecycle that can be driven by an API.
- Machine-to-machine and consumer variants - The specifications distinguish between device-initiated consumer provisioning and server-driven IoT provisioning.
- Where the real network verbs live - Scoring telecom found the IoT and eSIM tier to be the only place in the sector publishing genuine network-state operations: eUICC operations, profile ordering, SIM lifecycle.
- Published by non-carriers - Twilio, Soracom, emnify, 1NCE and KORE expose carrier-grade provisioning as REST; the carriers whose networks those profiles run on largely do not.
eSIM is a useful counter-example to the pessimism the rest of telecom’s API story invites. When a network capability was genuinely specified as a resource with a lifecycle, a competitive layer formed around it and published real contracts against it.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of Telecom APIs
The only tier in the sector publishing genuine network-state verbs — and it is non-carriers exposing carrier-grade provisioning as REST.
