Device status management
SIM activation
The SIM is patched to the Activated status after previously holding one of the following statuses: Issued, Suspended, or Factory Test.
You can manually trigger this event by using the emnify Portal or REST API. Or, it’s automatically triggered when the factory test mode threshold (data or SMS) is reached.
Activated SIMs can use network services.
Example JSON response: SIM status changed from Suspended to Activated
Example JSON response: SIM status changed from Suspended to Activated
Example JSON response: SIM activation after Factory Test volume reached
SIM suspension
The SIM is patched to the Suspended status, temporarily suspending and blocking it from network access. Starting from the first day of the next month, the suspended SIM doesn’t accrue any charges.
Activating a SIM with the Suspended status again is possible at any time.
Example JSON response
SIM deletion
The SIM is deleted and permanently removed from the SIM inventory.
Once deleted, the SIM cannot be restored for network access.
Endpoint enabled
Device is enabled.
Example JSON response
Endpoint disabled
Device is disabled.
Example JSON response
SIM factory test
SIM is patched from Issued to Factory Test status (for SIM testing).
Example JSON response
SIM registration
SIM or SIM batch is registered to a Workspace via a Batch Identification Code (BIC).
This event doesn’t trigger when the emnify team assigns SIMs to a Workspace. It also doesn’t trigger for every SIM of a SIM batch, so the events log is only be visible on the individual SIM when registering single SIM batches.
Example JSON response
SIM Released
SIM is released from a device.
Triggered through the emnify User Interface (EUI) or REST API.
Example JSON response
SIM Assigned
SIM is assigned to a device.
Triggered through the emnify User Interface (EUI) or while creating an endpoint using the emnify REST API.
Example JSON response
Reset connectivity
An action to reset a device’s connectivity was triggered. Resetting device connectivity resets the network state and allows the device to freshly reattach.
For more details on the subsequent series of events, see Reset connectivity in Device troubleshooting.
Example JSON response in the origin Workspace
SIM migration
One or more SIMs were transferred from a source Workspace to a target Workspace. This action generates two separate events:
- A source event in the originating Workspace, indicating which SIMs were transferred and where they were moved.
- A target event in the destination Workspace, confirming the receipt of the transferred SIMs.
Transfers may impact SIM status and billing, as described in the SIM transfer guide.