
One call returns daily follower counts for an X account over a time period (default 1 month, or all history if period=all). Each item is one day's follower count. The answer held 30 items (one per day in the last month). Get the next page by passing the `page` parameter.
1 live route on X, from $0.00 per call. Every route below answered our last live test on 2026-10-08; the gateway re-tests them daily.
The upstream price you are metered at, cheapest first. A route without a published price says so.
| Provider | Endpoint | Price |
|---|---|---|
List an X account's daily follower counts (history)GET followers_count_history | $0.00$0.0e+00 / 1k calls |
From a real call to the route: TwitterScore.
followers_count[].dateDate (YYYY-MM-DD)followers_count[].followers_countFollower count on that datetotalTotal days in the periodHTTP with your key in x-api-key, or the call_endpoint tool of our MCP server.
| Parameter | Type | Notes | |
|---|---|---|---|
| username | string · query | optional | X username without @ (or send twitter_id instead).e.g. VitalikButerin |
| twitter_id | string · query | optional | X numeric id (or send username instead). |
| period | string · query | optional | 3d, 1w, 1m, 6m, 1y or all (default 30 days). · default 1m |
| page | integer · query | optional | Page, for period=all. |
curl "https://fetchapi.co/api/gw/twitterscore/followers_count_history?period=1m&username=VitalikButerin" \ -H "x-api-key: YOUR_KEY"
call_endpoint("twitterscore.followers_count_history", {"period": "1m", "username": "VitalikButerin"}){
"page": 1,
"size": 30,
"pages": 1,
"total": 30,
"success": true,
"followers_count": [
{
"date": "2026-10-08",
"followers_count": 7983358
},
{
"date": "2026-10-07",
"followers_count": 7977193
},
"… 1 more"
]
}Call it over HTTP or from any MCP client. Each key has a rate limit and a monthly cap; calls are metered at the upstream price.