Skip to main content
GET
/
openapi
/
v1
/
crypto
/
bubble-map
Crypto bubble map
curl --request GET \
  --url https://api.hayinsights.com/openapi/v1/crypto/bubble-map \
  --header 'X-API-Key: <api-key>'
{
  "success": true,
  "statusCode": 200,
  "data": {
    "timeframe": "1d",
    "coins": [
      {
        "symbol": "BTC",
        "name": "Bitcoin",
        "marketCap": 1254560380643.96,
        "change": -2.9057,
        "size": 1
      },
      {
        "symbol": "ETH",
        "name": "Ethereum",
        "marketCap": 204246767811.64,
        "change": -3.2733,
        "size": 0.4035
      },
      {
        "symbol": "USDT",
        "name": "Tether USDt",
        "marketCap": 186279683262.83,
        "change": -0.0033,
        "size": 0.3853
      }
    ]
  },
  "meta": {
    "timestamp": "2026-06-19T08:50:00.981Z"
  }
}

Authorizations

X-API-Key
string
header
required

Your HayInsights API key (prefixed apk_). Create and manage keys in the HayInsights dashboard (Account → API keys).

Send it in the X-API-Key header on every request to /openapi/v1/*. Which data domains you may access and your request quota are both governed by the subscription plan attached to the key — see the Plans & features and Rate limits guides.

Query Parameters

timeframe
enum<string>
default:1d

Timeframe the price changes are computed over.

ValueDescription
1hLast 1 hour
1dLast 1 day
1wLast 1 week
Available options:
1h,
1d,
1w
limit
integer
default:100

Maximum number of coins to return.

Required range: 1 <= x <= 200

Response

Bubble-map dataset for the requested timeframe.

Standard success envelope shared by every endpoint. Each operation's response wrapper extends this (via allOf) and adds a typed data property.

success
boolean
required

Always true for a successful response.

Example:

true

statusCode
integer
required

Mirrors the HTTP status code.

Example:

200

data
object
required

Bubble-map dataset — the top coins by market cap with their price change over a selected timeframe and a normalised bubble size for visualisation.

meta
object

Response metadata. Always present; timestamp is the server time the response was generated.