Picture this: you're building a product that has to activate, suspend, swap and replace SIMs and eSIM profiles from code. Maybe it's a fleet of connected devices, maybe a travel app that sells data plans. You search for who offers an API for that, and you need to know which ones are worth your time.
The APIs.io catalog has an answer, and it's more modest than you might hope. SIM & eSIM Lifecycle Management is capability BC-2640.20: personalising, distributing, swapping and replacing physical SIMs and eSIM profiles. The catalog finds 30 API surfaces from 13 providers that perform some part of it. Only 3 of those are rated strong or better.
Here's the part you might not expect. Two of those three are communications platforms, not SIM companies. Twilio, rated exemplar with a composite of 91.6, and Telnyx, also exemplar at 86.1, sell voice, messaging and numbers first, and SIMs as one more product. The third, KPN, is rated strong at 62.4 with a single API on this capability.
If you need the deepest surface, Telnyx has it. Six of its APIs are tagged SIM Card Actions, SIM Card Groups, SIM Card Group Actions and OTA updates. Its Agent Readiness is 78.6, the highest in the group. Twilio is the best-scored overall, but its Agent Readiness is 52.1 and it has two APIs here.
Now look at the companies whose whole business is IoT connectivity. Soracom, 1NCE, Onomondo and Hologram sit between 23.7 and 51.5. Soracom comes in at 51.5, 1NCE at 44.7, and the rest trail below. If you assumed the specialists would lead, the record says otherwise.
The post points to three things in the record. First, carriers are in, through their own APIs. MTN publishes SIM Activation and SIM Swap. Airtel publishes SIM LifeCycle and SIM LifeCycle Bulk. KPN's one API is a SIM block controller. Swap and block are the fraud-sensitive operations, and the carriers expose them directly.
Second, the consumer eSIM sellers are the weakest. eSIM Go at 24.4 and Maya Mobile at 21.0 each surface a single eSIMs API. Selling travel data plans through an API is the newest market here, and it has the least machine-readable surface. If you're building on one of those, expect to do more of the reading yourself.
Third, a caution if you're comparing vendors. KORE's tags carry Twilio's names. Its matched APIs include SupersimV1Sim and SupersimV1EsimProfile, which are Twilio Super SIM resource names. KORE took over Twilio's IoT business, and the contract still says so. If you're weighing the two, you should know you may be reading related surfaces rather than two independent ones.
Then the post turns to its own record, and this is the part worth holding onto. The capability has three sub-capabilities: Physical SIM Provisioning, eSIM Profile Management and Profile Swap & Replacement. Every one of them shows 0 providers. The thirteen providers match the parent, but nothing is rolled down a level, even where a tag says eSIM Profile Management or Sim Swap outright. The post is plain about whose fault that is: the gap is the catalog's. It also notes that capabilities themselves are not scored, so none of this is a judgement of the capability, only of the surfaces that reach it.
So if you went looking for a clean answer to "who does eSIM profile management," the catalog can't give you one at that level yet. It can tell you who touches the parent capability, and it says so rather than papering over the empty rows.
What do you take away? If you need to manage SIMs from code today, Telnyx is the most complete and the most agent-ready, and Twilio is the best-scored overall. Treat the numbers as a reading of published surfaces, not a verdict on the companies behind them.
And if you run one of the IoT specialists, the post says where you would move most: publish full contracts for SIM state changes, with idempotency on activate, suspend and swap. Those are the calls an agent should never send twice.
Read the original: https://apis.io/2026/10/26/sim-and-esim-lifecycle-has-thirteen-providers-and-the-iot-specialists-trail-the-cpaas/