List approvals
Payouts and batch runs waiting on your approvers.
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 approval status. Unknown values are a 400.
Allowed values:pendingapprovedrejectedexpiredShow 4 more values
executingexecutedexecution_failedexecution_unknownlimitintegerOptionalDefaults to50From 1 to 100. Defaults to 50. Outside the range is a
400, not clamped.
Behavior
When your organization requires M-of-N approval on API payouts, a
POST /payouts or a batch confirm above the threshold answers 202
with an approval id instead of a payout. This is that queue.
An approval is a resource of its own, not a payout status: the
payout does not exist until the approval executes, and then it begins
at pending like any other. An executed approval carries the
payoutId it became; so does the payout_approval.executed event.
Approving and rejecting are human actions, done in the dashboard by
an owner or admin on their own passkey:
POST .../payouts/approvals/{approvalId}/approve and
POST .../payouts/approvals/{approvalId}/reject. An API key is refused
on both, whatever role its member holds. The initiator cannot approve
their own request, a second vote from the same signer changes nothing,
one rejection is terminal, and a pending request expires after 24 hours.
There is no cursor: data holds at most limit approvals, newest
first, and older ones are not reachable from this list. Filter by
status to see the ones that matter.
Responses
200Approvals, newest first.
Body
dataarray of objectRequiredShow 14 properties
idstringRequiredkindstringRequiredAllowed values:payoutpayout_batchstatusstringRequiredThe lifecycle of an approval, a pre-payout resource.
executingandexecution_unknownare visible on the resource but emit no event.Allowed values:pendingapprovedrejectedexpiredShow 4 more values
executingexecutedexecution_failedexecution_unknownrequiredApprovalsintegerRequiredM, snapshotted when the request was created.
approvalsintegerRequiredApprove votes so far.
payoutIdstringOptionalPresent once a
payoutapproval isexecuted, naming the payout it became.batchIdstringOptionalPresent on
payout_batchapprovals.amountstring | nullRequiredSource-currency amount; for a batch, the run's estimated total.
currencystring | nullRequireddestinationAccountIdstringOptionalerrorobject | nullOptionalPresent on
execution_failedandexecution_unknown: why the approved payout could not be sent, or why its outcome is unknown.Show 2 properties
codestringOptionalThe error
typethe send answered with, when there was one (PAYOUT_OUTCOME_UNKNOWNonexecution_unknown).messagestringRequired
createdAtstring<date-time>RequiredexpiresAtstring<date-time> | nullRequiredA
pendingrequest expires 24 hours after creation.updatedAtstring<date-time>Required
Errors
400VALIDATION_ERROR:statusis not an approval status, orlimitis out of range.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?