Instagram API

Instagram Following API

List about the first 50 accounts a public Instagram user follows: usernames, names, and profile details. Instagram caps these lists, so this returns one page, not the whole list.

POST/v1/run/instagram.following
Uptime
100.00%
30d · 7 calls
Requests
7
30d · weekly, last 12 wks
Response
1.2s
median · 30d

Provider network

Providers ranked by traffic

Try it

Make your first request

requireFieldsarray
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.
Open in
Get a free key
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 InstagramFollowingResponse {
  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 30d
POST /v1/run/instagram.following
curl -X POST https://api.getanyapi.com/v1/run/instagram.following \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"username":"nasa"}'
FieldTypeExample value
Request body
usernamestring"nasa"The Instagram username, user ID, or profile URL whose following list to fetch (e.g. natgeo).
cursorstringOpaque pagination cursor from a previous response's nextCursor. Today every source behind this endpoint returns a single page of about 50 accounts 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.
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.
Response
dataobject
data.itemsobject[]Records for the accounts the target user follows. About the first 50, in the order the source returns them, not the user's full following list - see nextCursor. Populated whenever the provider has data for the entity.
data.items[].handlestringThe followed account's username, without the @ prefix. Populated whenever the provider has data for the entity.
data.items[].idstringThe followed account's numeric Instagram user ID, as a string. Populated whenever the provider has data for the entity.
data.items[].imagecan requirestringURL of the followed account's profile picture, with tracking query params stripped. Empty when the upstream omits it.
data.items[].namecan requirestringThe followed account's display name. Empty when the account has none.
data.items[].privatecan requirebooleanWhether the followed account is private.
data.items[].urlcan requirestringCanonical URL of the followed account's profile, with tracking query params stripped. Empty when the lane does not return it.
data.items[].verifiedcan requirebooleanWhether the followed account is verified.
data.nextCursorcan requirestringOpaque cursor for the next page of results, 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 accounts and no continuation. Pass it back as cursor whenever it is non-empty.
foundbooleanWhether the account was found and returned following records.
Price
Price per requestUSD$0.0015
Price /1k reqUSD$1.50

FAQ

About the Instagram Following API

The AnyAPI Instagram Following API returns Instagram following data as normalized JSON from one POST call to /v1/run/instagram.following. List about the first 50 accounts a public Instagram user follows: usernames, names, and profile details. Instagram caps these 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 following calls through AnyAPI succeeded, with a median response time of 1.2 seconds across 7 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 accounts a public Instagram user follows: usernames, names, and profile details. Instagram caps these 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 following calls through AnyAPI succeeded, with a median response time of 1.2 seconds across 7 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.