Suspend & Unsuspend eSIMs
Suspending an eSIM temporarily disables its network services. Depending on the underlying carrier, the eSIM may be fully blocked from connecting or it may attach to the network but be unable to use any services. The eSIM and its assigned bundles are preserved — suspending is a reversible action.
Endpoints
POST /v2.5/esims/{iccid}/suspend— suspend or unsuspend an eSIMGET /v2.5/esims/{iccid}/suspend— check the current suspension status of an eSIM
Suspending an eSIM
curl -X POST https://api.esim-go.com/v2.5/esims/{iccid}/suspend \ -H 'X-API-Key: $API_KEY' \ -H 'Content-Type: application/json' \ -d '{"suspend": true}'A successful response returns 201:
{ "status": "eSIM suspended successfully"}Unsuspending an eSIM
curl -X POST https://api.esim-go.com/v2.5/esims/{iccid}/suspend \ -H 'X-API-Key: $API_KEY' \ -H 'Content-Type: application/json' \ -d '{"suspend": false}'Suspension types
There are two types of suspension, and it is important to understand the difference:
Partner suspension — initiated by you via the API. You can unsuspend at any time by setting suspend: false.
Policy enforcement suspension — initiated by eSIM Go when an eSIM breaches a fair use or compliance policy. These suspensions cannot be reversed via the API. Contact eSIM Go support if you believe a policy suspension has been applied in error.
Attempting to unsuspend a policy-enforced suspension via the API will return 403 Forbidden.
Constraints
| Condition | Result |
|---|---|
| eSIM is already suspended | 400 Bad Request |
| eSIM has been deactivated | 400 Bad Request |
| eSIM is policy-suspended | 403 Forbidden on unsuspend attempt |
| ICCID not in your organisation | 403 Forbidden |