reseller
GET /v1/reseller/client-wallets/{walletId}/top-ups
The deposits on one client's balance.
Authentication
Send an API key as a bearer token. The key must carry the reseller.view permission; a key without it is refused with 403, not 404.
Where your organisation id goes
This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.
Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/reseller/client-wallets/{walletId}/top-ups \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
What a refund is chosen from. A wallet belonging to another reseller answers 404, never 403, so this is not an existence oracle. Requires `reseller.view`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
walletId (path) | Uuid | Yes | — |
org_id (query) | Uuid | No | Which of your organizations this applies to. Required only when you belong to more than one here — otherwise it is inferred, and an id outside your direct memberships is a 404 r… |
Errors this endpoint can return
401 · 403 · 404 · 429