
spacefan Incredible shot 🔭
Sep 16, 202542 likesReply
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.
{"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}
Pricing and providers
The cheapest provider serves first. If it fails, the next one takes over in the same call.
Try it
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
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
JSON, posted to this endpoint.
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.
Pagination cursor from a previous response's nextCursor.
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.
JSON, one example value per field.
Populated whenever the provider has data for the entity.
spacefan
Populated whenever the provider has data for the entity.
URL of the commenting account's profile avatar image.
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.
18051843701642870
Populated whenever the provider has data for the entity.
42
Number of likes on the comment. Null when the source does not report it.
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.
Incredible shot 🔭
Populated whenever the provider has data for the entity.
Instagram user id of the commenting account. Null when this source does not report it.
false
Opaque cursor for the next page of comments, or null when this lane has no more. Pass it back as cursor to continue.
true
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.
Selling this API? See the full schema your endpoint must return.
FAQ
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.

spacefan Incredible shot 🔭
Sep 16, 202542 likesReply