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.

$1.88/1k req, pay per request, no subscription.

What the API returneditems[0]
{
"id": "5510239490",
"handle": "kingarthurbaking",
"name": "King Arthur Baking Co.",
"image": "https://scontent.cdninstagram.com/v/t51.2885-19/king_arthur_avatar.jpg",
"verified": true,
"private": false,
"url": "https://www.instagram.com/kingarthurbaking/"
}
Uptime
99.95%
30d · 1,900 calls
Requests
1,902
30d · weekly, last 12 wks
Response
3.9s
median · 30d

Pricing and providers

Instagram Following API pricing: one API, 2 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

You pay
$18.80
$1.88/1k req, only for what you use. No monthly plan.
Your first 53 requests are free with the $0.10 starting balance.

Try it

Get Instagram following in one 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.

This sample shows 11 of 12 fields. See every field

{
  "found": true,
  "data": {
    "items": [
      {
        "id": "5510239490",
        "handle": "kingarthurbaking",
        "name": "King Arthur Baking Co.",
        "image": "https://scontent.cdninstagram.com/v/t51.2885-19/king_arthur_avatar.jpg",
        "verified": true,
        "private": false,
        "url": "https://www.instagram.com/kingarthurbaking/"
      },
      {
        "id": "5510239491",
        "handle": "theoparkerfit",
        "name": "Theo Parker",
        "image": "https://scontent.cdninstagram.com/v/t51.2885-19/theo_parker_avatar.jpg",
        "verified": true,
        "private": false,
        "url": "https://www.instagram.com/theoparkerfit/"
      },
      {
        "id": "5510239492",
        "handle": "mira.codes",
        "name": "Mira Chen",
        "image": "https://scontent.cdninstagram.com/v/t51.2885-19/mira_chen_avatar.jpg",
        "verified": false,
        "private": false,
        "url": "https://www.instagram.com/mira.codes/"
      }
    ],
    "nextCursor": null
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-31 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • usernamestring

    junobakes

    The Instagram username, user ID, or profile URL whose following list to fetch (e.g. natgeo).

  • cursorstring

    Opaque 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.

  • 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.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

each itemdata.items[]

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.

  • handlestring

    kingarthurbaking

    The followed account's username, without the @ prefix. Populated whenever the provider has data for the entity.

  • idstring

    5510239490

    The followed account's numeric Instagram user ID, as a string. Populated whenever the provider has data for the entity.

  • imagestring

    https://scontent.cdninstagram.com/v/t51.2885-19/king_arthur_avatar.jpg

    URL of the followed account's profile picture, kept whole because its query carries the CDN signature. Empty when the upstream omits it.

  • namestring

    King Arthur Baking Co.

    The followed account's display name. Empty when the account has none.

  • privatebooleancan require

    false

    Whether the followed account is private.

  • urlstring

    https://www.instagram.com/kingarthurbaking/

    Canonical URL of the followed account's profile, with tracking query params stripped. Empty when the lane does not return it.

  • verifiedboolean

    true

    Whether the followed account is verified.

datadata
  • nextCursorstring

    null

    Opaque cursor for the next page of results, or null/empty when there are no more. Some sources return a single page of about 50 accounts and no continuation, so it is empty there. Pass it back as cursor whenever it is non-empty.

top level
  • foundboolean

    true

    Whether the account was found and returned following records.

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

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.88 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 99.9% of Instagram following calls through AnyAPI succeeded, with a median response time of 3.9 seconds across 1,900 measured calls.

It costs from $1.88 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

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, 99.9% of Instagram following calls through AnyAPI succeeded, with a median response time of 3.9 seconds across 1,900 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 53 Instagram Following calls at $0.00188 each.

AnyAPI asks the next of its 2 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/instagram.following with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.