Threads Search API
Keyword search over public Threads posts — query in, structured post rows out, same envelope as the rest of the Threads tag.
GET /v1/threads/search1 credit per successful request.
About this endpoint
Brand and product teams watch Threads for the same reasons they watch Instagram captions: launches, complaints, and creator chatter that never lands on a profile you already follow. DIY scrapers for threads.net age poorly, and Meta's official Threads APIs expect an approved app before you can poll search at all.
`GET /v1/threads/search` takes a required `query` string (max 512 characters after trim) and returns matching public posts under `data.posts`, with `data.query` echoed and `data.totalResults` set to the count in that response. Optional `startDate` and `endDate` use `YYYY-MM-DD`; if both are set, end must be on or after start. Set `trim=true` when you want a smaller payload. Bill from `meta.creditsCharged` and keep `meta.requestId` when a row looks wrong.
This route is free-text post search. People discovery is `GET /v1/threads/users/search`. A known handle is `GET /v1/threads/profiles/{handle}`. A known post URL is `GET /v1/threads/posts`. All share one Social Fetch API key — no Meta Threads developer app required for these public lookups.
Threads Search API FAQ
What does the Threads Search API return?
Matching public posts under data.posts, the echoed query under data.query, and data.totalResults for how many posts came back in that response. Each response uses the shared Social Fetch envelope with meta.requestId and meta.creditsCharged.
How do I call Threads keyword search?
Send GET /v1/threads/search with x-api-key and a required query parameter. Optionally add startDate, endDate, and trim. Full parameter rules and examples are in the API docs.
How much does Threads post search cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.
Can I filter Threads search by date?
Yes. startDate and endDate are optional YYYY-MM-DD filters. When both are present, endDate must be on or after startDate. Invalid calendar dates or a reversed range return HTTP 400.
Does Threads search support cursor pagination?
No. This operation returns one result page for the query (and optional date filters). There is no cursor or nextCursor parameter. Re-run with a tighter query or date window if you need a smaller set.
Is this the same as Threads user search?
No. GET /v1/threads/search finds posts by keyword. GET /v1/threads/users/search finds people. Use the Threads hub docs if your job needs both.
What does trim do on Threads search?
trim=true requests a smaller response shape when available. Use it for list UIs or agents that do not need every nested media field on the first pass.
Do I need a Meta Threads developer app?
No. You authenticate to Social Fetch with an API key. The route reads public search results; it does not act on behalf of a logged-in Threads user or require Meta app review for these lookups.