API ReferenceMarket Data
Crypto breaking headlines
/api/v3/crypto/events/headlines- Plan
- Free and up
- Price
- 1 credit per call
- MCP tool
crypto_events_ headlines
Call this for what is BREAKING on crypto-native social and blogs right now, already mapped to coins. Sourced from the accounts that break events — exchange officials, security firms, tier-1 desks — with the post's own timestamp, so it runs minutes to hours ahead of any article. Every item is classified (exploit / halt / depeg / regulatory / listing / delisting / etf / unlock / liquidation) and tagged tier 1 or 2 by whether the account is a known breaking source; tier1_only=true keeps just those. A post matching no class is a plain 'headline', and a coin is tagged only when the post names it (a cashtag, a ticker or the coin's name). Retweets and replies are dropped and an account's re-posts of one post fold into the first (n_reposts) — an event is the original post, not the 400 accounts quoting it. lag_ms is how late FIRM first read the post, age_ms its age. The classification is an event TYPE, never a direction: read the price for that. DATA context, not a score. Auth: X-API-Key.
Parameters
Query
limitintegerOptional501 to 200event_typestringOptionalexploithaltdepegregulatorylistingdelistingetfunlockliquidationheadlinesymbolsstringOptionalComma list of BASE assets.
tier1_onlybooleanOptionalOnly accounts that BREAK events.
falseasset_classstringOptionalThis route is crypto-native. asset_class=crypto is accepted.
cryptocryptoResponse
A 200 is a JSON envelope: ok: true and this endpoint's own fields (see Crypto). It carries X-Request-ID, the credit headers (X-Credits-Cost, X-Credits-Remaining, X-Credits-Receipt, X-Credits-Settlement) and the rate-limit headers.
A 200 is billed even when it holds no data (an empty list, null, found: false), so check those fields. Pricing & credits explains the credit headers.
Errors
No error is billed. The body is { "ok": false, "error", "detail", "request_; read the code from error.
| Error | Meaning |
|---|---|
400 invalid_ticker | The request is malformed, for example a ticker that is not a symbol: invalid_ticker, refused before any credit is reserved, with param naming the parameter. Not billed. |
401 unauthorized | Missing or invalid API key. |
402 plan_required | Your plan does not include this tool, you are out of credits, or your workspace's spend cap paused its keys. plan_required names the plan that unlocks the tool; usage_exceeded means the credit balance is spent; spend_cap_reached means the key is paused until the cap resets or is raised: detail names the cap and the reset, cap_usd and resets_at (ISO 8601) carry them, and doc_url links pricing and credits. Not billed. |
403 scope_denied | This API key is limited to some products and this tool is not one of them. product names the tool's product and scopes the key's products. An upgrade does not change it: use a key whose scopes include the product, or change this key's scopes. Not billed. |
404 not_found | No such resource. Not billed. |
422 validation | A parameter is missing, out of range or the wrong type; param names it. Not billed. |
429 rate_limited | Your plan's rate limit is spent for this window. Retry after Retry-After seconds. Not billed. |
503 paid_ | The data could not be served completely right now; retry later. Not billed. |
504 request_timeout | The request ran past the server's time budget; retry. Not billed. |
This table lists what the spec declares for this route. Error responses lists every code FIRM sends, with when to retry.
Guides
Read the Crypto guide for this endpoint's fields and examples.