Threads API (Meta) pricing: Threads post API
Is Threads API (Meta) yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
GET / v1.0/ profile_ posts Threads API (Meta)'s only call for this APIAbout this item
- Freshness. We don't know how fresh this plan's data is.
- 3 of the 4 key fields we check. Text, Media, Author.
- Nothing to pay.
- One call. You send
usernametoGET /. You can also sendv1.0/ profile_ posts fields,since,until,limitand one ofbeforeorafter. The call returns the account's posts. - Who can get it: with conditions. Keep data: with conditions. Use data: with conditions.
Threads API (Meta): Threads post API alternatives
Threads API (Meta) alternatives: every Threads post API provider ranked
We list other providers' plans closest to this plan in price per 1,000 posts.
| This planThreads API (Meta), free | lobstr.io, free | EnsembleData, free | Captapi, free | SociaVault, free | ScrapeAtlas, free | |
|---|---|---|---|---|---|---|
| $ per 1,000 posts | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Completeness | 75% | 100% | 100% | 100% | 100% | 100% |
| Billing | free | free | free | free | free | free |
| Pay | $0 | $0 | $0 | $0 | $0 | $0 |
| Enough for | not published | 100 results a month | 50 results a day | 50 pages, once | 50 pages, once | 100 pages, once |
| Freshness | unknown | live | live | live | live | unknown |
| Who can get it | anyone with a Meta app on the Threads use case and a Threads user access token holding the threads_basic and threads_profile_discovery permissions, with standard access only @meta, @threads, @instagram and @facebook can be looked up | professionals, not consumers | anyone | anyone at least 18 years old, once their email is verified | anyone | anyone at least 18 and legally able to enter the agreement, a business's account holder must be authorized to bind it |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-02.
- developers.facebook.com/docs/threads
- developers.facebook.com/docs/threads/get-started
- developers.facebook.com/docs/threads/overview
- developers.facebook.com/docs/threads/retrieve-and-discover-posts/retrieve-posts
- developers.facebook.com/documentation/threads/reference/user.md
- developers.facebook.com/terms/
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Text
- Media
- Engagement, not in the answer
- Author
| $ per 1,000 posts | $0.00 |
|---|---|
| Per | page of 100 |
| Billing | free |
| $ per 1,000 | $0.00 |
|---|
| Their pitch | Use the GET /profile_posts?username=... endpoint to look up a public profile and retrieve a paginated list of their posts on Threads. |
|---|
| Keep data | Platform Terms 3.d: "Delete all Platform Data as soon as reasonably possible in the following cases: a. When retaining the Platform Data is no longer necessary for a legitimate business purpose that is consistent with these Terms and all other applicable terms and policies, [...] c. When we request you delete the Platform Data for the protection of Users [...]" and "Update or delete Platform Data promptly after receiving a request from us or the User to do so". |
|---|---|
| Use data | Threads API overview: "You may use the Threads API to enable people to create and publish content on a person's behalf on Threads, and to display those posts within your app solely to the person who created it." Platform Terms 2.a: "You will not sell, transfer, or sublicense Platform to anyone." Platform Terms 3.a: "You will not perform, or facilitate or support others in performing, any of the following prohibited practices (collectively, “Prohibited Practices”): i. Processing Platform Data to discriminate or encourage discrimination in a manner that disadvantages people based on personal attributes [...] ii. Processing Platform Data to make eligibility determinations about people, including for housing, employment, insurance, education opportunities, credit, government benefits, or immigration status. [...] iii. Processing Platform Data to perform, facilitate, or provide tools for surveillance. [...] iv. Selling, licensing, or purchasing Platform Data. v. Processing Platform Data without valid User consent in order to build or augment user profiles for any purpose. vi. Attempting to decode, circumvent, re-identify, de-anonymize, unscramble, unencrypt, reverse hash, or reverse-engineer Platform Data that is provided to you. vii. Changing your App's core functionality or data Processing so that Users would view it as an unfamiliar or different App, or materially changing the scope of Processing of previously collected Platform Data, unless in each case you first re-submit your App and receive our approval through App Review. viii. Processing Platform Data for purposes other than the applicable permitted purposes set forth in Meta's Developer Docs." Platform Terms 3.c: "You may only share Platform Data in compliance with these Terms [...] and only in the following circumstances". |
| Pay | $0 |
|---|
| Per day | 1,000 |
|---|---|
| Batch | 1 |
| Answer | in the call |
|---|
| You send | username. Optional: fields, since, until, limit, one of before or after |
|---|---|
| Method | GET |
| Path | /v1.0/profile_posts |
| Plan | Free |
|---|---|
| Who can get it | anyone with a Meta app on the Threads use case and a Threads user access token holding the threads_basic and threads_profile_discovery permissions, with standard access only @meta, @threads, @instagram and @facebook can be looked up |
The 22 fields the plan's answer can hold
post ID, media product type, media type, media URLs, post URL, author username, text, created at, post code, thumbnail URL, carousel media, is quote post, alt text, link attachment URL, has replies, reply control, quoted post, reposted post, GIF URL, is spoiler media, text entities, topic tag