Skip to content
Loading 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`.

Response Body

application/json

application/json

curl -X GET "https://api.wajub.com/accounts/acc_Gt6yU3nE8rM1kS5vX9bQ"
GET
/accounts/{id}
{  "code": 200,  "status": "OK",  "message": "Account retrieved",  "account": {    "id": "acc_Gt6yU3nE8rM1kS5vX9bQ",    "reference": "shop-amina",    "sandbox": false,    "account_type": "direct",    "capabilities": [      "read",      "payments",      "refunds"    ],    "profile": {      "business_name": "Boutique Amina",      "email": "contact@shop-amina.example",      "country": "CM"    },    "metadata": {      "vendor_id": "4172"    },    "callback": "https://example.com/connected",    "status": "active",    "payment_status": "active",    "commission_refund_policy": "prorata",    "slave": {      "id": "9b2f4c1e-6a3d-4e8f-b7c5-2d1e0f9a8b76",      "name": "Boutique Amina",      "email": "contact@shop-amina.example"    },    "pricing": {      "percentage_fee": 2.5,      "fixed_fee": 0,      "min_fee": 0,      "max_fee": 0,      "currency": "XAF"    },    "expires_at": null,    "created_at": "2026-08-20T10:30:00+00:00",    "updated_at": "2026-09-01T07:45:12+00:00"  }}

OK

What did you think of this content?