List all orchestrations, optionally filtering and paging the results.
By default, orchestrations are returned in reverse chronological (descending) order by creation time. If no query parameters are supplied, the response will include up to the last 100 orchestrations which were created.
The paginated results default to display up to 100 orchestrations, unless
otherwise specified with the limit
parameter. The maximum limit
value is 1000.
Every paginated response contains a next_page_cursor
field until the last page is reached.
Pass the next_page_cursor
value into the page_cursor
field of a new
request to retrieve the next page of results.
When filtering by profile IDs using the profile_ids
parameter, there is a limit of 100 profiles
that can be specified in a single request.
Orchestrations are provided for various operations including:
The access token received from the authorization server in the OAuth 2.0 flow.
Optionally filter by the initiating orchestration_rule_ids.
Optionally filter by source assets
Optionally filter by destination assets
Optionally filter by statuses.
Include timestamps strictly less than lt. RFC3339 format, like 2006-01-02T15:04:05Z
.
Include timestamps less than or equal to lte. RFC3339 format, like 2006-01-02T15:04:05Z
.
Include timestamps exactly equal to eq. RFC3339 format, like 2006-01-02T15:04:05Z
.
Include timestamps greater than or equal to lte. RFC3339 format, like 2006-01-02T15:04:05Z
.
Include timestamps strictly greater than gt. RFC3339 format, like 2006-01-02T15:04:05Z
.
Number of results to return. Defaults to 100 if no limit is provided. Maximum 1000.
Sort order for the results. Defaults to DESC by created_at time.
DESC
, ASC
Optional Cursor for getting the next page of results.
Optionally filter by a list of orchestration IDs.
Optionally filter by the target profiles. Limit 100.
A successful response.
The response is of type object
.