Instagram API

Instagram Post comments API

List the comments on a post or reel by URL with cursor pagination: text, author, verification and like count.

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

What the API returnedcomments[0]
{
"id": "18051843701642870",
"text": "Incredible shot 🔭",
"author": "spacefan",
"verified": false,
"likes": 42,
"createdAt": "2025-09-16T17:03:04.000Z",
"avatarUrl": string,
"createdUtc": number,
... 2 more fields
}
Uptime
99.94%
30d · 323,270 calls
Requests
332,200
30d · weekly, last 12 wks
Response
1.9s
median · 30d

Pricing and providers

Instagram Post comments API pricing: one API, 6 interchangeable providers

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

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

Try it

Get Instagram post comments 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 `replies`, 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 comment that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
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 8 of 14 fields. See every field

{
  "found": true,
  "data": {
    "comments": [
      {
        "id": "18051843701642870",
        "text": "Incredible shot 🔭",
        "author": "spacefan",
        "verified": false,
        "likes": 42,
        "createdAt": "2025-09-16T17:03:04.000Z"
      }
    ]
  }
}

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-11-06 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • urlstring

    https://www.instagram.com/p/C8aBcDeFgHi/

    Full Instagram post or reel URL, carrying the media shortcode: /p/, /reel/, /reels/, or /tv/. A profile URL such as https://www.instagram.com/username names no post, so it is rejected instead of charged for an empty result - send that account's handle to instagram.user_posts to list its posts.

  • cursorstring

    Pagination cursor from a previous response's nextCursor.

  • 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 `replies`, 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 comment that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.

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

Response

JSON, one example value per field.

each commentdata.comments[]

Populated whenever the provider has data for the entity.

  • authorstring

    spacefan

    Populated whenever the provider has data for the entity.

  • avatarUrlstring

    URL of the commenting account's profile avatar image.

  • createdUtcnumber

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. Populated whenever the provider has data for the entity.

  • idstring

    18051843701642870

    Populated whenever the provider has data for the entity.

  • likesinteger

    42

    Number of likes on the comment. Null when the source does not report it.

  • repliesintegercan require

    Number of replies to the comment, which tells you whether instagram.comment_replies has anything to fetch. Null when this source does not report it.

  • textstring

    Incredible shot 🔭

    Populated whenever the provider has data for the entity.

  • userIdstringcan require

    Instagram user id of the commenting account. Null when this source does not report it.

  • verifiedboolean

    false

datadata
  • nextCursorstring

    Opaque cursor for the next page of comments, or null when this lane has no more. Pass it back as cursor to continue.

top level
  • foundboolean

    true

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

Selling this API? See the full schema your endpoint must return.

FAQ

About the Instagram Post comments API

The AnyAPI Instagram Post comments API returns Instagram post comments data as normalized JSON from one POST call to /v1/run/instagram.post_comments. List the comments on a post or reel by URL with cursor pagination: text, author, verification and like count. AnyAPI routes each request across 6 sources and falls back automatically when one fails. It costs from $0.80 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 99.9% of Instagram post comments calls through AnyAPI succeeded, with a median response time of 1.9 seconds across 323,270 measured calls.

It costs from $0.80 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 the comments on a post or reel by URL with cursor pagination: text, author, verification and like count. 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 post comments calls through AnyAPI succeeded, with a median response time of 1.9 seconds across 323,270 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 125 Instagram Post comments calls at $0.0008 each.

AnyAPI asks the next of its 6 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.post_comments 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.