GET /v1/threads/post/comments
Threads Post Comments API
Returns the replies Threads bundles with a post, usually about 20. Send limit above 25 (up to 50) to collect more first-level replies from a second source.
10–100 credits, metered · single call · failed calls free · 10 free calls to start
curl "https://api.insightsocial.app/v1/threads/post/comments?url=https%3A%2F%2Fwww.threads.com%2F%40zuck%2Fpost%2FDZpPDXbCeTt" \-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
When to use it
Use it to read the reaction under a post you already have the URL for. It is one window with no cursor. Set limit above 25 when the bundled window is not enough.
Parameters
Query parameters for GET /v1/threads/post/comments. Send your key in the x-api-key header.
| Name | Required | Description |
|---|---|---|
| url | Yes | Full URL of the Threads post whose replies you want, for example https://www.threads.com/@zuck/post/DZpPDXbCeTt. Both threads.com and threads.net are accepted. |
| trim | No | Ask for a stripped record. This is a real shape change, not just less whitespace: a trimmed row carries only the id, text, shortcode, like count, timestamp and author, so media, reply count, share count, view count, topic tag, pinned flag and quoted post all come back null. Ignored when limit is above 25, because the deeper source has no trimmed mode. |
| limit | No | How many replies to collect, 1 to 50. Leave it off, or send 25 or less, and nothing changes: you get the bundled window. Threads publishes only part of a large conversation without a login, so a post declaring a thousand replies will still return about 50. |
Response fields
The same unified schema every platform returns, so code written for Threads works on the other eight. A field the platform did not provide is null and listed in unavailable.
| Field | Type | Notes |
|---|---|---|
| id | string | An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53. |
| url | string | null | |
| parent_id | string | null | An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53. |
| post_id | string | null | An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53. |
| text | string | null | |
| author.id | string | null | |
| author.username | string | null | |
| author.display_name | string | null | |
| author.avatar_url | string | null | |
| author.verified | boolean | null | |
| engagement.likes | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.replies | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| flags.pinned | boolean | null | |
| flags.deleted | boolean | |
| published_at | string | null | ISO-8601 timestamp in UTC, ending in Z. |
| language | string | null | The content's language as the platform states it, e.g. en, pt-BR. Detected languages come later (§7.1). |
| replies | array | null | |
| ext | object | null | Platform-specific fields, snake_case. |
Every field, error and example is in the Threads Post Comments API reference.
How much does the Threads Post Comments API cost?
Metered: 10–100 credits a call. The ceiling is reserved when the call starts and you are charged what it actually read.
Failed calls are free
A call that errors or finds nothing costs 0 credits.
Know the price first
Add dry_run=1 and the response quotes the call without making it. Nothing is charged.
One balance
API calls and Chrome extension exports share the same credits, on the free plan too.
Threads Post Comments API: frequently asked questions
Send GET /v1/threads/post/comments with the url parameter and your key in the x-api-key header. Returns the replies Threads bundles with a post, usually about 20. Send limit above 25 (up to 50) to collect more first-level replies from a second source.
Metered: 10–100 credits a call. The ceiling is reserved when the call starts and you are charged what it actually read. A call that errors or finds nothing costs 0 credits, and an answer from the shared cache costs 2. Pro's 10,000 monthly credits cover about 1,000 calls at 10 credits each. Add dry_run=1 to see the price of a call without making it.
No. There is no Threads app, OAuth flow or app review. One InsightSocial API key works for this endpoint and every other platform, and your first 10 calls priced at 100 credits or less are free.
One call returns the comments in the data object of the standard response envelope. Fields the platform did not provide are listed in unavailable, so a null there means unknown, not zero.
You get an error or an empty result, and it costs 0 credits. The API reads public Threads data only, so private accounts and deleted content come back as not found rather than as partial data.
Yes. Add the hosted MCP server at https://api.insightsocial.app/mcp to your AI app and sign in. The assistant finds this endpoint by name, shows its price and calls it with your credits.