Activates items across many orders at once - perfect for processing monthly contract starts, scheduled go-lives, or end-of-quarter activations.

Every entry must supply OrderId, at least one order line item identifier, and a
ReadyForActivationDate; the whole request is rejected with 400 Bad Request if any entry is
incomplete.

Unlike the single-order activate endpoint, isAsync is honoured directly here:
false processes the activations in the request thread and returns the outcome per order, while
true queues the work and returns a job identifier that can be polled through the job status
endpoints.

Note that this endpoint is routed at /orders/orderlineitems/activate and is not scoped to a
single parent order, since each entry names its own order.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
boolean
Defaults to false

Strongly recommended to set this to true for processing 50 or more items. True means you get immediate confirmation and processing happens in the background. False means you wait for everything to complete before getting results. Defaults to false when omitted

Body Params

Your list of orders to activate. For each order, specify: the order number/ID, which items to activate, and when activation should take effect. Each order can have a different activation date

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Responses

204

No Content

500

Internal Server Error

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain
application/json
text/json