Authorizations
An API key that grants access to the Connect API. You can create and manage API keys in the portal.
Headers
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.
256
Body
Request to create a new order. Orders can be created with minimal information and progressively configured. User and customer information can be added later, including through mid-flow authentication.
The user who will use the services in this order. To create a new user, provide their details. For a returning user, provide their user ID.
- ExistingUser
- NewUser
Reference to a customer of the order, either an existing customer or to set up a new customer.
- ExistingCustomer
- NewCustomer
Billing information for an order.
For existing customers, we suggest you pre-fill this with the customer's billing information, however it is possible to override this at the order level.
Shipping information for order fulfillment. Only required if the order contains shippable items.
Initial line items for the order (can be empty).
- Subscription
- License
- Add-on
- Top-up
- External Product
- External Item
- Subscription Change
- License Change
- Add-on Change
Promo code to apply to the order.
"SUMMER2023"
A set of key-value pairs that can be attached to an object for storing additional information in a semi-structured format.
Response
Order created successfully
A shopping cart for telecommunications services and products. Add line items to configure services, get pricing, and submit for fulfillment. Orders track progress from creation through completion.
Unique identifier for the order.
"order-123"
The status of an order in its lifecycle.
- PENDING: Order is in cart state, can be modified
- CONFIGURED: Order is complete and ready for submission
- SUBMITTED: Order has been submitted for processing
- PENDING_APPROVAL: Order is pending approval
- PROCESSING: Order is being fulfilled
- COMPLETED: Order has been successfully fulfilled
- CANCELLED: Order was cancelled before completion
- EXPIRED: Order expired due to inactivity
PENDING
, CONFIGURED
, SUBMITTED
, PENDING_APPROVAL
, PROCESSING
, COMPLETED
, CANCELLED
, EXPIRED
Line items in the order.
- Subscription
- License
- Add-on
- Top-up
- External Product
- External Item
- Subscription Change
- License Change
- Add-on Change
When the order was created.
"2024-01-15T10:00:00Z"
When the order was last updated.
"2024-01-15T10:30:00Z"
The user associated with this order. Includes minimal details about the user and creation details if the user was created during order fulfillment.
The customer associated with this order. Includes minimal details about the customer and creation details if the customer was created during order fulfillment.
Billing information for an order.
For existing customers, we suggest you pre-fill this with the customer's billing information, however it is possible to override this at the order level.
Shipping information for order fulfillment. Only required if the order contains shippable items.
Promotional code applied to this order, if any.
"STUDENT2024"
Customer consents and acknowledgments.
{
"termsOfService": "true",
"marketing": "true"
}
The price of an order. In regions with complex tax rules (e.g., the US), you need to call the price calculation endpoint to get accurate tax amounts before submitting the order. In other regions, tax is dependent on customer type but typically included.
Validation status of the order and its line items.
Requirements to submit the order. All listed requirements must be met before the order can be submitted.
What is required depends on platform configuration and the contents of the order.
For example, a prepaid order with only free items would not require payment, it could however require card capture. Postpaid orders typically either require card capture or signing.
When the order expires if not submitted (automatically refreshed on each order update to maintain active session).
"2024-01-22T10:30:00Z"
When the order was submitted for fulfillment.
"2024-01-15T14:30:00Z"
When the order was completed.
"2024-01-15T15:00:00Z"
Entities created as part of order fulfillment.
A set of key-value pairs that can be attached to an object for storing additional information in a semi-structured format.