Aller au contenu
Chargement des API keys…
Authorization<token>

A public key (pk./pk_test.) is accepted on /payments, /customers, /links, /invoices and the catalogue reads (/channels, /providers, /countries, /currencies); anything that moves money out, reads the balance or manages the account answers 406 to it. It is an identifier, never an authorization. Use a secret key (sk./sk_test.) for sensitive operations (transfers, refunds, balance), or a restricted key (rk./rk_test.) scoped to specific permissions. The _test. variant of any key selects the sandbox environment, there is no separate sandbox URL. Never expose your secret key in client-side code.

In: header

Path Parameters

idstringrequired

The subaccount `id`.

Query Parameters

date_fromstring | null

Payouts created on or after this day, `YYYY-MM-DD`.

date_tostring | null

Payouts created on or before this day, `YYYY-MM-DD`.

statusstring | null

One status or several, comma-separated: `pending`, `processing`, `succeeded`, `failed`, `cancelled`.

per_pageinteger | null

Max results per page (1–100). Defaults to 25.

cursorstring | null

The `next_cursor` of a previous response, a numbered page included: switches the list to cursor pagination.

Response Body

application/json

application/json

curl -X GET "https://api.wajub.com/accounts/acc_Gt6yU3nE8rM1kS5vX9bQ/payouts?date_from=2026-11-01&date_to=2026-11-30&status=succeeded&per_page=25"
GET
/accounts/{id}/payouts
{  "code": 200,  "status": "OK",  "message": "Payouts retrieved",  "items": [    {      "id": "po_Lw4Hq8Tz2Nc6Vb1Xk9Rm",      "object": "payout",      "account": "acc_Gt6yU3nE8rM1kS5vX9bQ",      "amount": 18620,      "currency": "XAF",      "status": "succeeded",      "failure_reason": null,      "created_at": "2026-11-19T08:00:04+00:00",      "succeeded_at": "2026-11-19T08:00:09+00:00"    }  ],  "meta": {    "current_page": 1,    "last_page": 1,    "per_page": 25,    "total": 1,    "next_cursor": null,    "has_more": false  }}

OK

Que pensez-vous de ce contenu ?