Change an existing add-on to a different product offering (upgrade or downgrade).
This endpoint allows you to change an existing add-on attached to a subscription to a different add-on product offering. The change can be scheduled for immediate or future execution.
When the change takes effect depends on the new product offering chosen, billing cycle, and the preferred schedule date provided in the request.
An API key that grants access to the Connect API. You can create and manage API keys in the portal.
A unique key to ensure idempotency of requests. If a request with the same key has already been processed, the same result will be returned. The key must be unique for each distinct operation. Keys are expired after 24 hours, but we recommend using a new key for each request.
Modified requests with the same idempotency keys are rejected with a 409 Conflict status code.
256The unique identifier of the subscription.
Request to change an existing add-on to a different product offering.
The unique identifier of the new add-on product offering to change to.
"addon-data-5gb"
Earliest date to perform the change on. If the change schedule doesn't fit this date, the earliest date after this will be chosen.
"2024-02-01"
Reason for the change.
"Customer upgrade request"
A set of key-value pairs that can be attached to an object for storing additional information in a semi-structured format.
Add-on change scheduled successfully.
A subscription represents a telecommunications service provisioned for a customer with embedded product and pricing details.
The unique identifier for the subscription.
The status of the subscription.
PENDING, ACTIVATED, BLOCKED, CANCELLED, PAUSED The type of subscription, categorizing the service into various telecommunications service types.
The display name for the subscription, typically a pretty-print of the msisdn.
The currently active phone number for this subscription.
Customer information embedded in responses. Sensitive details require separate API calls with appropriate authorization.
Embedded representation of a product offering.
SIM card information for the subscription. Sensitive details like PUK require separate API calls.
Use dedicated SIM API endpoints with proper authorization to access sensitive information such as PUK.
The date and time when the subscription was activated.
The date and time when the subscription was created.
The date and time when the subscription was last updated.
A subscriber is a user that has a subscription.
Additional subscription extensions fields provided for custom subscription types.
Details about when a pending phone number change is scheduled for this subscription.
Details about when a pending status change is scheduled for this subscription.
Pending product offering change.
Number porting information for subscriptions, indicating scheduled number transfers.
To get the detailed porting information, use the porting endpoint.
The date and time when the subscription was cancelled (if applicable).
A set of key-value pairs that can be attached to an object for storing additional information in a semi-structured format.