Comments

Each call reads one page of comments live from the platform; nothing is stored. Pass the returned nextCursor back as cursor until there is no next page.

Read a page of comments

curl -G {API_BASE_URL}/v1/comments \
  -H "Authorization: Bearer <API_TOKEN>" \
  --data-urlencode "url=https://www.instagram.com/p/ABC123/"

There are no other parameters. Any other query parameter is ignored.

{
  "platform": "instagram",
  "postUrl": "https://www.instagram.com/p/ABC123/",
  "comments": [
    {
      "id": "17890012345678",
      "username": "creator_jane",
      "text": "Love this!",
      "createdAt": "2026-09-23T10:00:00.000Z",
      "likeCount": 4,
      "replyCount": 1
    }
  ],
  "nextCursor": "cursor-value",
  "hasMore": true
}

Only top-level comments are returned. replyCount counts the replies to a comment; the replies themselves are comment replies.

A 200 with an empty first page means the post has no comments. A post that is gone returns 404 POST_NOT_FOUND instead. On TikTok, an empty first page is checked against the video itself, so a missing video returns an error, typically 404, and does not look like a video with no comments.

Order and page size

Read every page

Every page is a separate data lookup, so a post with many comments costs one lookup per page. A page that fails is not counted.

async function allComments(postUrl: string) {
  const comments = [];
  let cursor: string | null = null;
  do {
    const params = new URLSearchParams({ url: postUrl });
    if (cursor) params.set("cursor", cursor);
    const res = await fetch(`${API_BASE_URL}/v1/comments?${params}`, {
      headers: { Authorization: `Bearer ${API_TOKEN}` },
    });
    if (!res.ok) throw new Error((await res.json()).error);
    const page = await res.json();
    comments.push(...page.comments);
    cursor = page.hasMore ? page.nextCursor : null;
  } while (cursor);
  return comments;
}

The cursor is opaque: send back only what nextCursor returned, unchanged. Stop when nextCursor is null, even if hasMore is true. The two differ by platform:

The route allows 60 requests per minute from one client IP, so pace a long walk or handle 429 RATE_LIMITED by waiting for the Retry-After header.

Errors

Every error has the standard error and message envelope, and you branch on error.

Comments on an Instagram post with an age restriction can fail as 502 or 504 rather than POST_AGE_RESTRICTED, because the read stalls instead of being refused. Retrying will not help while the post stays age-restricted.

Any other failure returns 500 INTERNAL_ERROR. See data lookup errors for the codes every data lookup shares. 404 and 422 are permanent for that post; 429, 502, 503 and 504 are worth retrying.

Comment replies

Replies read the replies to one comment on an Instagram post or reel, a TikTok video or a YouTube video, one page at a time. On YouTube, a reply lookup takes the continuation token that a comment returns, not a comment id.

YouTube comments

• YouTube. Input: video, and top or newest order. Returns the video's comments. A cap applies to how many comments one video returns.

Replies to an X post

• X. Input: the post id, not the post URL. Returns the replies to the post.