Breaking
Activation Orders with Port-In – New On-Hold Order Type
·By eliasramos
New Activation Order Type for Port-In
A new order type has been introduced to support subscription activation using a ported-in number, allowing partners to onboard users without issuing a temporary MSISDN.
Orders created with on_hold_condition = porting now enter an On Hold state immediately after subscription creation. This gives partners full control to start and manage the port-in process while the order waits safely.
Key Capabilities
Non-Breaking Changes
New On-Hold Order Flow
- A new order flow allows activation to pause until the port-in is completed.
- Partners receive the subscription via webhook and can initiate the port-in whenever appropriate.
New Webhooks
order.on_hold– triggered when the order enters On Hold.- Existing porting webhooks (e.g.,
porting.completed,porting.failed) now apply naturally within this flow.
Manual Resume Supported
Partners may manually resume the order using:
POST /orders/{orderId}/resume
- If port-in is completed → activate with ported MSISDN
- If not completed → fallback activation using a temporary MSISDN
Automatic Resume (Optional)
Automatic resume of the order after port-in completion can be enabled.
Partners must request this configuration through support so we can enable it server-side.
Breaking Changes ⚠️
The following breaking changes are introduced from version 2026-02-05 onwards:
- The
Pending First Usageproduct status has been replaced by a genericPendingstatus - A new
reasonfield is introduced to differentiate activation flows:First Usage ActivationActivation with Porting