reseller

POST /v1/reseller/client-wallets

Open a client's float, or add credit to it.

All reseller endpoints

Authentication

Send an API key as a bearer token. The key must carry the reseller.manage 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 POST https://api.zinndigital.com/v1/reseller/client-wallets \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "client_org_id": <Uuid>, "currency": <string>, "amount_minor": <integer>, "reason": <string> }'

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

Records a deposit you took **outside** our gateway — a bank transfer, cash, an invoice settled directly — or a goodwill credit, or a balance migrated in from whatever you used before. It lands as an adjustment on the client's ledger with your reason on the line they read. Requires `reseller.manage`. ⛔ This is the only way to bring a client's float into existence. Every other write on this surface needs a `wallet_id`, and until this endpoint a wallet only appeared once the client had paid by card — so a reseller could see an empty liability register with no control on it, which is what was measured on production on 2026-08-16 (`ClientWallet` held zero rows estate-wide). ⛔ It is deliberately **not** a card charge. `POST /v1/wallet/top-ups` is that, it is the client's own action, and it settles into your gateway. Money that never moved through a gateway must not be recorded as though it had. A client that does not bill back to you is a **404**, never a 403 — this endpoint must not become a way to discover who else resells to whom.

Parameters

NameTypeRequiredWhat it is
org_id (query)UuidNoWhich of your organizations this applies to. Required only when you belong to more than one here — otherwise it is inferred.

Request body

NameTypeRequiredWhat it is
client_org_idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
currencystringYes
amount_minorintegerYesStrictly positive. Opening a float is a DEPOSIT; taking money off a client is a correction and belongs on the adjustments endpoint, which has the below-zero guard and an existin…
reasonstringYesThe client reads this on their own statement of account.

Response

NameTypeRequiredWhat it is
org_idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
currencystringYes
balance_minorintegerYesWhat you are **owed** — the float your provider is holding for you.
spendable_minorintegerYesWhat you can **spend today**. Lower than `balance_minor` when your provider's reseller programme is suspended: the deposit is still yours, but nobody is delivering service again…
reseller_org_idUuid | nullNoThe provider whose float this is.
entriesClientWalletEntry[]Yes
other_floatsClientOtherFloat[]YesBalances a **previous** provider still holds for you. ⛔ Normally empty. A client who changed provider is still owed what the old one took; omitting it would make that money disa…
providerstring<reseller, zinn>No⭐ **Who is holding this money.** One screen serves both, because *"credit you hold with your provider"* is one question whose answer depends on the customer, not on the feature.…
pursesWalletPurse[]NoThe owner's *"one ledger, named purses"* — a balance may be restricted to a kind of spending. ⛔ Empty for a reseller float, which has no purses. A purse whose authoritative stor…

Errors this endpoint can return

401 · 403 · 404 · 422 · 429