
One call returns the accounts a given X account started following on a specific date. Each item is one account that was followed on that date. The answer was empty (total: 0), meaning no follows occurred on that date.
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 the accounts an X account started following on a given dayGET friendshipHistory/following | $0.00$0.0e+00 / 1k calls |
From a real call to the route: TwitterScore.
HTTP 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). |
| date | string · query | required | Day to read, YYYY-MM-DD.e.g. 2026-10-06 |
| tag_ids | string · query | optional | Only accounts with these tag ids (comma-separated). |
| size | integer · query | optional | Rows. · default 10e.g. 10 |
curl "https://fetchapi.co/api/gw/twitterscore/friendshipHistory/following?date=2026-10-06&size=10&username=VitalikButerin" \ -H "x-api-key: YOUR_KEY"
call_endpoint("twitterscore.friendship_history_following", {"date": "2026-10-06", "size": "10", "username": "VitalikButerin"}){
"data": [],
"page": 1,
"size": 0,
"pages": 1,
"total": 0,
"success": true
}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.