List recent posts by a Threads account. The upstream returns up to 25 posts per request. Supplying user_id removes the handle-resolution lookup and makes the request a single upstream lookup; without it, a cold cache resolves the handle first. Responses cover page 1 only.
Run this endpoint
Endpoint
Parameters
Start with the required fields, then add optional filters only when your use case needs them.
Runnable path
1 required parameter needed before sending a request.
1 optional filter available.
string
Required
Threads handle without the leading @.
natgeo
integer
Optional
Optional numeric primary key. Supplying it skips the handle-resolution lookup.
1234567890
Response Schema
Example response fields are illustrative; inspect the JSON before integrating.
Example response fields
Scan these fields before integrating.
meta
posts
search_parameters
{
"meta": {
"attempts": 1,
"duration_ms": 820,
"endpoint_family": "threads_user_posts"
},
"posts": [],
"search_parameters": {
"engine": "threads_user_posts",
"username": "natgeo",
"upstream_lookups": 1
}
}Errors
Handle these documented responses before retrying or showing customer-facing failures.
Not Found
Returned, and not billed, when the handle, post code or hashtag does not exist or is not publicly available.
Validation Error
Returned, and not billed, when a parameter is missing or outside its allowed range.
Service Unavailable
A retryable, non-billable failure. The upstream returned a degraded or unreadable response, or the request budget ran out.
Generate Code with AI
Copy a ready-made prompt with all the endpoint details, parameters, and example responses. Paste it into ChatGPT, Claude, or any AI assistant to instantly generate working code.
Try It Live
Test this endpoint in our interactive playground with real data.