POST /settings/batch-requests
Submit a batch of settings requests by this single API operation.
By default, one batch settings request can contain a maximum of 100 single operation requests, including:
- All the single requests in the process batch settings request.
- All the children requests of the single requests.
This maximum value is configurable.
Servers
- https://rest.test.zuora.com
- https://rest.sandbox.na.zuora.com
- https://rest.apisandbox.zuora.com
- https://rest.na.zuora.com
- https://rest.zuora.com
- https://rest.test.eu.zuora.com
- https://rest.sandbox.eu.zuora.com
- https://rest.eu.zuora.com
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Content-Encoding |
String | No |
Include the |
Zuora-Track-Id |
String | No |
A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue. The value of this field must use the US-ASCII character set and must not include any of the following characters: colon ( |
Authorization |
String | Yes |
The value is in the |
Idempotency-Key |
String | No |
Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types. With this header specified, the Zuora server can identify subsequent retries of the same request using this value, which prevents the same operation from being performed multiple times by accident. |
Zuora-Entity-Ids |
String | No |
An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you do not need to set this header. |
Zuora-Org-Ids |
String | No |
Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header. The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails. If the header is not set, the operation is performed in scope of the user's accessible orgs. |
Accept-Encoding |
String | No |
Include the If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
requests[] |
Array | No | |
requests[].id |
String | No |
The id of the request. You can set it to any string. It must be unique within the whole batch. |
requests[].method |
String | No |
One of the HTTP methods supported by the setting endpoint, for example, GET,PUT,POST or DELETE. Possible values:
|
requests[].url |
String | No |
The relative URL of the setting. It is the same as in the |
requests[].body |
Object | No |
Request payload if any |
requests[].children[] |
Array | No |
An array of requests that can only be executed after its parent request has been executed successfully. |
requests[].children[].id |
String | No |
The id of the request. You can set it to any string. It must be unique within the whole batch. |
requests[].children[].method |
String | No |
One of the HTTP methods supported by the setting endpoint, for example, GET,PUT,POST or DELETE. Possible values:
|
requests[].children[].url |
String | No |
The relative URL of the setting. It is the same as in the |
requests[].children[].body |
Object | No |
Request payload if any |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.