A Wallet is the BlooBank platform’s unit of balance and the isolation boundary for every payment order, ledger entry, and webhook event. This page documents the resource model; for the operational mental model, see Wallet overview.Documentation Index
Fetch the complete documentation index at: https://developers.bloobank.com/llms.txt
Use this file to discover all available pages before exploring further.
Resource
| Field | Type | Notes |
|---|---|---|
id | string | Server-assigned, immutable (wal_…). Use as database key. |
kind | string | Always Tenant.Wallet. |
walVersion | integer | Snapshot version. Increments on each mutation. |
status | enum | ACTIVE or DISABLED. See Wallet lifecycle. |
name | string | RFC 1035 DNS label. 1–63 lowercase chars. Globally unique. Immutable. |
selfName | string | wallets/<name> — portable, base-URL-free reference. |
createdAt / updatedAt | string | UTC ISO 8601 with millisecond precision. |
etag | string (hex) | Content fingerprint. Reserved for optimistic concurrency. |
Endpoints
| Operation | Method | Path | Idempotent? |
|---|---|---|---|
| List wallets | GET | /wallets | ✅ |
| Create wallet | POST | /wallets | ❌ (uniqueness via name) |
| Get wallet | GET | /wallets/{wallet} | ✅ |
| Update wallet | PUT | /wallets/{wallet} | ✅ |
| Get balance | GET | /wallets/{wallet}/balance | ✅ |
Path parameter — {wallet}
All sub-resource endpoints accept the wallet in the path as either its id (wal_…) or its name (production-main). Both resolve to the same wallet.
Related concepts
Wallet overview
Mental model, balance breakdown, use cases.
Wallet lifecycle
State machine — ACTIVE, DISABLED, transitions.
Resources & naming
id, selfName, etag, walVersion across all resources.
Amounts & currency
How balance is represented.