Release 4.18.0 - June 11, 2025

New Features

SubscribeAddon API

• The new “SubscribeAddon” API will allow to assign an Addon to an endpoint.

  • Enables adding or removing a single addon to an endpoint.

  • Only applicable to endpoints. Only one addon can be subscribed at a time.

  • Note: This function is also possible via the Modify Endpoint API. Goal to have a new “SubscribeAddon” API is to have this specific for that function while the Modify Endpoint API can modify all parameters on the endpoint.

• Success Response:

  • Includes promotional plan details, benefit details, addon details (uniqueId), and counter details associated with the addon.

Endpoint Event for SubscribeAddon API

• New Notification: Introduces a new event, "Addon Activation", triggered when an on-usage or immediate addon is activated.

• Event Scenarios: (If the endpoint addon is configured with 2 notification Activation and Subscription)

  • If the endpoint addon - Activated By is set to “On Usage”, only the subscription occurs. The "Addon Subscription" notification is triggered. Once data usage is initiated by the endpoint then the "Addon Activation" notification will also be triggered.

  • If the endpoint addon - Activated By is set to “Immediate”, both subscription and activation occur simultaneously. Both "Addon Subscription" and "Addon Activation" notifications are triggered.

  • For an OEM account, the new Addon subscription/Activation notification will be triggered only when Endpoint moving to the Active state.

Enhancements

eSIM HUB

• Times out on the local operator's system, the system will now verify whether the suspension or activation was successful.

  This improvement ensures that the status of endpoints with a local profile is accurately reflected, even in cases where the initial action encounters a timeout.

Callback URL

To ensure seamless integration with our callback stream feature, we have modified the URL length and path segment length. Please follow these guidelines:

• New maximum URL Length: Must not exceed 2,000 characters. (was 355 chars)

• New Path Segment Length: Each segment (between slashes /) must be no longer than 255 characters. (was 50 chars)

• Scheme Requirement: Only https:// URLs are accepted.

• Allowed characters: Only below mentioned special characters are allowed, except these characters, no other special characters are allowed in the URL.

  • dot .

  • hyphen -

  • underscore _

  • forward slash /

  • colon : When colon character is used when port number is used in the URL. 

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