Threads reference
Threads API guide
Find public Threads posts or accounts, resolve a selected author and inspect a post discussion. Account search and post search answer different questions.
Quickstart
Start with Threads
Find public Threads posts or accounts, resolve a selected author and inspect a post discussion. Account search and post search answer different questions.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Find relevant posts
Retain returned post URLs and author handles. The search contract does not declare cursor paging; do not keep inventing page numbers. Parameters and current cost →
curl "https://www.monocrawl.com/v1/threads/search?query=developer%20tools" \ -H "x-api-key: mn_your_key_here"
2. Resolve an author
Replace this illustrative handle with an author from your search results. Resolve identity before aggregating posts by display name. Parameters and current cost →
curl "https://www.monocrawl.com/v1/threads/profile?handle=zuck" \ -H "x-api-key: mn_your_key_here"
3. Inspect a discussion
Use a returned post URL and preserve any returned comment continuation and relationship fields. Parameters and current cost →
curl "https://www.monocrawl.com/v1/threads/post-comments?url=https%3A%2F%2Fwww.threads.com%2F%40zuck%2Fpost%2FDZpPDXbCeTt" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| Search window | Only use the declared start_date and end_date inputs. Search and user-posts do not declare page or cursor controls. Endpoint reference → |
| Discussion paging | Preserve the post URL when following the comment cursor; absence of continuation is not proof of exhaustive history. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| Discover accounts | search-users | Search for users rather than treating post authors as a complete account directory. |
| Read one account feed | user-posts | A bounded account read. Do not assume the same continuation as post comments. |
| Resolve one post | post | Use its source URL, and distinguish the post author from quoted or reposted content. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Posts and media
Comments and replies
Accounts and audiences
Search and discovery
Operations
Threads
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Threads
6 operationsElsewhere
The same registry, other shapes
- Threads overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=threads— the same rows to your code at runtime, for 0 credits.