Threads user_replies API
Threads user_replies data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.
- 1 documented endpoints
- GET /v1/threads/users/{username}/replies
Contract summary (English): List Threads user replies (capability threads.user_replies)
- Normalized response entity
- threads/user_replies
- capability
- threads.user_replies
Every response also carries freshness (cache / default / live) and billing metadata.
Use cases
- Monitor what a {{platform}} account publishes, in order, with normalized per-item metrics.
- Detect new activity when scheduled jobs re-query the feed — ideal for alerting and digest workflows.
- Benchmark publishing cadence and engagement across accounts with comparable, structured output.
Response fields
Threads threads.user_replies response (normalized envelope)
Response envelope of the /v1/threads threads.user_replies capability. Cursor is opaque and platform-independent; page size follows the request's `limit` parameter (1..100, default 20).
| Field | Type | Required | Description |
|---|---|---|---|
| data | comment[] | Required | — |
| next_cursor | string | null | Required | Opaque pagination cursor; null when the list is exhausted. |
| meta.request_id | string | Required | — |
| meta.freshness.mode | cache | default | live | Required | — |
| meta.freshness.age_seconds | integer | null | Optional | — |
| meta.freshness.source_layer | cache | db | upstream | Required | — |
| meta.freshness.stale | boolean | Optional | — |
| meta.billing.cache_hit | boolean | Required | — |
| meta.billing.amount_credits | integer | Required | Credits actually charged for this request (the settlement unit; 1 credit = $0.0001, permanent). |
Field notes are shown in the contract's original English.
Response meta
| Field | Type | Required | Description |
|---|---|---|---|
| mode | cache | default | live | Required | Effective mode after merging param > max_age > source policy (D-004). |
| age_seconds | integer | null | Optional | Age of served data; null when unknown. |
| source_layer | cache | db | upstream | Required | Which layer served the response (PRD §10). |
| stale | boolean | Optional | True when stale data was served under stale_if_error / SWR (D-004). |
| billing.amount_credits | integer | Required | Micro-USD (1e-6 USD) actually charged for this request. |
| billing.cache_hit | boolean | Required | — |
Field notes are shown in the contract's original English.
Example request & response
/v1/threads/users/{username}/repliescurl -H "Authorization: Bearer $MESHDATA_API_KEY" \
"https://api.fetchpi.com/v1/threads/users/newdev/replies"{
"data": [
{
"id": "7458000000003001",
"platform": "threads",
"type": "comment",
"post_id": "7459000000001001",
"author": {
"id": "7455000200",
"username": "threads_fan",
"display_name": null,
"verified": false
},
"text": "讲得清楚,赞。",
"created_at": "2026-09-16T12:01:22Z",
"metrics": {
"likes": 96,
"replies": 3
},
"fetched_at": "2026-09-21T09:00:00Z"
}
],
"next_cursor": null,
"meta": {
"request_id": "req_01HTXQ8Z9HTQ",
"freshness": {
"mode": "default",
"age_seconds": 0,
"source_layer": "upstream",
"stale": false
},
"billing": {
"amount_credits": 200,
"cache_hit": false
}
}
}Free demo
Create a free account, grab an API key and call this endpoint from the browser-based Playground.
Try it in the PlaygroundParameter tables, error codes and response semantics for this endpoint live in the API documentation.
Open the endpoint referenceFrequently asked questions
Can I poll the feed on a schedule?
Yes — the endpoint is a plain REST call, so any scheduler can re-query it. Use the freshness parameters to control how current each answer is and how it is billed.
Can I try this endpoint for free?
Yes — register an account, grab an API key and call it from the Playground in the console.
How is the user_replies capability billed?
Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.
Pricing
Per-request credit billing with cache/live freshness options — current prices live on the pricing page.