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
Path Parameters
The unique identifier of the order
Body
Request to submit an order for fulfillment.
Depending on the order's requirements, payment intent, saved payment profile, or signing reference may be required.
In a fully managed flow, the order may be auto-submitted on successfully fulfilling all requirements (e.g. successful payment or signing).
Reference to completed payment session for orders requiring payment collection.
"a1b2c3d4-e5f6-7890-1234-56789abcdef0"
Reference to completed payment profile session for zero-total orders requiring payment method setup.
"b2c3d4e5-f6a7-8901-2345-6789abcdef01"
Reference to completed signing session.
"c3d4e5f6-a7b8-9012-3456-789abcdef012"
A set of key-value pairs that can be attached to an object for storing additional information in a semi-structured format.
Response
Order submitted 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.