OCAPI Batch Requests 23.1

An OCAPI batch request is a multipart HTTP request that can contain up to 50 subrequests. Each subrequest (part) must operate on a single resource; subrequests that specify multiple ids (for example, '/products/(p1,p2...)') are forbidden.

Batch requests reduce network overhead by reducing the overall amount of information transmitted and by reducing the number of calls you have to make. For example, to build an application screen, you can construct a single large multipart batch request instead of constructing numerous smaller individual OCAPI requests.

The HTTP method used for the batch request as a whole must be POST or OPTIONS. Each subrequest can specify a different HTTP method if necessary.

Each batch request has a main header section. In this section, you must include a Content-Type header that specifies a type (multipart/mixed) and a boundary separator that is used to delimit each subrequest. For example:

Every header included in the main header section of the batch request is implicitly inherited by each subrequest. The query parameters of the main batch request are also implicitly inherited by each subrequest.

Each subrequest, however, is conceptually a complete OCAPI request with its own resource path, header section, and request body. If needed, a subrequest can override its inherited headers and its inherited query parameters.

To specify the behavior of subrequests and to define the mapping between requests and responses, you must specify the following headers where appropriate:

Header nameLocationDescription
x-dw-http-methodrequest, subrequestSpecifies the HTTP method used to access the resource.
x-dw-resource-pathrequest, subrequestSpecifies the base resource path. The value of this header is combined with value of the x-dw-resource-path-extension header to provide a complete resource path.
x-dw-resource-path-extensionrequest, subrequestSpecifies an extension for the value of the base path, as specified by the x-dw-resource-path header. This header is optional if the base resource path already represents a valid OCAPI resource.
x-dw-content-idsubrequest, subresponseSpecifies an ID of the subrequest. This header value is used to map a subrequest to a subresponse.
x-dw-status-codesubresponseSpecifies the status code of a single subresponse.

Batch requests are supporting CORS. Allowed expose headers and origins are mentioned in OCAPI settings for each client ID. To access them, it’s mandatory to send a batch request for a specific client in a context, either of a specific site or global. There are several possibilities to pass a client identification:

  1. Client ID as query parameter
  2. Client ID as x-dw-client-id header
  3. OAuth access token via Authorization header
  4. JWT via Authorization header

Subrequests in a batch request body adhering to the standard defined in Multipart Media Type. This approach means that the header section in a Multipart subrequest has to follow directly after the Multipart boundary. The header section and the Multipart body section have to be separated by two subsequent newline characters.

Example 1

Correct formatted subrequest.

Example 2

Wrong formatted subrequest. Only one newline after header section.

Example 3

Wrong formatted subrequest. Two newlines after boundary lead to an empty header section.

Example 1

This example shows how you can access multiple resources of the same type:

Example 2

This example shows how you can access resources of different types:

The site context for each request can be defined in x-dw-resource-path or x-dw-resource-path-extension. If no site context is given in these headers, the one from the main request is taken. This implies, that the site context from the main request can be overwritten by the resource path headers.

The size of the batch request body is limited to 5 MB. The maximum number of subrequests is 50.

Exeption nameStatus codeDescription
IllegalContentTypeException400Thrown if the request content type isn’t multipart/mixed or specifies no boundary.
IllegalQueryStringException400Thrown if the query string for the request or a subrequest is invalid.
InvalidAuthorizationHeaderException401Thrown if the authorizarion header has not the format Authorization: Bearer ...
InvalidHttpMethodException400Thrown if the HTTP method in the request header or subrequest header is invalid.
InvalidRequestBodyException400Thrown if the request body is invalid.
InvalidTokenException401The token sent via Authorization: Bearer header is invalid or expired.
MethodNotAllowedException405Thrown if the batch request was sent with an HTTP method other than POST or OPTIONS.
MissingClientIdException400Thrown if no client identification was sent with the main request (either as client ID or authorization token).
MissingHttpMethodException400Thrown if at least one subrequest has no HTTP method.
MissingResourcePathException400Thrown if at least one subrequest has no resource path.
QuotaExceededException400Thrown if the batch request contains more than 50 subrequests.
RequestEntityTooLargeException400Thrown if the batch request body is larger than 5 MB.
ResourcePathNotAllowedException400Thrown if at least one subrequest is a multiple-ID resource call.
UnauthorizedOriginException401Thrown if the given origin isn’t mentioned in the OCAPI settings for the accessing client.
UnknownClientIdException401Thrown if the given client identification isn’t known to the account manager.
UnknownSiteIdException400Thrown if the request was sent in the context of an unknown site name.