Field names
Field names and query parameters are camelCase:marketCap, priceChangePct, countBack.
Enumerated values are case-sensitive strings, such as "side": "buy", "flags": ["pro_trader"] and "metric": "marketCap". Send and compare them exactly as documented.
Timestamps
Every timestamp is an integer count of milliseconds since the Unix epoch, in requests and responses alike.- Fields that hold a point in time end in
At:createdAt,graduatedAt,updatedAt. - Some records use a plain name instead, such as a trade’s
timestampand a candle’stime.
Money
Every price, market cap, liquidity, volume and fee total is returned in two units:
The API has no standalone
priceUsd field.
Decimals
Prices, amounts, supplies and percentages are returned as strings containing exact decimals:"0.0000216", "1000000000".
JSON numbers are floating point and lose precision on small prices and large token amounts, so parse these strings with a decimal type:
holders.count and buyCount, are plain JSON integers.
Candle values
Candle values (open, high, low, close, volume) are JSON numbers, because charting libraries consume them as floats. Candles are the only place where the API returns money as a number.
Percentages
A field ending inPct holds a signed percentage on a 0–100 scale, as a decimal string.
"-2.5" means a decrease of 2.5%, not a factor of -0.025.
Transfer fees are the only exception: transferFeeBps is an integer in basis points, so 250 means 2.50%.
Trailing windows
A token’sstats object holds one entry per trailing window, keyed 5m, 30m, 1h, 6h and 24h. Each window ends at the current time rather than aligning to a calendar bucket.
Missing values
- Most values that are not yet known are
null. For example,graduatedAtisnulluntil a token leaves its launchpad. - A few fields use an empty value instead. For example, a trade’s
nameandsymbolare empty strings until the token’s metadata is available. - Empty lists may be omitted:
platformsandannotationson a token, andflags,platformsandidentitieson a trade. Treat a missing list as empty.