Instagram API
Instagram Followers API
List about the first 50 followers of any public Instagram account by username: follower usernames, names, and profile details. Instagram caps follower lists, so this returns one page, not the whole list.
POST/v1/run/instagram.followers
Uptime
100.00%
30d · 10 calls
Requests
10
30d · weekly, last 12 wks
Response
1.8s
median · 30d
Provider network
Providers ranked by traffic
Try it
Make your first request
requireFieldsarrayOptional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `private`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
"data": {
"items": [
{
"handle": "alex_rivera",
"id": "a1b2c3d4",
"image": "https://example.com/image.jpg",
"name": "Example title",
"private": false,
"url": "https://example.com/page",
"verified": true
}
],
"nextCursor": "example"
},
"found": true
}Response interface
interface InstagramFollowersResponse {
data: {
items: {
handle: string;
id: string;
image?: string;
name?: string;
private?: boolean;
url?: string;
verified?: boolean;
}[];
nextCursor?: string | null;
} | null;
found: boolean;
}Full parameter and response reference - every field, type, and example for this endpoint.
Reference
Request, response, and price
Last verified 2026-09-16 · uptime and latency measured over 30dPOST /v1/run/instagram.followers
curl -X POST https://api.getanyapi.com/v1/run/instagram.followers \
-H "Authorization: Bearer $ANYAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"username":"nasa"}'| Field | Type | Example value |
|---|---|---|
| Request body | ||
| username | string | "nasa"The Instagram username, user ID, or profile URL whose followers to list (e.g. natgeo). |
| cursor | string | Opaque pagination cursor from a previous response's nextCursor. Today every source behind this endpoint returns a single page of about 50 followers and no continuation cursor, so nextCursor comes back empty and there is no further page to request; this parameter is accepted but has nothing to resume from. |
| requireFields | array | Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `private`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted. |
| Response | ||
| data | object | |
| data.items | object[] | Follower records for the target account. About the first 50, in the order the source returns them, not the account's full follower list - see nextCursor. Populated whenever the provider has data for the entity. |
| data.items[].handle | string | The follower's username, without the @ prefix. Populated whenever the provider has data for the entity. |
| data.items[].id | string | The follower's numeric Instagram user ID, as a string. Populated whenever the provider has data for the entity. |
| data.items[].imagecan require | string | URL of the follower's profile picture, with tracking query params stripped. Empty when the upstream omits it. |
| data.items[].namecan require | string | The follower's display name. Empty when the account has none. |
| data.items[].privatecan require | boolean | Whether the follower's account is private. |
| data.items[].urlcan require | string | Canonical URL of the follower's profile, with tracking query params stripped. Empty when the lane does not return it. |
| data.items[].verifiedcan require | boolean | Whether the follower's account is verified. |
| data.nextCursorcan require | string | Opaque cursor for the next page of followers, or null/empty when there are no more. Empty on every source behind this endpoint today, because each returns a single page of about 50 followers and no continuation. Pass it back as cursor whenever it is non-empty. |
| found | boolean | Whether the account was found and returned follower records. |
| Price | ||
| Price per request | USD | $0.0015 |
| Price /1k req | USD | $1.50 |
FAQ
About the Instagram Followers API
The AnyAPI Instagram Followers API returns Instagram followers data as normalized JSON from one POST call to /v1/run/instagram.followers. List about the first 50 followers of any public Instagram account by username: follower usernames, names, and profile details. Instagram caps follower lists, so this returns one page, not the whole list. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $1.50 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Instagram followers calls through AnyAPI succeeded, with a median response time of 1.8 seconds across 10 measured calls.
It costs from $1.50 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.
List about the first 50 followers of any public Instagram account by username: follower usernames, names, and profile details. Instagram caps follower lists, so this returns one page, not the whole list. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.
Over the last 30 days, 100.0% of Instagram followers calls through AnyAPI succeeded, with a median response time of 1.8 seconds across 10 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.
More to call
Other Instagram endpoints
Profilefrom $1.20 /1k reqUser postsfrom $0.80 /1k reqPostfrom $0.50 /1k reqUser reelsfrom $0.80 /1k reqPost commentsfrom $0.80 /1k reqHashtag searchfrom $1.20 /1k reqAudio reelsfrom $1.20 /1k reqBasic profilefrom $1.20 /1k reqComment repliesfrom $1.20 /1k reqEmbedfrom $1.20 /1k reqFollowingfrom $1.50 /1k reqHashtag analyticsfrom $1.93 /1k resultsHashtag recent postsfrom $1.50 /1k reqHashtag top postsfrom $1.50 /1k reqHighlight detailfrom $1.20 /1k reqLocation postsfrom $1.20 /1k reqMedia transcriptfrom $1.20 /1k reqPost likersfrom $2.40 /1k reqProfile contactfrom $2.57 /1k reqReel transcriptfrom $5.94 /1k audio minutesReels searchfrom $1.50 /1k reqSearchfrom $3.60 /1k reqSearch locationsfrom $2.40 /1k reqSearch profilesfrom $1.20 /1k reqSimilar profilesfrom $2.40 /1k reqStories fullfrom $2.40 /1k reqStories thinfrom $1.50 /1k reqTagged postsfrom $1.50 /1k reqTrending reelsfrom $1.20 /1k reqUser highlightsfrom $1.20 /1k reqUser repostsfrom $1.20 /1k reqWeb reels searchfrom $1.20 /1k req