Changelog

Follow up on the latest improvements and updates.

RSS

You can now publish consumer eSIM profiles to Apple's or Google's discovery service when you assign EIDs. The device then finds its profile on its own, so you no longer send an activation code or push a server address to each device.
What you can do
  • Choose Apple or Android when you assign an EID on a device's eSIM tab, or for a whole bulk upload from Connected Devices.
  • Make the same choice through the API, on the Link by SIM and Link by Product actions.
  • See right away why a publication failed, and assign the EID again.
  • Remove an assignment, and emnify withdraws the profile from the discovery service too.
Assigning a single EID and a bulk upload with a discovery service
How to get started
  1. Order consumer eSIM profiles with EID linking as the installation method.
  2. Assign the device's EID in the Portal or through the API.
  3. Choose Apple or Android.
  4. When the device finds its profile, the person holding it confirms the download.
Discovery service delivery is available now. Read more in the API reference and the EID assignment how-to.
You asked for it. It is here.
Verizon is now available at emnify. Together with AT&T and T-Mobile, your US devices can use all three major networks on one SIM,
on selected data plans.
To get Verizon, talk to your Customer Success Manager or Account Executive.
What you get
  • Strong coverage across the US.
    Each of the three networks has its own strengths, and now your devices can use all of them.
  • More choice for your devices.
    Three networks to choose from, so your deployment is not tied to one network.
  • Nothing to rebuild.
    Same SIM, same portal, same API.
Have you been waiting for Verizon? We are ready when you are.
You can assign a role to every app token, so AI agents, monitoring tools, and other integrations get exactly the access they need and nothing more. Integrate third-party tools with only permissions they need.
What’s new
1. A role on every token.
When you create a token, you choose a role. Start with Admin, Observer, or User. Choosing Admin shows a reminder that the token gets full account access.
2. Expiry is required.
New tokens must have an expiry date. Default is 1 year. Existing tokens with no expiry keep working and still appear in the table with a “never expires” mark.
3. Clearer token table.
Table columns for App token table can be now configured for your preferences. A new column shows whether a token was created by a user or by another token. Expired tokens are clearly marked.
How this affects you
  • Your existing tokens keep working, including ones that never expire.
  • New tokens you create need a role and an expiry date.
  • Observer is a good fit for read-only tools. User fits operational integrations. Use Admin only when the integration truly needs full access.
  • If you manage app tokens through the API, move that code to the v2 application token API by 1 June 2027. Role assignment and the other new fields are on v2 only. Check our migration guide.
  • Custom roles on tokens would be soon available.
How to get started
  1. In the Portal, go to Integrations → Application tokens.
  2. Create a token, pick the role that matches the integration, and set an expiry date.
  3. Use that token in your integrations.
app-token
You can now filter Connected Devices to show only devices that are Blocked. You no longer have to dig through the Event Log to find them.
The new filter shows every device that is blocked right now, however long ago the block happened. This was one of the most requested filters from our customers, so we prioritized it.
What you can do
  • Filter by Blocked in the Portal: under Connected Devices → Connectivity → Blocked, see all currently blocked devices in one list.
  • Combine it with other filters: narrow the list by tag, service policy, name, or ICCID to find the blocked devices in a specific project.
  • Restore service right away: select the blocked devices and use Extend limits to bring them back online for the rest of the month, without changing the service policy.
  • Use it over the API
The Blocked filter is available now.
Screenshot 2026-10-08 at 17
Screenshot 2026-10-08 at 17
You can now retrieve the QR code, activation code, and Apple Universal Link for your eSIM profiles in the emnify Portal, for a single device or for a whole order. No more raising a request and waiting for codes to come back by email.
Why you'll love it
Ordering an eSIM profile was only the first step. Until now, installing that profile meant requesting the activation code from emnify and waiting for it. Manageable for a few profiles, but a bottleneck at scale.
You can now complete the entire workflow yourself: order the eSIM profile, retrieve its activation code, and deliver it directly to the device.
What you can do
  • Choose your installation method at checkout: I will use activation codes or I will link profiles using the EID. Only the first generates codes.
  • Retrieve codes per device: under Connected Devices → select your device → eSIM tab, to view and download the QR code, the activation code, and the Apple Universal Link.
  • Download codes in bulk: from the Order details page, in CSV format, so you can load a full batch into your own systems at once.
  • Pull codes over the API: request the QR code as an image, or the activation code and Apple Universal Link as JSON, from the eUICC profile endpoint.
Here is what you will see in the eSIM tab:
esim-modal-scrubbed
Important:
Activation codes apply to eSIM profiles that you install yourself, whether they land on Consumer (SGP.22) or Advanced (SGP.32) eUICCs. Preloaded profiles and profiles linked by EID do not offer an activation code, because they do not need one.
Activation codes are available now
Head to Connected Devices or your Order details page to retrieve them. For step-by-step guidance see our docs on QR code activation, activation codes, and Apple Universal Link.
You can now save and manage multiple delivery addresses for your account in the SIM Shop and pick the right one at checkout. No more editing a single saved address every time you ship to a different location.
Why you'll love it
If you ship SIMs to more than one place: different manufacturers, warehouses, offices, or your own customers, than you no longer have to overwrite your delivery details for each order. Set up your addresses once, then simply choose where each shipment should go.
What you can do
  1. Add multiple delivery addresses to your workspace (up to 10).
  2. Manage them centrally: under Settings → Organisation Data → Delivery address section: to add, edit, or remove addresses anytime.
  3. Choose the delivery address or add new ones at checkout when placing a SIM order, instead of being limited to your last saved address.
Multiple addresses are available now. Just head to your organisation settings to add your addresses, and you'll see them as selectable options on your next order.
Mult Add
Mult Add#2
By
July 31, 2026
the USSD service will be permanently shut down. After this date the service will no longer be available under any circumstances, and there will be no further extensions.
The USSD service reached its official End-of-Life on January 31, 2024. Since then we have continued running the remaining instances as a temporary grace period to give customers still on USSD additional time to complete their migration. This grace period is now ending.
We strongly recommend that any devices still relying on USSD are switched to mobile data well before the cut-off date. After shutdown, no SLA, support, or service availability will be provided for USSD.
Background:
USSD is a 2G/3G technology based on the SS7 protocol stack. As more network operators sunset their 2G and 3G networks in favour of 4G and 5G, USSD is becoming unavailable in a growing number of markets and is not a future-proof technology. LTE-only modules cannot make use of USSD. For these reasons the service can no longer be sustained.
NewUser InterfaceAPIData StreamerAutomations

New in Automations: Daily Data Threshold trigger

You can now use Daily Data Threshold as a trigger in Automations. It's the first of our new Custom Event Templates - a flexible way to configure events that match how your business actually runs.
Why it matters
Daily data usage doesn't look the same across your fleet. A CCTV camera, an asset tracker, and a smart meter each have very different "normal" and very different "something's wrong." Until now, a single threshold had to fit them all.
With Daily Data Threshold, you can finally match the alert to the use case.
What you can do
  • Set multiple thresholds - configure one or many Daily Thresholds across different projects and verticals (e.g. CCTV cameras, asset tracking, scooters and EV-chargers).
  • Tune severity per threshold - assign the right severity level so the right events stand out in the Event Log.
  • Independent rules per Automation - each threshold lives inside its own Automation, so teams managing different projects don't step on each other.
  • Get real-time alerts - the moment a device crosses its daily limit, the trigger fires and your Automation takes action.
  • Use it for tracking only - you can create the event with just parameters (threshold + severity) and skip notifications entirely. Once triggered, it simply appears in the Event Log, giving you a lightweight way to monitor and audit threshold crossings without generating alert noise.
Example
A logistics customer running two deployments:
  • Asset trackers - alert when a device exceeds 50 MB/day (possible misuse or data leak) → severity Critical
  • CCTV cameras - alert only above 2 GB/day → severity Warning
Both rules run side-by-side, each scoped to the right project, with the right severity in the Event Log.
How to try it
  1. Go to Automations → Create rule
  2. Select Daily Data Threshold as the trigger
  3. Choose data volume and severity
  4. Add your recipients to be notified by email
Screenshot 2026-04-23 at 16
Screenshot 2026-04-23 at 16
daily-data-threshold
We’ve updated the SIM ordering flow so that SIM invoice PDFs are automatically emailed to your "Invoice Address" when an order is completed, no matter which user placed the order.
Whats new
Once a SIM order is completed, we automatically send an invoice copy (PDF) directly to:
  • the Invoice Address registered in the portal, or
  • the Invoice Address entered/edited during checkout.
ImprovedUser InterfaceEvents

Event Log improvements for auditing

We’ve improved the Event Log to
better support auditing of SIM management activities.
For key SIM-related actions, the Event Log now shows
who performed the action
, making it easier to understand changes at a glance and answer questions like “Who suspended this SIM?”.
What’s new
For critical SIM management actions, the Event Log now includes the executing user. You’ll now see “Action performed by” for major actions such as:
  • SIM deletion / released / assigned
  • Endpoint enabled / disable
  • SIM registration / activation / suspension / factory test
image
Load More
→