Skip to main content
POST
POST /v1/token · 2 credits per 25 items (windows included; 2 more per call with include=security) Full-detail batch twin: up to 25 {chain, address} items (EVM and Solana can be mixed in one call), response array in input order with per-item {error} slots. Billed 2 credits per 25 items served: 1 to 25 tokens cost 2 credits.
Mixed families in one batch; a missing token returns a per-item error slot, never a failed batch.
Each item’s payload is identical to GET /v1/token, stats24h included. windows (optional, shared by the whole call, same values as the GET, 1m, 5m, 15m, 30m, 1h, 4h, 6h, 12h, 24h, as a comma-separated string or a list) ends each token served with its windows block, exactly as the GET returns it; an unknown window is a 400 on the call. The windows are included in the price of the call: 25 tokens cost 2 credits with or without them.
include (optional, shared by the whole call, a comma-separated string or a list, like windows) takes security: each token served then carries its tokenSecurity block right after risk, exactly as GET /v1/token returns it with include=security (the liquidity safety of the token’s main market, the shares of its 100 and 200 largest holders and every contract flag, with the names and values of /v1/token/security). An item in error carries no block, and an unknown value of include is a 400 on the call. The option costs 2 more credits for the call, whatever the number of tokens, when at least one block is served: 25 tokens with include=security cost 4 credits. Nothing more is billed when every block is null.
The security sheets of one chain are read together: when one is not available, tokenSecurity is null for every token of that chain in this response, and the tokens of the other chains keep their block. A batch with include=security counts one per item in the Security rate group, the one of /v1/token/security and /v1/pool/security (100 per minute per key by default, raised on request): a batch of 25 takes 25 of it, and a batch that does not fit answers 429 with details.group security before anything is read. The same batch without include still passes.

Authorizations

Authorization
string
header
required

Your raw API key (not needed on the demo server).

Body

application/json
items
object[]
required

1 to 25 of {chain, address}. Each item takes address or its other name, tokenAddress.

Required array length: 1 - 25 elements
Example:
windows

Same as the GET, applied to every item: windows among 1m, 5m, 15m, 30m, 1h, 4h, 6h, 12h, 24h, as a comma-separated string or a list. Each token served then ends with its windows block. Absent unless you ask; an empty value adds nothing. The windows are included in the price of the call.

include

Same as the GET, applied to every item: security (a comma-separated string or a list) adds a tokenSecurity object right after risk to each token served. 2 more credits for the call, whatever the number of tokens, when at least one block is served: 25 tokens cost 4 credits. Absent unless you ask; an empty value adds nothing; an unknown value is a 400.

Example:

"security"

Response

200

Standard { data, meta } envelope.