Hyperliquid wallet Data API

The WalletFollow Data API serves authenticated, read-only Hyperliquid account, position, spot balance, performance and trade data. This public documentation describes endpoint availability, API-key authentication, request weights, limits and error handling. It does not provide anonymous access to account responses. Scripts, applications and AI research tools should use the documented data connection rather than scraping account pages.

Select the documented endpoint that answers your question and retain its observation times, account scope and coverage fields. The service uses prepared observations, so retrieving a response now does not establish that its underlying state was observed now. A missing value is not a zero balance, and an observed history is not a complete lifetime record.

API capacity is measured by request weight. Endpoint variants can have different costs, and monthly budgets, minute limits, burst limits and active-key allowances are separate controls. Read the current catalog and published plan tables before estimating a workload. Handle rate-limit responses according to their error code and retry instructions, and monitor usage instead of repeatedly issuing failed requests.

A data-service key grants supported data access within its limits, not permission to execute trades, transfer assets or withdraw funds. Store credentials outside source code, browser bundles and conversation text. Keep them out of URLs and logs. The API guide explains setup and read-only access, while the methodology describes timestamps, PnL definitions, valuation and coverage limitations.