Skip to main content
GET
/
v0
/
user
/
me
/
assets
Get User Assets
curl --request GET \
  --url https://api.sumvin.com/v0/user/me/assets \
  --header 'x-sumvin-pat: <api-key>'
{
  "_links": {},
  "total_assets": 123,
  "assets": [
    {
      "symbol": "<string>",
      "name": "<string>",
      "chain_id": 123,
      "total_balance": "<string>",
      "wallet_count": 123
    }
  ]
}

Authorizations

​
x-sumvin-pat
string
header
required

Personal access token issued to the Sumvin CLI. Send it in the x-sumvin-pat header to authenticate as the owning user.

Headers

​
x-sumvin-token
string | null
​
x-sumvin-pat
string | null
​
x-juno-jwt
string | null
​
x-juno-orgid
string | null

Tenant org ID for multi-tenant auth

​
X-Timestamp-Format
string

Controls how timestamp fields are serialized in JSON response bodies.

Default (header omitted or any other value): epoch milliseconds as integers. iso8601: UTC ISO 8601 strings of the form YYYY-MM-DDTHH:MM:SSZ.

Example: with X-Timestamp-Format: iso8601, the field value 1704067200000 becomes "2024-01-01T00:00:00Z".

Affected fields (recursively, in dicts and arrays): any field whose name ends in _at, plus the literal field names timestamp, period_start, and period_end. All other fields are passed through unchanged.

Only iso8601 is recognized. Any other value (or omitting the header) yields the default epoch-ms representation; the server does not reject unknown values, so this is documented as an example rather than an enum to keep generated clients permissive.

Example:

"iso8601"

Query Parameters

​
expand
string[]

Expand options: wallet to include per-wallet balance breakdown

Allowed value: "wallet"
​
chain_id
integer | null

Filter assets by blockchain chain ID

Response

User assets retrieved successfully

​
_links
Links · object
required

HAL-style hypermedia links for navigation and available actions.

​
total_assets
integer
required
​
assets
(UserAssetData · object | UserAssetDataExpanded · object)[]
required