Batching

These endpoints allow you to submit multiple requests in a single call, improving efficiency for various operations. A batch of individual requests sent in the request body will be processed asynchronously in the background. You can then poll the status of the batch request to check if it has been completed and receive a consolidated response for all operations.

Create a batch request

This operation creates a batch request to execute multiple operations asynchronously in a single HTTP request.

SecuritybearerAuth
Request
header Parameters
X-Adobe-Accept-Unsupported-API
required
integer

The X-Adobe-Accept-Unsupported-API request header is required when a client wants to opt-in into using a product-only API, not designed for public consumption. Not providing this header to an endpoint that requires it will make the server answer with a 400 status code.

Value: 1
Request Body schema: application/json
required
Array of objects (SingleRequest) non-empty
Responses
202

The request was accepted for processing and it will be executed asynchronously.

400

Bad Request. The Problem Details object will provide more information about the exact cause.

415

Unsupported Media Type. When provided as a response to a PATCH request, the response will provide an Accept-Patch response header to notify the client what patch document media types are supported.

500

The server encountered an unexpected error. Retrying the request after a certain time could help.

post/cf/batch
Request samples
application/json
{
  • "requests": [
    ]
}
Response samples
application/problem+json
{}

Retrieve the status of a batch request

This operation retrieves the status of a batch request and the results of the operations that were executed.

SecuritybearerAuth
Request
path Parameters
id
required
string

The ID of the Batch Request

header Parameters
X-Adobe-Accept-Unsupported-API
required
integer

The X-Adobe-Accept-Unsupported-API request header is required when a client wants to opt-in into using a product-only API, not designed for public consumption. Not providing this header to an endpoint that requires it will make the server answer with a 400 status code.

Value: 1
Responses
200

The status of the batch request and the results of the operations that were executed.

404

Not Found

406

Unacceptable. indicates that the target resource does not have a current representation that would be acceptable to the user agent, according to the proactive negotiation header fields received in the request.

500

The server encountered an unexpected error. Retrying the request after a certain time could help.

get/cf/batch/{id}
Request samples
Response samples
application/json
{
  • "status": "QUEUED",
  • "responses": [
    ]
}