Address balances endpoint

`GET /v1/addresses/{publicKey}/balances`

Auth: workspace token. Scope: read.

Not available in this release

This route returns a stable 501 with code not_implemented. wative-core 2.4.4 implements no balance-refresh path, and a capability guard answers before the handler can run.

{
  "error": {
    "code": "not_implemented",
    "message": "Balance lookup is not available in this release.",
    "status": 501,
    "requestId": "…"
  }
}

Getting balances today

Read balances from your own RPC endpoint, using the addresses returned by GET /v1/accounts/{slug}/wallets. Each address carries the network and chainId you need to pick the right endpoint.

Errors

The 501 is the route’s answer, but it is not the first one. Authentication and scope are checked before the capability is, so a client still needs to handle both:

Status	Code	When
401	`session_expired`	Missing, invalid, or expired token — checked first
403	`scope_denied`	The token lacks `read`
501	`not_implemented`	Everything else, always

No 404 is possible: the handler never runs, so an address that does not exist returns the same 501 as one that does.

Accounts endpoints — where addresses come from
Networks and RPC — your own endpoints