- Create a payout request batch
Creates a batch of payout requests for batch processing.
The batch links multiple payout requests together so they can be auto-allocated and processed together. Each payout request can be assigned to only one batch. If any of the specified payout requests are already included in another batch, a 409 Conflict error is returned.
Both approaches are limited to a maximum of 1000 payout requests per batch.
Two mutually exclusive approaches are supported:
- Explicit IDs: Provide an array of payout request IDs in the
payoutRequestIdsfield. - Filter-based: Provide a
filterstring to select payout requests that match the specified criteria at execution time. Payout requests that are already included in a batch are automatically excluded from the filter results. If more than 1000 payout requests match the filter, only the oldest 1000 are included in the batch, sorted by creation time. To view the number of matching items before creating the batch, use the Preview payout request batch filter results operation.
Resource for the payout request batch.
- Mock serverhttps://www.rebilly.com/_mock/catalog/all/payout-request-batches
- Sandbox serverhttps://api-sandbox.rebilly.com/organizations/{organizationId}/payout-request-batches
- Live serverhttps://api.rebilly.com/organizations/{organizationId}/payout-request-batches
- SecretApiKey
- JWT
- Explicit IDs
- Filter-based
curl -i -X POST \
https://www.rebilly.com/_mock/catalog/all/payout-request-batches \
-H 'Content-Type: application/json' \
-H 'REB-APIKEY: YOUR_API_KEY_HERE' \
-d '{
"payoutRequestIds": [
"pout_req_0YVDMDE2BMC6KBB5MX76RF6T80"
],
"description": "Batch processed on 2024-01-15"
}'Payout request batch created.
Total number of rate limit tokens for this request within a rate limit period. For more information, see Rate limits.
ID of the user who created the batch.
Optional description of the batch.
Order for auto-allocation of payout requests in this batch. When set, this field overrides the organization-level allocation order during batch auto-allocation. Must contain selected-payment-instrument exactly once. Valid values: payment-card (payment cards), alternative-payment-methods (catch-all for alternative payment methods), selected-payment-instrument (customer-requested instrument), or any payment method API name (for example, paypal, Interac-eTransfer).
[ "paypal", "Interac-eTransfer", "payment-card", "alternative-payment-methods", "selected-payment-instrument" ]
{ "id": "preq_batch_0YVDMDE2BMC6KBB5MX76RF6T80", "userId": "usr_0YVCEENYJ3D7Q9EN6BN16HA0G4", "totalCount": 10, "customerCount": 3, "totalAmountByCurrency": [ { … } ], "description": "Batch processed on 2024-01-15", "allocationOrder": [ "paypal", "Interac-eTransfer", "payment-card", "alternative-payment-methods", "selected-payment-instrument" ], "createdTime": "2019-08-24T14:15:22Z", "updatedTime": "2019-08-24T14:15:22Z", "_links": [ { … } ] }