Instagram API docs

Instagram API: Comments — replies by shortcode

Retrieve public Comments conversations from Instagram for audience monitoring, moderation, and content analysis.

Use “replies by shortcode” when you need discussion text, authors, timestamps, and sequential pagination.

Method GET
Entity Comments
Versions 2
What this endpoint does

What you can build with this API method

Review the result and common workflows first, then move to parameters and a working request example.

What this endpoint helps with

The response includes conversation items, public author data, engagement signals, and pagination fields.

When to use it

Use “replies by shortcode” when you need discussion text, authors, timestamps, and sequential pagination.

Common use cases

Conversation monitoring

Track audience reactions under content and around selected objects.

Moderation

Send public messages into review, classification, and quality-control queues.

Feedback analysis

Use discussion text and metadata in reports and audience research.

Available versions

Response version

Both versions solve the same job and accept the same parameters. Use the switch to compare the response structure and choose the version your client expects.

Response version V2

Switch versions on this page to compare response structures while keeping the same documentation URL.

What stays the same

Authentication, required parameters, and the request shape stay the same across V1 and V2. In practice, you choose the version when you build the endpoint path and when you parse the response.

What changes between versions

The main difference is the response envelope. Use V2 for new integrations and keep V1 only when you need compatibility with an existing client contract.

How to use it

How to call the method

Use the same API key header and the same query parameters for both versions. This documentation shows the shared parameter set first, then version-specific endpoint paths and code snippets.

Input parameters

Shared parameters
Parameter Required Type Example Description
comment_id Yes str value ID of the comment whose related data you want to retrieve.
shortcode Yes str value Short code from the post's public URL.

Version-specific request path

V2

Choose a version when you copy the exact endpoint path, example URL, and code snippet. The parameter list above stays the same.

GET /api/v2/instagram.com/comments/replies-by-shortcode

Normalized format

Code examples

curl --request GET \
  --url "https://www.scrapestorm.net/api/v2/instagram.com/comments/replies-by-shortcode" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'comment_id=value' \
  --get --data-urlencode 'shortcode=value'
Response example

Live response by version

The preview keeps key fields and the first collection items so you can scan the response shape quickly. Switching versions changes the JSON format.

Response example

V2 response JSON

Placeholder

A live verification example is not available for V2 yet. This placeholder keeps the standard response envelope visible until a verified example is ready.

{
  "success": true,
  "status": "ok",
  "data": {}
}
What to do next

Continue the evaluation

Use this documentation as the first decision point, then move into pricing, platform coverage, and integration rules before you connect the endpoint for recurring use.

Open the Instagram platform page

Compare adjacent entities, API method groups, and related docs before implementation.

Open platform page

Compare API method pricing

Check where this API method sits inside the public price table before you scale usage.

View pricing

Review integration rules

Use the starter docs to confirm authentication, versioning, retries, and mock vs live behavior.

Open docs
FAQ

Questions teams ask before implementation

Use these answers to decide whether this API method fits your workflow, versioning choice, and rollout plan.

What data does this Instagram API method return?

The method performs “replies by shortcode” for Comments. The compact response example below shows the exact field structure.

Should I choose V1 or V2?

Choose V2 for new integrations because it provides a normalized structure. Use V1 only for compatibility with clients that already consume the platform-native format.

What do I need for the first request?

Create an API key, send it in the request header, and provide the required parameters from the table. The code samples already contain the correct path and request structure.