SIM lifecycle management
When selling connected devices, it's difficult to determine when devices are in use and when not. Using SIM cards that can't align with the device lifecycle incur unnecessary costs. emnify SIM cards don't incur any costs unless activated.
After the registration, the SIMs move between the different states depending on your needs and requirements.
SIM states
The SIMs have five different states that can be configured via the SIM Inventory in the emnify Portal or the emnify SIM REST API:
| State | Description |
|---|---|
| Issued | Initial state after the SIM has been registered to an account. The SIM isn't usable in this state, so it won't generate traffic or incur charges. Issued SIMs can be tested by patching them to the Factory Test state. It's impossible to transition the SIM back to Issued once it has been in another state. |
| Activated | The SIM is enabled and can use network services if connected to a device with configured policies. Regardless, the SIM is chargeable if activated anytime during the month. |
| Suspended | Temporarily blocks an Activated SIM from network access. Starting from the first day of the next month, the suspended SIM doesn't accrue any charges. The SIM can be reactivated and suspended again at any time. |
| Factory Test | The SIM is enabled and can generate traffic. It can be used up to defined data and SMS thresholds without incurring charges. Once either threshold is crossed or the test period has elapsed, the SIM automatically moves to the Activated state. For more information, see Factory test mode. |
| Deleted | Permanently removes the SIM from the SIM Inventory. Once deleted, it can't be restored for network access. |
If you're using the emnify REST API to configure devices, it's possible to have an Activated SIM assigned to a Disabled endpoint. In this case, you'll continue to accrue costs as emnify charges for activated SIMs. Be sure to suspend the assigned SIM to avoid unexpected charges.
You can also check the Portal Dashboard to see if you have unused but charged SIMs.
Reference: Endpoint Object and Endpoint API