Partner Orders
OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.
Obtain a token via the OAuth flow described in OAuth Bearer Token.
Pass the token in the Authorization header: Bearer <token>
Order submitted successfully.
Response returned after successfully submitting an order.
Unique identifier of the created order.
order-4dd195c3eee4297e33aecb5436cf8092Human-readable order reference code.
8HK92PL401QWProcessing status of the order.
completePossible values: The external order reference provided in the request, if any.
EXT-ORD-12345Reference code of the subscription created or modified by this order.
2TJ25TK632EGThe identity ID that owns objects created by this order.
id-62401f8d5bf6b26a37ea0defd66fd005Invalid order payload.
Unauthorized — the request lacks valid authentication credentials. Verify your Bearer token or API key is correct and has not expired.
Not found.
Bad Gateway — an upstream service returned an unexpected response. This typically indicates an issue with the request payload (e.g. invalid field values, missing required fields) or a transient infrastructure error. Retry the request, and if the issue persists, verify the request body matches the expected schema.
OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.
Obtain a token via the OAuth flow described in OAuth Bearer Token.
Pass the token in the Authorization header: Bearer <token>
Order payload to preview.
Order preview with calculated pricing.
Preview result from the billing provider. Structure varies by billing plugin (Zuora, Stripe).
Unauthorized — the request lacks valid authentication credentials. Verify your Bearer token or API key is correct and has not expired.
Bad Gateway — an upstream service returned an unexpected response. This typically indicates an issue with the request payload (e.g. invalid field values, missing required fields) or a transient infrastructure error. Retry the request, and if the issue persists, verify the request body matches the expected schema.
Last updated
Was this helpful?

