Trending
Trending endpoints answer one question: what is getting attention right now? They return counts and token or contract identifiers, not post text and not sentiment.
| Endpoint | Returns |
|---|---|
GET /v2/aggregations/trending-tokens | Tokens ranked by mention count. Experimental. |
GET /v2/aggregations/trending-cas/twitter | Contract addresses mentioned on Twitter/X, with mention counts. |
GET /v2/aggregations/trending-cas/telegram | Contract addresses mentioned on Telegram, with mention counts. |
Trending Tokens
GET /v2/aggregations/trending-tokens returns tokens with the most mentions over a time period, filtered by a minimum mention threshold.
This endpoint is under active development and its behavior may change without notice. Use it with caution in production.
Sample response (from the spec example):
{
"success": true,
"data": {
"pageSize": 1,
"page": 1,
"total": 1,
"data": [
{ "change_percent": 1, "previous_count": 1, "current_count": 1, "token": "string" }
]
}
}
Request:
curl "https://api.elfa.ai/v2/aggregations/trending-tokens?timeWindow=24h&page=1&pageSize=1&minMentions=5" \
-H "x-elfa-api-key: $ELFA_API_KEY"
| Field | Type | Meaning |
|---|---|---|
data.page | number | Current page. |
data.pageSize | number | Items per page. |
data.total | number | Total matching tokens. |
data.data[].token | string | The token. |
data.data[].current_count | number | Mentions in the window. |
data.data[].previous_count | number | Not described in the spec. |
data.data[].change_percent | number | Not described in the spec. |
| Parameter | Required | Type | Meaning |
|---|---|---|---|
timeWindow | No | string | Window ending now, e.g. 30m, 1h, 4h, 24h, 7d, 30d. Default 7d. |
from | No | number | Start of the window, unix timestamp. Use with to. |
to | No | number | End of the window, unix timestamp. Use with from. |
page | No | number | Page number. Default 1. |
pageSize | No | number | Items per page. Default 50. |
minMentions | No | number | Minimum mentions for an item to be included. Default 5. |
timeWindow or from and to
Provide either timeWindow or both from and to. If you send both, from and to take priority and timeWindow is ignored.
Uses
- Start each run from live attention instead of a hardcoded ticker list.
- Compare a short window against a longer one to separate tokens heating up from tokens that already peaked.
- Use
minMentionsas a significance floor.
Also via x402: GET /x402/v2/aggregations/trending-tokens
Trending Contract Addresses on Twitter
GET /v2/aggregations/trending-cas/twitter returns contract addresses mentioned on Twitter/X, with mention counts.
Sample response (from the spec example):
{
"success": true,
"data": {
"pageSize": 1,
"page": 1,
"total": 1,
"data": [
{ "contractAddress": "string", "chain": "ethereum", "mentionCount": 1 }
]
}
}
Request:
curl "https://api.elfa.ai/v2/aggregations/trending-cas/twitter?timeWindow=24h&page=1&pageSize=1&minMentions=5" \
-H "x-elfa-api-key: $ELFA_API_KEY"
| Field | Type | Meaning |
|---|---|---|
data.page | number | Current page. |
data.pageSize | number | Items per page. |
data.total | number | Total matching items. |
data.data[].contractAddress | string | The contract address. |
data.data[].chain | string | Chain of the contract, e.g. ethereum. |
data.data[].mentionCount | number | Mentions in the window. |
| Parameter | Required | Type | Meaning |
|---|---|---|---|
timeWindow | No | string | Window ending now, e.g. 30m, 1h, 4h, 24h, 7d, 30d. Default 7d. |
from | No | number | Start of the window, unix timestamp. Use with to. |
to | No | number | End of the window, unix timestamp. Use with from. |
page | No | number | Page number. Default 1. |
pageSize | No | number | Items per page. Default 50. |
minMentions | No | number | Minimum mentions for an item to be included. Default 5. |
timeWindow or from and to
Provide either timeWindow or both from and to. If you send both, from and to take priority and timeWindow is ignored.
Read It With Telegram
Use it to confirm whether a Telegram lead has crossed into the broader surface. Mention counts help an agent skip dead tickers.
Also via x402: GET /x402/v2/aggregations/trending-cas/twitter
Trending Contract Addresses on Telegram
GET /v2/aggregations/trending-cas/telegram returns contract addresses mentioned on Telegram, with mention counts.
Sample response (from the spec example):
{
"success": true,
"data": {
"pageSize": 1,
"page": 1,
"total": 1,
"data": [
{ "contractAddress": "string", "chain": "ethereum", "mentionCount": 1 }
]
}
}
Request:
curl "https://api.elfa.ai/v2/aggregations/trending-cas/telegram?timeWindow=24h&page=1&pageSize=1&minMentions=5" \
-H "x-elfa-api-key: $ELFA_API_KEY"
| Field | Type | Meaning |
|---|---|---|
data.page | number | Current page. |
data.pageSize | number | Items per page. |
data.total | number | Total matching items. |
data.data[].contractAddress | string | The contract address. |
data.data[].chain | string | Chain of the contract, e.g. ethereum. |
data.data[].mentionCount | number | Mentions in the window. |
| Parameter | Required | Type | Meaning |
|---|---|---|---|
timeWindow | No | string | Window ending now, e.g. 30m, 1h, 4h, 24h, 7d, 30d. Default 7d. |
from | No | number | Start of the window, unix timestamp. Use with to. |
to | No | number | End of the window, unix timestamp. Use with from. |
page | No | number | Page number. Default 1. |
pageSize | No | number | Items per page. Default 50. |
minMentions | No | number | Minimum mentions for an item to be included. Default 5. |
timeWindow or from and to
Provide either timeWindow or both from and to. If you send both, from and to take priority and timeWindow is ignored.
Read It Before Twitter
Telegram often shows contract addresses circulating before they reach broader Twitter visibility. Use it in place of group scraping or a hand-maintained watchlist.
Also via x402: GET /x402/v2/aggregations/trending-cas/telegram
Reading Twitter and Telegram Together
| Appears where | What it means |
|---|---|
| Telegram, not yet Twitter | Early circulation. |
| Both Telegram and Twitter | The move is already running. |
| Twitter, fading on Telegram | Late or losing freshness. |
Errors
No errors specific to these endpoints. See Enums and Errors.
Related
- Reference: Trending tokens, Trending CAs on Twitter, Trending CAs on Telegram
- Next: Mentions to inspect amplification and news for what you found, Narratives for the themes behind it, or Chat for interpretation.