Threads User Posts
https://api.sandbase.ai/v1/api/threads/web/user-postsReturns a list of posts from a specified Threads account. Accepts a user identifier and an optional pagination cursor to retrieve subsequent pages of data.
- Price
- $0.003USD / callFirst 100 calls per day free (shared per organization)
- Method
- POST
- Response
- JSON
- Parameters
- 1 required · 1 optional
Try the model
Playground
[
{
"data": null
}
]Examples
Select an example to load its inputs and result into the playground.
Model card
Specifications
Pricing
- Base price
- $0.003 / run
- Daily free calls
- First 100 calls per day free (shared per organization)
Request & response
- Method
- POST
- Request body
- application/json
- Response
- application/json
- Execution
- sync
Parameters
- user_id
- string · required
- end_cursor
- string · optional
Access
- Provider
- Threads
- API
- Platform API
- Base URL
- https://api.sandbase.ai
- Endpoint
- /v1/api/threads/web/user-posts
- Authentication
- Bearer API key
API README
Threads User Posts API
Fetch posts for a target account using user_id. You can navigate multi-page timelines by providing an end_cursor.
Use cases
- Retrieve historical posts from a specific Threads profile.
- Page through account activity feeds using pagination tokens.
- Collect post content and metadata for social media monitoring.
Request
curl -X POST "https://api.sandbase.ai/v1/api/threads/web/user-posts" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"user_id": "<user_id>"}'
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
user_id | string | Yes | User ID, for example: 63625256886, can be obtained from user profile API |
end_cursor | string | No | Pagination cursor (optional), used to get next page data |
Notes
user_idcan be obtained from the user profile API.end_cursoris used to navigate to the next page of results.
Related APIs
- Threads Post Detail: Returns detailed information for a specific Threads post using its numeric ID.
- Threads Post Detail (V2): Returns detailed information for a specific Threads post.
- Threads Profile Search: Searches Threads user profiles based on a specified text query string.
Start building
Send your first request
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/threads/web/user-posts" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"user_id": "example"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Explore more
Related APIs
| API | Price | Response | Released |
|---|---|---|---|
Threads User PostsThis API Threads | $0.003 per call | JSON | Jul 31, 2026 |
Threads | $0.003 per call | JSON | Jul 31, 2026 |
Threads | $0.003 per call | JSON | Jul 31, 2026 |
Threads | $0.003 per call | JSON | Jul 31, 2026 |
Threads | $0.003 per call | JSON | Jul 31, 2026 |
Threads | $0.003 per call | JSON | Jul 31, 2026 |
Questions
FAQ
How do I use the Threads User Posts API?
Send a POST request to https://api.sandbase.ai/v1/api/threads/web/user-posts with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
How much does the Threads User Posts API cost?
$0.003 per call. Every organization gets 100 free calls per UTC day, shared across eligible SandBase APIs including this one; after that each call is billed at this price from your SandBase balance. There is no subscription.
What parameters does the Threads User Posts API accept?
Required: user_id (string). Optional: end_cursor (string). The Parameters table and the Playground on this page list every field.
What does the Threads User Posts API return?
A JSON response returned in the same HTTP request (synchronous).
Do I need a Threads developer account or API key?
No. Threads User Posts runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Threads API access separately.
