Nexscope

Instagram Comments

Read public Instagram post or reel comments with text, timestamps and commenter details. Reply counts are included when Instagram provides them.

CostAt least 10 credits / call
Try online
POST · https://api.nexscope.ai/social/instagram/post/commentsMCP · social_instagram_post_comments

What this API does

Read public Instagram post or reel comments with text, timestamps and commenter details. Reply counts are included when Instagram provides them. The request accepts url, include_replies, cursor. Its documented result includes platform, resourceStatus.

Instagram Comments API use cases

Plan a Instagram Comments request

A researcher checks the published operation description and supplies url, include_replies, cursor for Instagram Comments. The request stays within the supported parameters rather than assuming other platform capabilities.

Inspect Instagram Comments results

An analyst reviews platform, resourceStatus from Instagram Comments for the requested subject. Missing values remain explicit, and the response does not establish complete platform coverage.

Document Instagram Comments observations

A researcher records the inputs and available results from Instagram Comments alongside its published description. The record supports a scoped review without inferring unsupported actions, refresh intervals or broader conclusions.

Instagram Comments API FAQ

What does the Instagram Comments API return?

Read public Instagram post or reel comments with text, timestamps and commenter details. Reply counts are included when Instagram provides them. The documented output includes platform, resourceStatus. It corresponds to the supplied url, include_replies, cursor. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Instagram Comments API cost?

The current documented cost is At least 10 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Instagram Comments API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/social/instagram/post/comments with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call social_instagram_post_comments. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/social/instagram/post/comments
MCP method
social_instagram_post_comments

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/social/instagram/post/comments

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/social/instagram/post/comments' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "https://www.instagram.com/reel/DOq6eV6iIgD"
}'

Code example

{
  "url": "https://www.instagram.com/reel/DOq6eV6iIgD"
}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.
All categories/ Social Data
POSThttps://api.nexscope.ai/social/instagram/post/comments

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/social/instagram/post/comments
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
urlstringrequired
The URL of the post or reel to get comments from
Example: https://www.instagram.com/reel/DOq6eV6iIgD
include_repliesbooleanoptional
Set to true to include replies for every returned comment. Costs 15 credits when comments are returned, This is much slower and may time out at 29 seconds.
cursorstringoptional
The cursor to get more comments. Get 'cursor' from previous response.

Social data contract

Use your Nexscope API key. No supplier credentials are required. Requests reject unknown fields, including pageSize. URLs require HTTPS and an exact supported platform host and resource path. Documented YouTube video URLs may use youtu.be; other short links are unsupported. Check the request schema for supported fields and defaults.

Each request fetches one page. Continue manually with the returned nextCursor, or nextPage for Instagram Reels (pages 1–11). Cursors are opaque, unchanged strings up to 65536 UTF-8 bytes. No automatic pagination, retry, media download or transcription is performed. Repeated requests may purchase data again.

Resource status is independent of HTTP and billing: AVAILABLE, PARTIAL, PRIVATE, RESTRICTED, NOT_FOUND, NO_TRANSCRIPT or UNKNOWN can accompany code 0. Unknown values remain null; arrays remain empty arrays. fetchedAt is the response observation time; sourceFetchedAt is null without source evidence.

usage.billingStatus is NOT_CHARGED, SETTLED or UNKNOWN; chargedCredits is null when unconfirmed. Unknown charges never mean free. Completed lookups have a minimum charge of 10 credits, including cached, no-caption and unavailable-resource results; check API usage records for the actual charge. Parameter errors and unpublished APIs use the standard error envelope; upstream failures use code 13007, rate limits 429 and timeouts 408. Always check code and msg.

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

{
  "code": 0,
  "cost": "-1",
  "data": {
    "data": {
      "comments": [
        {
          "child_comment_count": 0,
          "comment_like_count": 0,
          "created_at": "2025-09-16T17:03:04.000Z",
          "has_more_replies": false,
          "id": "18051843701642870",
          "replies": [],
          "replies_cursor": null,
          "text": "\"...but who wants to know people who don't love animals anyway?\". ❤️",
          "user": {
            "fbid_v2": "17841446780736699",
            "id": "46773599357",
            "is_unpublished": null,
            "is_verified": false,
            "pk": "46773599357",
            "profile_pic_url": "https://scontent-dfw5-1.cdninstagram.com/v/t51.2885-19/542013919_18051324464559358_4060586438619554592_n.jpg?stp=dst-jpg_s150x150_tt6&efg=eyJ2ZW5jb2RlX3RhZyI6InByb2ZpbGVfcGljLmRqYW5nby4xMDgwLmMyIn0&_nc_ht=scontent-dfw5-1.cdninstagram.com&_nc_cat=110&_nc_oc=Q6cZ2QEVOAPWq7DXE6cVfhoMQb0GTMvPo_vizELP9TUgQylvA5jBW1WSonDzvjeTQpAGJ3w&_nc_ohc=b__bzrMG6kYQ7kNvwGXM67R&_nc_gid=oDBffhoPbGLAq2tbCGpGKg&edm=AKp6CbIBAAAA&ccb=7-5&oh=00_AflThVwZ86n6DiACA5-zJCNFQZWBwHfaG6AXZclgea57BA&oe=695A3139&_nc_sid=d62176",
            "username": "catherina_thijs"
          }
        }
      ],
      "cursor": "AQHSpoi6HyDbzYRMzrD.........",
      "success": true
    },
    "platform": "instagram",
    "resourceStatus": "AVAILABLE",
    "usage": {
      "billingStatus": "UNKNOWN"
    }
  },
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

NameTypeRequiredDescription
codeintegerrequired
0 means accepted or successful; nonzero is a platform error.
coststringrequired
Elapsed milliseconds, never credits; -1 outside web requests.
dataanyrequired
Data value used by this API operation.
msgstring | nullrequired
Msg value used by this API operation.
timestringrequired
Server local time: yyyy-MM-dd HH:mm:ss.
traceIdstring | nullrequired
Trace id value used by this API operation.
tsstringrequired
Epoch milliseconds.

Any of option 1 — requires platform, resourceStatus, data, usage

NameTypeRequiredDescription
dataobjectrequired
Data value used by this API operation.
data.dataobjectrequired
Data value used by this API operation.
data.platformstringrequired
Platform value used by this API operation.
data.resourceStatusstringrequired
Resource status value used by this API operation.
data.usageobjectrequired
Usage value used by this API operation.

Any of option 2

NameTypeRequiredDescription
datanullrequired
Data value used by this API operation.

Responses

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json
Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "social_instagram_post_comments",
    "arguments": {
      "url": "https://www.instagram.com/reel/DOq6eV6iIgD"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What data can Instagram Comments provide, and how might I use it?

AI answer

Retrieves comments on a public Instagram post or reel. Each comment includes the comment text, creation timestamp, reply count when Instagram provides it, and commenter details such as username, user ID, verification status, and profile picture URL. child_comment_count can be null when Instagram does not expose the count publicly. Set include_replies=true to fetch the first page of replies for every returned comment. This adds replies, replies_cursor, and has_more_replies to each

Data categoryDocumented fieldsHow to use them
Requesturl, cursor, include_repliesProvide the required identifiers, filters, or paging inputs listed in the API document.
Responsedata.data, data.platform, data.resourceStatusInspect returned values and source references; availability depends on the request and upstream source.
  • Review Instagram Comments.
    • Prompt example: “Retrieve Instagram Comments for [public URL]. Summarize only the information actually returned and preserve source links when available. Report private, restricted, missing or partial results explicitly; missing values are not zero.”
  • Collect a Bounded Set of Results.
    • Prompt example: “Retrieve Instagram Comments for [public URL] across at most two pages within my approved credit budget. Use only the continuation information actually returned, with the same query and filters. Stop at the documented page limit, an absent continuation, an end indicator or a repeated page. Keep source references and report that the collection is bounded, not exhaustive.”
  • Read Comments With Their Reply Context.
    • Prompt example: “Use Instagram Comments for [public URL]. Include replies for returned comments only after I approve the documented additional charge. Keep parent comments and replies associated; do not claim every thread is complete.”
  • Prepare a Snapshot of Returned Public Counts.
    • Prompt example: “Retrieve Instagram Comments for [public URL] and make a compact table of the public counts actually returned. Keep each count attached to its item or account, label estimates and preserve the observation time when supplied. Do not invent engagement rates, historical growth, unique audience size or missing values.”

These are suggested workflows, not completed lookups. Report missing, restricted, or partial data explicitly; verify the live response before making a decision.

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

One request fetches one page. Copy nextCursor into cursor, or nextPage into page (1–11 for Reels), then run manually. Repeated requests may purchase data again. Completed lookups have a minimum charge of 10 credits, including cached, no-caption, private, restricted and not-found results. Resource status and actual billing status are independent; null credits are unknown, never free. Check usage.billingStatus, usage.chargedCredits and API usage records for the actual charge.

Try it

Send a real request with the same contract shown in the reference.

Endpoint
/social/instagram/post/comments
MCP method
social_instagram_post_comments
cURL
curl -X POST \
  https://api.nexscope.ai/social/instagram/post/comments \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://www.instagram.com/reel/DOq6eV6iIgD" }'
Request estimate: Estimating…Usage based. The final charge depends on actual usage. Estimating does not run the API or charge credits.API usage records
Response
No response yet. Run the request to see the response here.

Related APIs