Skip to main content
GET
List an account's assets and whether it can use them
Requires scope: manage:accounts — see Required scopes. The same assets as List supported assets, each annotated with a permitStatus telling you whether this account can move that asset yet. Check this before offering an asset to an end-user. An asset the tenant has enabled is not automatically usable by every account: the account’s wallet needs an allowance in place first, and on a self-custody wallet only the customer can grant it.
permitStatus is derived on every request and never stored. Don’t cache it — a status can change as soon as a customer signs or a wallet finishes activating.
Only READY means “spend now”. Treat everything else as unavailable, and use ACTION_REQUIRED as the trigger to send the customer through permits and allowances.

Authorizations

Headers

x-tenant-id
string<uuid>

Which tenant the request is scoped to, among those your token grants. Omit it when the token grants exactly one tenant; it is required when the token grants more than one. A supplied value must exactly match a tenant the token grants.

Absent when required, blank, malformed, or naming a tenant the token does not grant — each gets the same generic 403 forbidden, which reveals neither whether a tenant exists nor which ones you may use. Send the header once: a repeated header is rejected the same way.

Example:

"3fa85f64-5717-4562-b3fc-2c963f66afa6"

Path Parameters

accountId
string<uuid>
required

Unique account identifier

Response

The account's assets with derived usability

success
boolean

Indicates whether the request was successful

result
object[]