Create a new subscription for a customer.
Activation Modes:
Immediate Activation
Scheduled Activation
Deferred Activation (Shell Subscription)
Common use cases:
Note: This endpoint may be disabled when Seamless OS manages billing. In that configuration, subscriptions are created through the orders endpoint instead.
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.
256Create a new subscription for a customer.
Activation Options:
When to use shell subscriptions:
Note: This endpoint is disabled when Seamless OS manages billing. In that case, subscriptions are created through orders.
The unique identifier for the product offering to subscribe to.
This controls what type of subscription is being created.
The unique identifier for the existing customer who will own this subscription.
Subscriber details for this subscription.
Configuration and details required to activate a subscription in the telecommunications network.
This includes the phone number (MSISDN), SIM card details, and optional number porting information. All subscriptions require this activation data before they can be used for telecommunications services.
Activation configuration for this subscription.
When to provide:
Use cases:
Date when the subscription should be activated in the network.
Only applicable when activation data is provided. If omitted, activation will be immediate or as soon as network resources are available.
Note: Network availability and porting timelines may affect the exact activation time. This date is a preference, not a guarantee.
"2024-01-15"
Additional subscription extensions fields for custom subscription types.
Custom display name for the subscription. If not provided, will be auto-generated from msisdn.
A set of key-value pairs that can be attached to an object for storing additional information in a semi-structured format.
The created subscription.
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.