Addresses within a Hyperliquid tier
Addresses within a Hyperliquid tier (paginated)
/api/hl/tier/:slug/addressesRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| slug path | string | Required | — | stardust, meteor, asteroid, comet, planet, star, supernova, galaxy | Tier slug; 404 if unknown. Example: galaxy |
| page | integer | Optional | 1 | ≥ 1 | Page number (1-based). Example: 1 |
| size | integer | Optional | 20 | ≥ 10 · ≤ 100 | Page size. Example: 20 |
Parameters marked “path” are part of the URL.
Example request
curl -s "https://www.coinboss.com/api/hl/tier/galaxy/addresses?page=1&size=20"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.
| Field | Type | Unit | Description |
|---|---|---|---|
| success | boolean | — | true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`. |
| updated | number | ms | When the data was last updated. |
| total | number | — | Total. |
| page | number | — | Current page (1-based). |
| size | number | — | Page size. |
| rows | array | — | Result rows. empty in the samples used to generate this table |
Generated 2026-11-11 23:00 UTC from 1 real responses.
Example response
/api/hl/tier/galaxy/addresses?page=1&size=20 · Real response captured 2026-11-13 04:03:07 UTC.
- "success"true
- "updated"0
- "total"0
- "page"1
- "size"20
- "rows"
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 2m
- Edge micro-cache
- 10s
- Update frequency
- hourly scan, ingested within 30 s; addresses not seen for 48 h are removed; API cache 120 s
- Window
- latest scan per address
- Data sources
- Per-address account value, margin and exposure for one account-size tier, from hourly full scans run on our own Hyperliquid node.
- Exchange coverage
- Addresses covered by the hourly scan (about 59,600 at probe time), grouped into tiers
- Pagination
- page + size (10-100, default 20); total returned
- Sorting
- pos_value desc, then account_value desc
- Units
- USD
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
The per-address table behind this endpoint is currently empty, so `rows` is `[]` and `total` is 0 even for tiers that have wallets.
Availability, last 30 days
100% of 410 checks passed
Errors
Failed calls share one shape on every endpoint. The full list is on the errors page. Errors and rate limits →
| Code | HTTP | Meaning | What to do |
|---|---|---|---|
| INVALID_PARAM | 400 | A 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. |
| UNAUTHORIZED | 401 | The `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. |
| FORBIDDEN | 403 | The route is not part of the public API (internal or account-only). | Do not retry. |
| NOT_FOUND | 404 | Unknown route, or the requested coin / exchange / fund does not exist. | Do not retry; check the path and identifiers against the catalog. |
| RATE_LIMITED | 429 | More requests than the per-minute limit. `Retry-After` gives the seconds to wait. | Wait for `Retry-After`, then retry with backoff. |
| INTERNAL | 500 | Unexpected 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_FAILED | 503 | The 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. |
| UNAVAILABLE | 501 / 503 | The 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_FAILED | 200 | Some 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
/api/hl/tier/:slug/addressesPartialstring — Tier slug; 404 if unknown.
integer · default 1 · min 1 — Page number (1-based).
integer · default 20 · min 10 · max 100 — Page size.
https://www.coinboss.com/api/hl/tier/galaxy/addresses?page=1&size=20More in this category
- Hyperliquid account state for an address /api/hl/address/:addr
- Hyperliquid per-coin whale positions page data /api/hl/coin
- HYPE burn overview /api/hl/hype-burn
- HYPE burn statistics /api/hl/hype-burn-stats
- HYPE burn / buyback transactions /api/hl/hype-burn-txs
- Hyperliquid address labels /api/hl/labels/:addr
- Hyperliquid position-size distribution /api/hl/margin-distribution
- Hyperliquid perp market list /api/hl/markets
- Hyperliquid wallet PnL distribution /api/hl/pnl-distribution
- Hyperliquid position summary /api/hl/position-summary
- Hyperliquid smart-money leaderboard /api/hl/smart-money
- Hyperliquid tier × coin heatmap /api/hl/symbol-heatmap
- Hyperliquid tier detail /api/hl/tier/:slug
- Addresses within a Hyperliquid tier /api/hl/tier/:slug/addresses
- Hyperliquid vault fills /api/hl/vault-fills
- Hyperliquid vault deposit / withdrawal flows /api/hl/vault-flows
- Hyperliquid vault profile /api/hl/vault-profile/:addr
- Hyperliquid vault detail /api/hl/vault/:addr
- Hyperliquid vault list /api/hl/vaults
- Hyperliquid vault overview table /api/hl/vaults/overview
- Hyperliquid whale open / close activity /api/hl/whale-actions
- Hyperliquid single-whale detail /api/hl/whale/:addr
- Hyperliquid whale position list /api/hl/whales
- Hyperliquid whale long/short split /api/hl/whales/long-short
- Hyperliquid whale-pool statistics /api/hl/whales/stats