Skip to main content
Every error is:
400 UNKNOWN_PARAM names the parameter we do not know (Unknown query parameter "blockchain"), so a leftover parameter from another provider is caught on the first call; 400 INVALID_PARAM is a known parameter with a bad value. 503 responses carry a Retry-After header (seconds): retry after that delay, the request is not billed. In a batch, which answers 200, a failed item comes back as an { error } slot carrying one of these codes, and that item is not billed either. 402 PAYMENT_REQUIRED (a billing step is needed on the account) and 402 QUOTA_EXCEEDED (the account reached its allowance for now) are covered, with 403 FORBIDDEN on a suspended account, in Authentication & Limits: for keys created in the portal they carry details.action, the machine-readable next step. 429 RATE_LIMITED (per-key rate) is covered on the same page. 4xx requests and rejected calls are never billed. A 429 RATE_LIMITED whose details.limit is watchlistWallets or watchlists is a watchlist limit, not a rate: nothing was written, and waiting does not help. Remove wallets or delete a watchlist first. When creating a watchlist or adding wallets, an entry that would put an address both on every EVM chain (chains: "evm") and on a named EVM chain comes back in rejected with INVALID_PARAM; the other wallets are applied. A watchlist that does not exist (on its own routes, or in the watchlist filter of token holders) answers 404 NOT_FOUND with details.reason: unknown, or purged (unused for 48 hours, with details.purgedAt: create it again). On the stream, a watchlist subscription gets the same NOT_FOUND when its watchlist is deleted or purged, and ends (details.purgedAt can be missing there). On price webhooks, a 429 RATE_LIMITED whose details.limit is priceTriggers (active triggers across your webhooks) or priceWebhooks (webhooks) is a limit too: nothing was written; remove triggers or delete a webhook first. priceWebhookTest is the pace of test pings (one per webhook every 5 seconds) and priceWebhookTestInFlight too many test pings in progress at once: retry after Retry-After. A 503 OVERLOADED on creating a webhook or adding triggers means price webhooks cannot take new triggers for a moment: nothing was written, retry after Retry-After. A webhook that does not exist, or was deleted, answers 404 NOT_FOUND with details.reason: "unknown". A trigger that cannot be armed comes back in rejected with its index and the error (for example INVALID_PARAM with details.reason noPrice, idTaken, nativeCoin, wrappedNative or stablecoin, NOT_FOUND for an unknown token, or UPSTREAM_ERROR with details.reason: "usdRateUnavailable", a USD eq to send again after details.retryAfterSec); the others are armed. The watchlist filter of the top traders and trades endpoints answers the same 404, and 400 INVALID_PARAM with details.param: "watchlist" when it is sent with makers or maker. 415 UNSUPPORTED_MEDIA_TYPE: a POST body was not sent as application/json. 413 PAYLOAD_TOO_LARGE: the body is larger than the endpoint accepts; split the batch. 404 NO_PRICE_AT: on Token Price at a date, the token is known but had no trade at or before the timestamp asked on its main market (it was created later, or the date precedes its first trade); details.timestamp repeats the instant. A 404 NOT_FOUND there means the token itself is unknown. In a batch, the item comes back as an { error } slot with the same code, not billed. 422 TOO_MUCH_DATA: the request is valid but asks for more than one call computes. details names the limit (what, count, limit): on wallet equity history, a wallet that touched more than 10,000 tokens over the window; ask for a shorter window. Retrying the same request does not help, and it is not billed. On the WebSocket stream, errors arrive as {"op":"error","id":"<subscription id>","error":{…}} with the same codes. Three of them are notices that never end a subscription: REPLAY_TOO_OLD (some events may be missing: fetch them over REST from details.restFromMs), UPSTREAM_ERROR with details.resumes: true (live data briefly unavailable: nothing to do) and OVERLOADED on a subscribe (retry after details.retryAfterMs). On a watchlist subscription, RATE_LIMITED with details.refused is a notice too (that many wallets of the list cannot be followed for now), and on wallet-positions and wallet-portfolio so is any error with details.wallet (it concerns that wallet only) and an UPSTREAM_ERROR with details.wallets (that many wallets, back by themselves). On those two channels, a subscribe refused with RATE_LIMITED and details.limit: "watchlistWalletsPerMinute" is a rate: this connection subscribed to watchlists too fast, send the same subscribe again after details.retryAfterMs. See the Streams overview.