Holdings

Liquid balances a wallet holds directly, outside any protocol position.

API overview

GEThttps://api.syncrone.fi/api/holdings

Retrieve token holdings data across organizations, wallets and chains. Holdings represent direct token balances held by wallets, excluding DeFi protocol positions.

Supports filtering by wallet, chain, time range, and asset address.

Request#

Send the API key in the x-api-Key header. List endpoints cap limit at 500. When page_info.has_more is true, pass page_info.next_cursor back as next_cursor.

Example
curl "https://api.syncrone.fi/api/holdings?limit=100" \
  -H "x-api-Key: $SYNCRONE_API_KEY"

Parameters#

NameTypeDescription
chain_idinteger

Blockchain network ID (e.g., 1 for Ethereum mainnet, 137 for Polygon)

chainstring

Blockchain network name (alternative to chain_id)

walletstring

Wallet address to filter by

^0x[a-fA-F0-9]{40}$
from_datedate-time

Start date for time range filter (ISO 8601 format)

to_datedate-time

End date for time range filter (ISO 8601 format)

from_blockstring

Start block number for filtering

to_blockstring

End block number for filtering

via_proxystring

Proxy contract address if interaction was through a proxy

^0x[a-fA-F0-9]{40}$
snapshot_modestringall | daily_only | interaction_only | harmonized_only

Filter by snapshot capture mode:

  • all: All snapshot types
  • daily_only: Daily scheduled snapshots
  • interaction_only: Event-driven snapshots on wallet interactions
  • harmonized_only: Regularly scheduled harmonized snapshots
default all
next_cursordate-time

Pagination cursor from previous response

limitinteger

Maximum number of results to return (capped at 500)

1–500, default 500
holding_idstring

Unique identifier for a specific holding

asset_addressstring

Token contract address

^0x[a-fA-F0-9]{40}$
validatestringtrue | 1

Enable data quality validation (returns only WARNINGS)

Response#

200 returns HoldingsResponse. Field definitions for nested objects live on the models page.

FieldTypeDescription
holdingsHolding[]
page_infoPageInfo

Errors#

StatusMeaning
400Bad Request - Invalid parameters
404Not Found - No data found matching the criteria
500Internal Server Error

Error bodies use the Error object: error, message, and statusCode.