eSIM Lifecycle & Inactivity

eSIM Go automatically monitors eSIMs for inactivity. An eSIM that has had no bundle activity for 180 days is scheduled for permanent deactivation. This guide explains the deletion pipeline, the webhook events you’ll receive, and how to prevent deletion.

The deletion pipeline

When an eSIM crosses the 180-day inactivity threshold, it moves through the following stages:

Stage	Timing	Description
Deletion scheduled	Day 0	eSIM flagged as inactive. esim.deletion_scheduled webhook sent.
Warning period	Days 0–7	7-day window to apply a bundle (or have an existing bundle activate) to cancel deletion.
Deactivated	Day 7	eSIM deactivated at the network level. esim.deleted webhook sent.

Webhook events

Both events are sent to your configured callback URL. Ensure webhooks are set up to receive these notifications.

esim.deletion_scheduled

Sent when an eSIM is first flagged for deletion. You have 7 days to act.

{
  "date": "2026-06-22T13:03:31Z",
  "event": "esim.deletion_scheduled",
  "iccid": "8943108161000670038"
}

esim.deleted

Sent when the eSIM has been permanently deactivated following the 7-day warning period.

{
  "date": "2026-06-29T13:20:02Z",
  "event": "esim.deleted",
  "iccid": "8943108161000670038"
}

Cancelling a scheduled deletion

To cancel the deletion, apply a new bundle to the eSIM before the deletion date shown in the esim.deletion_scheduled event. Assigning an active bundle resets the inactivity clock and removes the eSIM from the deletion pipeline.

Once the esim.deleted event has been sent, the deactivation cannot be reversed.

Recommendations

• Monitor esim.deletion_scheduled events and decide whether to reactivate the eSIM or allow it to be deactivated
• If you have end users who may return after a long gap, store the ICCID and inform users their eSIM may have been deactivated if they haven’t used it in over 180 days