An integration can include many create, read, update, patch, and delete operations for reference records in one API request, instead of calling the API once for each reference.
How a Batch Runs
Each operation in a batch goes through the same checks Rhythm uses when that operation runs by itself. Validation, permissions, and all other rules still apply.
Operations run in parallel, not in the order you list them. Do not send a batch where one operation depends on another finishing first, because Rhythm does not guarantee a sequence.
Reading the Result
Rhythm reports the outcome of each operation separately. One operation in a batch can fail while the others succeed, so review each operation’s result instead of treating the batch as one all-or-nothing result.
Tip
Because operations do not run in a guaranteed order and each one is checked on its own, split the work into smaller requests if you need to create a reference and then immediately act on it. Send the create first, confirm it succeeded, and then send the follow-up operation.