Instagram Comments API
The Instagram Comments API brings Instagram comment management into a SaaS product, agency workflow, support tool, or automation through one API.
curl -X GET "{{API_BASE_URL}}/v1/comments/?platform=instagram&accountId=acc_ig_biz_789&postId=17901234567890123&limit=25" \
-H "x-access-key: your-api-key"curl -X GET "{{API_BASE_URL}}/v1/comments/?platform=instagram&accountId=acc_ig_biz_789&postId=1790123456789…
-H "x-access-key: your-api-key"
It supports listing comments and first-level replies, replying or creating a top-level comment, hiding or unhiding comments, and deleting comments on connected Instagram Business or Creator accounts.
Instagram Comments API overview
The Instagram Comments API is intended for developers adding comment reading and moderation to an existing product or automation. The core workflow is to connect an Instagram Business or Creator account, identify a post belonging to that connected account, list its comments and first-level replies, and then act on individual comments. Personal Instagram accounts are not eligible for these comment-management endpoints, so account-type checks should happen before any comment workflow is offered in a product.
Captured contract: List Comments request and response
The captured contract for listing is a GET request to {{API_BASE_URL}}/v1/comments/ with platform set to instagram, plus accountId, postId, and limit query parameters, and an x-access-key header. The captured response status is 202 and the body contains success, a comments array, and nextCursor. Each comment in the example contains id, text, author with id and name, timestamp, likeCount, hidden, and replies. Replies in the example contain id, text, author, timestamp, and likeCount. Treat the values in the worked example as illustrative placeholders for identifiers and content, while preserving the field names and structure exactly as captured.
List Comments and Replies: worked example with cursor pagination
List Comments and Replies is the starting operation in the List Comments request example and List Comments response example. Use it to fetch comments for a single post. Pass the connected account identifier as accountId and the media identifier as postId, and set limit to control page size. When the response includes nextCursor, that value indicates a further page exists; the request parameter or mechanism for supplying the cursor on a follow-up request was not captured in the supplied source, so do not assume a parameter name. Store the cursor opaquely and do not parse or construct it. Check success before rendering comments, and preserve hidden and likeCount values from each item so moderation state and engagement counts stay visible in your interface.
Moderation actions: reply, create, hide, unhide, and delete
Beyond listing, the source describes a reply and comment capability where the same endpoint is used by switching between a postId for a top-level comment and a commentId for a reply to an existing comment. It also describes Hide and Unhide as an Instagram-specific moderation action and Delete Comments as removal by comment ID. Because only the List Comments method, path, parameters, and response contract were captured, this page does not specify methods, paths, or payloads for those other actions. Implement them only from their own captured contracts, and keep the postId versus commentId distinction in your data model so a top-level comment is never mistaken for a reply.
Hide versus delete and existing-posts eligibility
Choose Hide and Unhide when moderation should be reversible, for example when spam or an unwanted comment may need to be restored after review. Choose Delete Comments when the comment should be removed permanently and hiding is not enough. Works on Existing Posts is the eligibility rule to apply in both cases: the post only needs to belong to the connected Instagram account, so comments on media published outside the API workflow can still be managed. Before deleting, confirm the comment ID from the list response and consider whether a reversible hide would preserve the record you need for support or audit workflows.
Failure matrix and checks before you call
Check account eligibility first: a personal account should fail the eligibility check for comment management, which requires a Business or Creator account. Check post ownership next: a post that does not belong to the connected account is outside the Works on Existing Posts rule and should not be treated as manageable. Treat unsupported actions as out of scope rather than guessing a contract; only List Comments has a captured method, path, and response in this draft. For listing failures, verify the x-access-key header, the platform value, and that accountId and postId match the connected account before retrying, and do not invent error codes that were not captured.
Meta permission, OAuth, and per-request credit
The hosted integration is described as approved for the instagram_business_manage_comments permission and as handling the Instagram OAuth flow, so a product using that hosted integration does not need to complete Meta App Review for it. Scope that statement to the hosted integration and permission as described; do not generalize it to a self-built Meta app. Each Comments API request uses 1 credit, and listing, replying, creating a comment, hiding, unhiding, and deleting are each separate API calls, so budget moderation queues by the number of calls rather than by the number of comments viewed.
| Parameter | Location | Example value | Purpose |
|---|---|---|---|
| platform | Query | Selects Instagram comment listing | |
| accountId | Query | acc_ig_biz_789 | Identifies the connected Instagram account |
| postId | Query | 17901234567890123 | Identifies the post whose comments are listed |
| limit | Query | 25 | Controls page size for the list request |
| x-access-key | Header | your-api-key | Authenticates the request |
Captured List Comments contract only; other actions have no captured input contract in supplied source and are not specified here.
| Field | Type in example | Purpose |
|---|---|---|
| success | boolean | Indicates whether the list request succeeded |
| comments | array | Comment items for the requested post |
| comments[].id | string | Comment identifier |
| comments[].text | string | Comment text |
| comments[].author.id | string | Author identifier |
| comments[].author.name | string | Author display name |
| comments[].timestamp | string | Comment timestamp in ISO format in example |
| comments[].likeCount | number | Like count for the comment |
| comments[].hidden | boolean | Whether the comment is hidden |
| comments[].replies | array | First-level replies to the comment |
| nextCursor | string | Cursor indicating a further page; continuation parameter not captured |
Field names and nesting preserved from captured 202 response example; types inferred only from example values. Cursor continuation parameter not captured.
| Criterion | Hide and Unhide | Delete Comments |
|---|---|---|
| Reversibility | Reversible: hidden true hides, hidden false restores | Permanent removal |
| Best for | Spam moderation pending review | Comments that should be removed for good |
| Identifier | Comment ID from list response | Comment ID from list response |
| Record retention | Preserves the comment record for later review | Removes the comment record |
Decision criteria derived from source FAQ and capability descriptions; no additional contract invented.
| Check | Expected result | Action if check fails |
|---|---|---|
| Account type | Business or Creator account | Do not offer comment management for personal accounts |
| Post ownership | Post belongs to the connected account | Treat the post as not manageable under Works on Existing Posts |
| Auth header | x-access-key present | Fix the header before retrying the list request |
| Action contract | List Comments contract captured | Do not guess methods or paths for reply, hide, or delete |
Failure checks derived from source eligibility rules; no error codes invented because none were captured.
Frequently asked questions
What can I do with the Instagram Comments API?
A connected account lets you fetch a post's comments together with their first-level replies, add a new top-level comment, answer an existing comment, toggle visibility, or remove a comment entirely.
Does the Instagram Comments API work with personal accounts?
They are outside the eligible set. Comment operations are limited to professional Business or Creator accounts, so personal profiles should be excluded from these endpoints.
Do I need my own Meta developer app or App Review?
For the hosted integration described here, no separate Meta app approval step is needed on your side. That integration is described as holding the instagram_business_manage_comments permission and managing the OAuth connection, which is a narrower statement than approval for a self-built Meta app.
Can I manage comments on posts I did not publish through the API?
Yes, provided the media belongs to the account you connected. Where the post was originally published does not affect eligibility under that rule.
What is the difference between hiding and deleting an Instagram comment?
Visibility toggling can be undone: hidden set to true suppresses a comment, and hidden set to false brings it back. Removal, by contrast, is final. That reversibility makes toggling the safer first step when you are still reviewing a comment.
How much does the Instagram Comments API cost?
The source states a charge of 1 credit for each Comments API call. Fetching, answering, adding, toggling visibility, and removing are counted as distinct calls rather than as one bundled operation.
What can I build with the Instagram Comments API?
Typical fits include social tools, agency dashboards, support systems, community products, and automated workflows. In each case the product needs a way to read incoming comments, respond to people, suppress unwanted entries, and remove entries that should not remain visible.
{
"success": true,
"comments": [
{
"id": "17851234567890111",
"text": "An example comment.",
"author": {
"id": "17841400000000001",
"name": "Maria"
},
"timestamp": "2026-08-05T14:22:10Z",
"likeCount": 3,
"hidden": false,
"replies": [
{
"id": "17851234567890222",
"text": "An example comment.",
"author": {
"id": "17841400000000002",
"name": "Your Brand"
},
"timestamp": "2026-08-05T14:31:04Z",
"likeCount": 0
}
]
}
],
"nextCursor": "QVFIUlZ..."
}