List payout batches
Your runs, newest first.
Path parameters
orgIdstringRequiredThe opaque organization id issued to you, normally CUID-shaped (for example
cmsx…). It is not anorg_-prefixed alias. Pass it unchanged in every organization-scoped path.
Query parameters
statusstringOptionalOne batch status to filter by.
Allowed values:receivedvalidatingawaiting_confirmationcreatingShow 3 more values
completedcanceledfailedexternalReferenceIdstringOptionalExact match on your own run id.
limitintegerOptionalDefaults to50Page size, 1-100. Defaults to 50. Outside the range is a
400, not clamped.cursorstringOptionalThe
nextCursorfrom your previous page. A cursor we did not issue is a 400, never an empty page.
Responses
200One page of batches.
Body
dataarray of objectRequiredShow 10 properties
batchIdstringRequiredexternalReferenceIdstring | nullRequiredYour own run id, echoed back.
statusstringRequiredA batch moves
received->validating-> eithercreating(autoCommit, zero errors) orawaiting_confirmation(anything else) ->creating->completed.canceledis reachable until creation starts;failedmeans the run broke, not a line. The batch tracks creation; payouts settle on their own lifecycle afterwards.Allowed values:receivedvalidatingawaiting_confirmationcreatingShow 3 more values
completedcanceledfailedautoCommitbooleanRequiredcountsobjectRequiredLines by status. The values sum to the number of lines submitted.
Show 8 properties
receivedintegerRequiredinvalidintegerRequiredvalidatedintegerRequiredcreatingintegerRequiredcreatedintegerRequiredcreate_failedintegerRequiredcanceledintegerRequiredrequires_reviewintegerRequired
estimatedSourceTotalstring | nullRequiredAdvisory. What the valid lines will draw from your balance, set when validation finishes; null while validation is running and when any line locks the destination side (no rate is consulted at validation time). Compare against
GET /balancebefore confirming. Half a paid payroll is worse than none.errorobjectOptionalPresent only when
statusisfailed, with the run-level reason.createdAtstring<date-time>RequiredupdatedAtstring<date-time>RequiredcompletedAtstring<date-time> | nullRequired
hasMorebooleanRequirednextCursorstring | nullRequiredPass as
cursorto continue. Null on the last page.
Errors
400VALIDATION_ERROR: a query parameter was refused, anderrorsnames it. Alimitoutside its range is refused, not clamped; acursorwe did not issue for this organization is refused (start from the first page); an unknown filter value or a parameter sent twice is refused.401The key was refused. Nothing ran.
UNAUTHORIZED: missing, invalid or revoked, or a key on a route that does not accept one.KEY_EXPIRED: the key passed the expiry it was issued with. Issue a new one; an expired key cannot be rotated.KEY_IP_NOT_ALLOWED: the key is pinned to source addresses and this request came from another.
403A valid key that may not make this call. Nothing ran.
FORBIDDEN: the key belongs to a different organization.ACCOUNT_BLOCKED: API access for your organization is suspended, and every key is refused until we lift it. Contact support.
429Too many requests. The default ceiling is 100 requests per minute per API credential on a 60-second window. High-volume payout and reconciliation routes declare a 600/minute override, and batch submission a 30/minute ceiling. A separate 2,000/minute per-source-IP abuse ceiling always applies.
Obey
Retry-After; it is in seconds and is authoritative. A 429 means the request was refused before the handler ran. Retry reads normally; retry an idempotent mutation with its sameIdempotency-Key.
Error body · Error
typestringRequiredStable machine-readable code.
detailstringRequiredWhat went wrong, in a sentence. Always a string, so
detail.toLowerCase()is safe.More
This is the field to read on
BAD_REQUESTandPROVIDER_REJECTED, where the type alone does not name the condition.messagestringRequiredThe same text as
detail, kept for integrations written beforedetailexisted. Readdetail.resolutionstringOptionalWhat to do about it, when there is a specific answer. It is not on every error (it is absent on
BAD_REQUEST,NOT_FOUND,PAYOUT_NOT_CANCELABLEandDESTINATION_ACCOUNT_NOT_FOUND), so treat it as optional and fall back todetail.statusintegerRequiredHTTP status, repeated in the body.
statusCodeintegerRequiredThe same value as
status, kept for integrations written beforestatusexisted. Readstatus.requestIdstringRequiredQuote this to support and we can find the exact request. Also sent as the
x-request-idresponse header, which is the only place it appears on a successful response. Success bodies do not carry it. Send your ownx-request-idon the request and we use it, so your trace and ours share one identifier; otherwise we mint one.errorsarray of stringOptionalPresent on VALIDATION_ERROR; names each field that failed.
originalIdempotencyKeystringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. Send the request again with this to receive the original payout instead of making a second one. Without it there is no way to recover except by risking a double payment.originalPayoutIdstringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. The payout the first request created.originalBatchIdstringOptionalOn a batch
DUPLICATE_REQUEST_DETECTED. The run the first request created.originalRequestIdstringOptionalOn a
409 PAYOUT_OUTCOME_UNKNOWNreplay. TherequestIdof the call whose outcome is unknown; quote it to support.existingRecipientIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The recipient in your organization that already holds this account.existingMethodIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The payment method on that recipient.
Branch on type, never on the status or the message. Every error type is listed with what to do about it.
Was this page helpful?