
One call returns the IDs of accounts a user follows; one item is a user id string. The call held 20 items (count=20). For the next page, pass pagination.nextCursor as cursor.
1 live route on X, from $0.00019 per call. Every route below answered our last live test on 2026-10-06; 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 |
|---|---|---|
twitter-api47RapidAPI listing | Following IDsGET v3/user/following-ids | $0.00019$0.19 / 1k calls |
From a real call to the route: twitter-api47.
data[]followed user idpagination.nextCursorcursor for the next pagepagination.prevCursorcursor for the previous pagePaging: read `pagination.nextCursor` from the answer and send it back as `cursor=` for the next page; stop when it is empty or repeats. From MCP: call_endpoint("rapidapi-twitter-api47.following_ids", params, pages=3) follows it for you.
HTTP with your key in x-api-key, or the call_endpoint tool of our MCP server.
| Parameter | Type | Notes | |
|---|---|---|---|
| count | string · query | optional | default 20 |
| cursor | string · query | optional | |
| userId | string · query | required | default 34743251e.g. 44196397 |
curl "https://fetchapi.co/api/gw/rapidapi-twitter-api47/v3/user/following-ids?count=20&userId=44196397" \ -H "x-api-key: YOUR_KEY"
call_endpoint("rapidapi-twitter-api47.following_ids", {"count": "20", "userId": "44196397"}){
"data": [
"2106001146925953025",
"1572780417601740800",
"… 2 more"
],
"pagination": {
"nextCursor": "1875286869520815722",
"prevCursor": "0"
}
}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.