curl --request GET \
--url https://api.hevn.finance/dapi/v1/client/balance \
--header 'Authorization: Bearer <token>' \
--header 'X-Hevn-Account: <x-hevn-account>'import requests
url = "https://api.hevn.finance/dapi/v1/client/balance"
headers = {
"X-Hevn-Account": "<x-hevn-account>",
"Authorization": "Bearer <token>"
}
response = requests.get(url, headers=headers)
print(response.text)const options = {
method: 'GET',
headers: {'X-Hevn-Account': '<x-hevn-account>', Authorization: 'Bearer <token>'}
};
fetch('https://api.hevn.finance/dapi/v1/client/balance', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"clientId": "cl_9f2c1ab84d7e4f1fa3c65b0e7d9a2c41",
"totalUsd": "500.00",
"baseSmartWallet": "<string>",
"tokens": [
{
"token": "USDC",
"balance": "500.00",
"usdValue": "500.00"
}
]
}{
"error": {
"code": "invalid_request",
"message": "<string>",
"details": {}
}
}Read a client's on-chain balance
The balance held by the Base smart wallet of the client selected by X-Hevn-Account, one row per settlement token.
curl --request GET \
--url https://api.hevn.finance/dapi/v1/client/balance \
--header 'Authorization: Bearer <token>' \
--header 'X-Hevn-Account: <x-hevn-account>'import requests
url = "https://api.hevn.finance/dapi/v1/client/balance"
headers = {
"X-Hevn-Account": "<x-hevn-account>",
"Authorization": "Bearer <token>"
}
response = requests.get(url, headers=headers)
print(response.text)const options = {
method: 'GET',
headers: {'X-Hevn-Account': '<x-hevn-account>', Authorization: 'Bearer <token>'}
};
fetch('https://api.hevn.finance/dapi/v1/client/balance', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"clientId": "cl_9f2c1ab84d7e4f1fa3c65b0e7d9a2c41",
"totalUsd": "500.00",
"baseSmartWallet": "<string>",
"tokens": [
{
"token": "USDC",
"balance": "500.00",
"usdValue": "500.00"
}
]
}{
"error": {
"code": "invalid_request",
"message": "<string>",
"details": {}
}
}Authorizations
Platform access token from POST /auth/token, carrying the platform audience and the developer_key_id of the registration that minted it. It acts as your own account; name a client you created with X-Hevn-Account: cl_…. Every request re-checks that the registration is still active and that the caller's source IP is inside its allowlist. A token is valid only against the server that issued it, so sandbox tokens are refused in production and production tokens in the sandbox.
Headers
The selected client account, as a cl_… id.
"cl_9f2c1ab84d7e4f1fa3c65b0e7d9a2c41"
Response
Successful Response
Account associated with this balance.
^(?:cl_)?[A-Za-z0-9._:\-]{1,216}$"cl_9f2c1ab84d7e4f1fa3c65b0e7d9a2c41"
Indicative total balance converted to USD.
"500.00"
Base smart-wallet address controlled by the account.
Balances grouped by supported digital asset.
Show child attributes
Show child attributes
Was this page helpful?