/api/v1/openapi/payout_requestsCreates a payout and auto-approve it.
Example: good
Example: {{credential}}
Example: {{$string.uuid}}
Example: zh-CN
Example: application/json
Payout request
Payout amount (decimal as string or number in JSON; string recommended to avoid precision issues). Rules: Must be > 0, otherwise 820004 Decimal places must match currency standard, otherwise 820010 Subject to transfer_method+currency limits: below min → 820005; above max → 820006
Example: 100.50
Remark (optional). Empty string is treated as omitted. Max 120 runes Charset: Unicode letters/numbers + / -?:().,'+ (CJK allowed) Failure → 820008 Invalid remark
Example: Invoice payment
Payout currency. Must be active and match the payee payout_account currency. Invalid currency → 820003; mismatch with payee → 820001
Example: HKD
Payee ID. Must belong to the current business and have a payout_account matching currency. Failure → 820001 Invalid payee
Example: 7c9e6679-7425-40de-944b-e07fc1f90ae7
Scheduled payout time (optional, RFC3339 absolute time with offset or Z). UTC (...Z) is recommended. Stored as UTC. Omit: not scheduled If provided: must not exceed global scheduled_payout_max_days Failure → 820002 Invalid schedule time
Example: 2026-07-25T02:00:00Z
Client idempotency / reconciliation reference. Maps to ISO 20022 EndToEndId; stored as ref_id. Required. Rules: Length 1–35 (runes) Charset: a-zA-Z0-9 / -?:().,'+ (space allowed) Must not start/end with /; must not contain // Unique within the same business Failure → 820009 Invalid reference ID Lock contention / busy → 500104 System service busy
Example: INV-2026-0001
Created successfully (auto-approved)
Always 200 on success
200
Example: 200
Always succeed on success
succeed
Example: succeed
Response data
Payout request