Release 4.19.0 - September 25, 2025

New Features

New GetEndpointAddonDetails API

We’ve introduced a new lightweight API called GetEndpointAddonDetails, designed to simplify access to addon-specific information for a given endpoint.

• Mandatory parameter:

  • endpointId – required to identify the target endpoint.

• Optional parameters:

  • addonId or uniqueId – can be used alongside endpointId to refine the query and retrieve specific addon details.

Recommended for all addon-related use cases
For scenarios where you need details about an addon, we strongly recommend using this API instead of the more general GetEndpointProfile API. It’s optimised for performance.

Start using GetEndpointAddonDetails today to streamline your integration and improve response efficiency.

SGP.32 testing available now

As part of our ongoing commitment to support the latest eSIM standards, Release 4.19 introduces our SGP.32 testing environment, including a compliant eUICC and eSIM IoT Remote Manager (eIM). This solution is currently available as a standalone setup, allowing to test and developing new SGP.32 use cases. Full integration into SIM for Things is planned for upcoming releases.

Interested in exploring SGP.32? Reach out to your account manager to get started.

Why SGP.32? Improvements:

SGP.32 brings significant improvements over previous standards like SGP.02:

• Broader profile availability without the need for complex integrations with local MNO platforms (no SM-SR/DP dependencies).

• No SMS requirement, making it ideal for NB-IoT devices that do not support SMS.

• Support for constrained IoT protocols such as MQTT, COAP, and UDP—perfect for smart meters, industrial sensors, and other low-power devices.

• Infrastructure readiness through our eSIM IoT Remote Manager (eIM) and SGP.32-compliant eUICC modules, enabling dynamic profile switching and remote management.

Learn more about SGP.32: https://www.bics.com/blog/sgp-32-explained-next-gen-esim-for-enterprise-iot/

Enhancements

Usage and Mobility events with tracking

We’ve introduced new capabilities to help customers monitor and recover missing records in the callback APIs for Usage and Mobility events.

What’s new:

• Two new fields added to the callback response:

  • "Date": Represents the UTC date of the callback.
    Example: "Date": "20250417"

  • "callbackIndex": A daily auto-incremented index that resets at midnight UTC.
    Example: "callbackIndex": "0000001"

These enhancements mark the first step towards improved resilience in our callback APIs. With the ability to track missing records, customers will gain better visibility and control over event delivery.

Coming next:
In the upcoming release, we’ll introduce a new retrieval method that allows to fetch any missing callback files for Usage and Mobility events directly.

Changes

DeletePlan API

As part of a future improvement of the Plan management we adapted the DeletePlan API structure.

The current DeletePlan API is planned to be deprecated with the next release: https://sft.bics.com/api/DeletePlan

Example

{ 
  "Request":{ 
    "requestParam":{ 
    "planId":"615510"
    }
  }
}

• the new API to delete a plan has the structure below: https://sft.bics.com/api/DeleteRatePlan

Example

 {
  "Request": {
    "plan": {
      "basicInfo": {
      "planId": "615510"
      }
    }
  }
}

For API related changes and bug fixes you can check the API documentation here: https://api.sft.bics.com