Threads scraper API

Meta's Threads API is designed around accounts that authorize your app. The InsightSocial API reads any public profile, its posts and the replies under them with one key.

Yes. /v1/threads/search returns posts for a keyword and /v1/threads/search/users returns accounts.

A profile is 10 credits. Posts, replies and search are priced per endpoint and listed before you call. Calls that fail or find nothing are free.

Yes. /v1/threads/search takes a keyword with start_date and end_date and returns the matching public posts with author, text, language and engagement counts. The API returns the posts as Threads serves them; deciding which ones are really about your brand, and their sentiment, happens on your side with keyword rules or your own model.

/v1/threads/user/posts returns an account's most recent posts, usually about 15. Set limit up to 50 to read further back, or since= to stop at a date.

/v1/threads/post/comments returns the replies Threads bundles with a post, usually about 20, in one window with no cursor. Set limit above 25, up to 50, to collect more first-level replies.

No. There is no Threads app, OAuth flow or review. One API key in the x-api-key header works for Threads and the other 24 platforms.

Yes. Your first 10 calls priced at 100 credits or less are free, and the free plan includes 500 credits every month. No credit card is needed to get a key.

60 requests a minute and 10 requests in flight at once, per API key. Going over either returns a 429 with a Retry-After header, and a rejected request costs nothing. There is no daily quota: past those two limits, your credit balance is what bounds volume.

List endpoints return rows in data.items and a pagination object with next_cursor and has_more. Send next_cursor back unchanged as the cursor parameter for the next page, and stop when has_more is false. A handful of endpoints page with their own parameter instead; their reference pages name it.

No. A call that errors or finds nothing costs 0 credits. A live fetch costs the endpoint's price, or for a metered endpoint what it actually read. An answer served from the shared cache costs 2 credits. Repeating a call is charged like the first time, because it can return newer data.

A call fetches live unless a recent copy is in the shared cache, and every response says which with the cached field; a cached answer costs 2 credits. Add fresh=1 or send Cache-Control: no-cache to skip the cache; that call is charged at the normal price.

Collecting publicly available data is generally treated differently from accessing private data, but the answer depends on your jurisdiction, Threads's terms and what you do with personal data afterwards. The API reads public data only. Talk to a lawyer for anything commercial.