24h Volume—Open Interest—24h Liquidations$1.36B24h Long/Short—BTC Dominance—ETH Dominance—
App
Language ▾
$ USD ▾
/api/hl/labels/:addr
GETAvailable

Hyperliquid address labels

Hyperliquid address labels (nickname, entity, tags)

GET/api/hl/labels/:addr

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
addr pathstringRequired——0x-prefixed 40-hex address; 400 on bad format (lowercase). Example: 0x5b5d51203a0f9079f8aeb098a6523a13f298c060

Parameters marked “path” are part of the URL.

Example request

curl -s "https://www.coinboss.com/api/hl/labels/0x5b5d51203a0f9079f8aeb098a6523a13f298c060"

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.
addressstring—On-chain address.
labelsarray—Labels.
labels[]object—Labels.
labels[].labelstring—Label.
labels[].typestring—Type.
labels[].sourcestring—Where the value comes from.
labels[].confidencenumber—Fixed score from 0 to 100 assigned by label source: 100 for leaderboard nicknames and algorithmic labels, 90 for entity aliases, 80 for community tags.
labels[].updatedAtstring—Date-time string.

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

Example response

/api/hl/labels/0x5b5d51203a0f9079f8aeb098a6523a13f298c060 · Real response captured 2026-11-13 03:58:36 UTC. Long arrays and maps are shortened for display: labels had 3 items.

  • {
    • "success": true,
    • "updated": 1794542316810,
    • "address": "0x5b5d51203a0f9079f8aeb098a6523a13f298c060",
    • "labels": [
      • { … 5 },
      • { … 5 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
60s
Edge micro-cache
10s
Update frequency
daily; API cache 60 s
Data sources
Labels for a Hyperliquid address: entity names from hypurrscan, display names from the official leaderboard, and behaviour tags computed in-house.
Exchange coverage
Addresses in the tracked pool plus hypurrscan's global alias list
Pagination
none
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

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

Availability, last 30 days

100% of 409 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/labels/:addrAvailable
Parameters

string — 0x-prefixed 40-hex address; 400 on bad format (lowercase).

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