/api/hl/vaults
GETAvailable

Hyperliquid vault list

Hyperliquid vault list

GET/api/hl/vaults

Request

This endpoint takes no parameters.

Example request

curl -s "https://www.coinboss.com/api/hl/vaults"

Response fields

The field table is generated from real responses, so it lists exactly what the endpoint returns. Paths use a[] for array items and {*} for objects keyed by a dynamic name such as a coin or an exchange.

FieldTypeUnitDescription
successboolean—true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`.
updatednumbermsWhen the data was last updated.
countnumber—Number of items.
rowsarray—Result rows.
rows[]object—Result rows.
rows[].namestring—Name.
rows[].vaultAddressstring—Address of the vault.
rows[].leaderstring—Vault leader address.
rows[].tvlnumberUSDTotal value locked in the vault.
rows[].aprnumber—Annualised return of the vault.
rows[].createTimeMillisnumbermsTime the vault was created.
rows[].isChildboolean—True for a child vault of another vault; always false here because child vaults are left out of this list.

Generated 2026-11-11 23:00 UTC from 1 real responses.

Example response

/api/hl/vaults · Real response captured 2026-11-13 03:53:10 UTC. Long arrays and maps are shortened for display: rows had 200 items.

  • {
    • "success": true,
    • "updated": 1794541991988,
    • "count": 2901,
    • "rows": [
      • { … 7 },
      • { … 7 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
2m
Edge micro-cache
10s
Update frequency
fetched on request, cached 300 s in memory and on disk; API cache 120 s
Data sources
Hyperliquid vault directory (TVL, APR, leader) from Hyperliquid's official stats-data feed.
Exchange coverage
Top 200 open vaults by TVL (closed, child and zero-TVL vaults excluded)
Pagination
fixed top 200
Sorting
TVL desc
Units
USD; APR as reported upstream
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:53:10 UTCHTTP 2001910 msSchema matchesNewest data point 0s old

Availability, last 30 days

100% of 408 checks passed

Errors

Failed calls share one shape on every endpoint. The full list is on the errors page. Errors and rate limits →

CodeHTTPMeaningWhat to do
INVALID_PARAM400A required parameter is missing or a value is not accepted. `param` names the parameter when it is known.Do not retry unchanged; fix the request.
UNAUTHORIZED401The `CB-API-KEY` header was sent but the key is unknown or revoked. Public data needs no key — drop the header or use a valid key.Do not retry unchanged.
FORBIDDEN403The route is not part of the public API (internal or account-only).Do not retry.
NOT_FOUND404Unknown route, or the requested coin / exchange / fund does not exist.Do not retry; check the path and identifiers against the catalog.
RATE_LIMITED429More requests than the per-minute limit. `Retry-After` gives the seconds to wait.Wait for `Retry-After`, then retry with backoff.
INTERNAL500Unexpected server error. The message is generic by design; quote `request_id` when reporting it.Retry once after a few seconds; report it with the request id if it persists.
UPSTREAM_FAILED503The data source behind this endpoint did not answer in time. No stale or substitute numbers are returned in its place.Retry with backoff; check the status page.
UNAVAILABLE501 / 503The dataset is temporarily not ready (cache warming) or the endpoint has no lawful public source yet.Retry later; the catalog marks endpoints that are unavailable by design.
REQUEST_FAILED200Some older endpoints answer HTTP 200 with `success: false`. Always check `success`, not only the HTTP status.Depends on the message; treat as a failed request.

Try it

GET/api/hl/vaultsAvailable
Parameters

No parameters.

Request URLhttps://www.coinboss.com/api/hl/vaults
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.