Instagram comments API | All Them APIs

What to build with it

Choose a video by URL or ID, then collect the first comment page.
Follow the returned cursor and deduplicate comments rather than assuming page numbers.
Report the collected sample size and collection time alongside any sentiment analysis.
Keep observed public comments separate from direct messages and private account interactions, which this operation does not provide.

Provider reference: Virlo documentation. Authentication uses a provider-issued Bearer token, stored on your server.

Endpoints and inputs

1 documented operation. Query and path fields are listed separately from JSON request-body fields.

GET/v1/raw/instagram/video/comments

Send exactly one of url or id. The fields are individually optional in the schema, but omitting both or sending both does not satisfy the documented request contract.

Path and query parameters

url: string (query) · optional
id: string (query) · optional
cursor: string (query) · optional

Documented response fields

data: array · required
data[].id: string · required
data[].text: string · required
data[].published_at: string | null · required
data[].likes: number | null · required
data[].reply_count: number | null · required
data[].author: object · required
data[].author.id: string | null · required
data[].author.handle: string | null · required
data[].author.display_name: string | null · required
data[].author.avatar_url: string | null · required
data[].author.verified: boolean | null · required
pagination: object · required
pagination.next_cursor: string | null · required
pagination.has_more: boolean · required

Documented HTTP responses: 200, 400, 401, 402, 404, 429, 502, 503, 504. Handle each non-success response explicitly; do not silently convert a failed lookup to an empty result.

Before you integrate

Public-data discovery is different from the authenticated Instagram publishing API. Do not use these endpoints to promise account management, private insights or posting.
Collected comments are not a representative audience survey. Respect privacy and retention requirements; avoid publishing identifiable commenters unnecessarily.

Check the provider's current price, allowed use and retention terms before sending requests. An optional field can be absent; the schema alone does not establish its completeness or accuracy.

For a deeper profile, compare the creator lookup with the ongoing tracking workflow.

Give this task to your coding agent

instagram-comments-api agent prompt

Help me implement instagram comments api using the documented Virlo API.

Reference: https://allthemapis.com/social-media-apis/instagram-comments-api
Provider documentation: https://dev.virlo.ai/docs/raw
Base URL: https://api.virlo.ai
Starting operation: GET /v1/raw/instagram/video/comments

Read the current provider docs and confirm the required inputs before writing code. Load VIRLO_API_KEY from a server-side environment variable and use Bearer authentication. Do not put the key in client code, logs, analytics, or the chat.

Ask me for any missing video URL, creator handle, research intent, or job ID. Do not invent a result. Ask for approval before starting billable lookups, recurring jobs, or destructive changes. For jobs, keep the returned ID and poll with the documented delay instead of starting the job twice. Handle pagination, rate limits, partial results, and missing fields explicitly.

Build the smallest integration for this task:
1. Choose a video by URL or ID, then collect the first comment page.
2. Follow the returned cursor and deduplicate comments rather than assuming page numbers.
3. Report the collected sample size and collection time alongside any sentiment analysis.
4. Keep observed public comments separate from direct messages and private account interactions, which this operation does not provide.

Return the code, the environment variables I need, and a short explanation of what was actually retrieved versus inferred. Do not execute paid requests until I approve.

Sources and review dates

Virlo's public documentation and OpenAPI schema reviewed October 27, 2026. Endpoint paths and field names below refer to that provider's API. This is an integration reference, not a measured performance ranking.

Corrections: email faizank@docsalot.dev with an official source.