- Add requests to a payout request batch
Adds payout requests to a batch with a specified ID. Accepts payout requests in any status, with or without allocations. A batch contains a maximum of 1000 payout requests.
Provide exactly one of the following fields:
payoutRequestIdsto add specific payout requests.filterto add payout requests that match the filter when the operation runs.
If any explicitly specified payout request is already associated with a batch, the operation returns a 409 Conflict response. Filter results exclude payout requests that are already associated with a batch. If more payout requests match the filter than the batch can contain, the operation adds only the oldest matching requests up to the batch limit, sorted by creation time. If adding explicitly specified payout requests would increase the batch to more than 1000 requests, the operation returns a 409 Conflict response. If the batch has reached its payout request limit, the operation returns a 409 Conflict response for either selection method. This operation is atomic. If a conflict occurs, the operation adds no payout requests to the batch.
- Mock serverhttps://www.rebilly.com/_mock/catalog/all/payout-request-batches/{id}/payout-requests
- Sandbox serverhttps://api-sandbox.rebilly.com/organizations/{organizationId}/payout-request-batches/{id}/payout-requests
- Live serverhttps://api.rebilly.com/organizations/{organizationId}/payout-request-batches/{id}/payout-requests
- SecretApiKey
- JWT
- Explicit IDs
- Filter-based
curl -i -X POST \
'https://www.rebilly.com/_mock/catalog/all/payout-request-batches/{id}/payout-requests' \
-H 'Content-Type: application/json' \
-H 'REB-APIKEY: YOUR_API_KEY_HERE' \
-d '{
"payoutRequestIds": [
"pout_req_0YVDMDE2BMC6KBB5MX76RF6T80"
]
}'Payout requests added to the batch.
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": [ { … } ] }