/v1/detail"platform": "threads"Threads Detail API
One post by ID or link.
Get any public Threads post by ID or link and get back text, author, likes, comment count, views and publish time, as JSON over HTTP or from your AI client over MCP. A call to the Threads Detail API costs 2 credits ($0.004 to $0.0067 depending on the pack), failed calls are free, and the response has the same format as every other call.
Last updated:
What you get from the Threads Detail API.
From a recorded answer.
A recorded call returned the object below, field by field. Names and text are removed from the sample; the numbers are as recorded.
Lighter for your AI: the same recorded data (1 item) is about 83,785 tokens as the platform's raw JSON and about 366 as this interface returns it, 99% fewer (measured 2026-11-06). How it was measured
| Field | In the recorded answer |
|---|---|
| url | removed from the sample |
| format | text |
| title | null: Threads cannot give it |
| text | removed from the sample |
| published_at | 2026-09-04T15:46:28.000Z |
| author.id | removed from the sample |
| author.username | removed from the sample |
| author.name | removed from the sample |
| author.verified | true |
| author.followers | null: Threads cannot give it |
| metrics.likes | 1,466 |
| metrics.comments | 43 |
| metrics.shares | 9 |
| metrics.collects | null: Threads cannot give it |
| metrics.views | 37,509 |
| metrics.reposts | 111 |
| images | empty list |
| hashtags | 1 entry |
| is_pinned | false |
2 credits a call (≈ $0.004–$0.0067): about 1,500 calls for $10.
Threads Detail API: request and response
curl https://socialtoai.app/v1/detail \ -H "Authorization: Bearer $SOCIALTOAI_API_KEY" \ -H "Idempotency-Key: $(uuidgen)" \ -H "Content-Type: application/json" \ -d '{ "platform": "threads", "id": "Dc3vb5DES3i" }'import osimport uuidimport requestsresponse = requests.post( "https://socialtoai.app/v1/detail", headers={ "Authorization": f"Bearer {os.environ['SOCIALTOAI_API_KEY']}", # A new key for each request; the same one again retries it without paying twice. "Idempotency-Key": str(uuid.uuid4()), }, json={ "platform": "threads", "id": "Dc3vb5DES3i", },)print(response.json())# Connected over MCP? Ask in plain words.Read this Threads post: Dc3vb5DES3i# Your AI calls the detail tool with:{ "platform": "threads", "id": "Dc3vb5DES3i"}{ "platform": "threads", "status": "ok", "items": [ { "platform": "threads", "id": "…", "ref": "…", "approx": [], "extra": {}, "type": "content", "url": "https://example.com/…", "format": "text", "title": null, "text": "…", "published_at": "2026-09-04T15:46:28.000Z", "author": { "id": "…", "username": "…", "name": "…", "verified": true, "followers": null }, "metrics": { "likes": 1466, "comments": 43, "shares": 9, "collects": null, "views": 37509, "reposts": 111 }, "images": [], "hashtags": ["…"], "is_pinned": false } ], "unavailable": ["title", "author.followers", "metrics.collects"], "cost_credits": 2}nullviews 37,509reposts 111Names and text were removed from the sample; the numbers are as recorded.
Threads Detail API parameters.
3 parameters, 1 required.
Send them as a JSON body with POST. Your key goes in the Authorization header, never in the URL.
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| platform | string | Required | — | Always "threads" on this page. |
| id | string | One of these | — | Post code: the last segment of the post's link |
| url | string | One of these | — | Link to the post, written threads.com/@handle/post/code or threads.com/t/code |
Where to get what you send.
idPost code: the last segment of the post's link (e.g. Dc3vb5DES3i)
Every item these return carries its ref; send it as it is:
searchThreads Search APIuser_postsThreads User Posts API
Or send the web link: the url field of the same items.
Threads Detail API response fields.
What Threads cannot give is marked.
| Field | Type | Meaning |
|---|---|---|
| items[].extra | object | What the platform gives of this item beyond the fields below, under the platform's own names (an IP location, a uid, a showcase flag); the interface's extra_fields says what each is. Empty when there is nothing more. Of a comment or a review, never who wrote it. |
| items[].url | string | A link that opens the item. |
| items[].format | string | video, image, text or article. |
| items[].title | stringalways null | The title. |
| items[].text | string | The body text or caption. |
| items[].published_at | string | When it was published, ISO 8601 in UTC. |
| items[].author.id | string | The author's account ID. |
| items[].author.username | string | The author's handle. |
| items[].author.name | string | The author's display name. |
| items[].author.verified | boolean | Whether the author is verified. |
| items[].author.followers | integeralways null | The author's follower count. |
| items[].metrics.likes | integer | Likes. |
| items[].metrics.comments | integer | Comments. |
| items[].metrics.shares | integer | Shares. |
| items[].metrics.collects | integeralways null | Saves. |
| items[].metrics.views | integer | Views or plays. |
| items[].metrics.reposts | integer | Reposts. |
| items[].images | string[] | Image addresses. |
| items[].hashtags | string[] | Hashtags, without the #. |
| items[].is_pinned | boolean | Whether the author pinned it. |
nullFields Threads cannot giveRead null as “Threads did not give this”, not as zero. These are always null on this call:
titleThe title.author.followersThe author's follower count.metrics.collectsSaves.
Compared with the X (Twitter) Detail API, this call also gives shares but does not give author followers or saves.
Every item also has platform, id, ref, approx and type; the response around the items is the same on every call. Response format
Threads Detail API: paging and billing.
5 calls per second per key, 20 after a purchase; going over is not charged. Rate limits
A failed call costs 0 credits and is never retried on its own. Error codes
Interface last tested: 2026-10-17. Each call reads from the platform, and fetched_at in the answer is when it was read. The same request sent again with the same key within 5 minutes is a replay (replayed: true): 0 credits, and the answer as first read.
Once connected over MCP, these questions use the Threads Detail API.
Read this Threads post: Dc3vb5DES3i
2 creditsdetail {"platform":"threads","id":"Dc3vb5DES3i"}Search Threads for posts about "nasa", then for the first 3: read this Threads post.
8 creditssearch {"platform":"threads","query":"nasa"}detail {"platform":"threads","id":"<ref>"} × 3
Give this to your AI.
Copy it into Claude or ChatGPT.
How to connectUse the SocialToAI MCP server (https://socialtoai.app/mcp) for this: Read this Threads post: Dc3vb5DES3iCall the detail tool with {"platform":"threads","id":"Dc3vb5DES3i"}. Needed: id, url.For several, call it once for each: 2 credits each.Before you start, work out how many credits it will take in all and ask me; call it only after I agree.If SocialToAI is not connected yet, tell me how to connect it; never ask me to paste a key into the chat.Answer with a link to every item you used, and tell me how many credits it cost.Paste it into a chat once SocialToAI is connected over MCP. There is no key in it: Claude and ChatGPT sign in, other clients send a key in a header.
These ready-made tools call it when they run.
batch-statsOne row per link with its numbers as they are now. Links that no longer work are marked
The same call on other platforms.
All platforms and prices/v1/detail{ "platform": "threads", "id": "Dc3vb5DES3i" }2 creditsper callRead next.
What its own API allows, who can use it and what it costs, with sources.
Let your AI read Threads.