5 APIs from 2 credits per call.
The APIs
Prices are in credits, per call, and the same on every plan. A call that fails costs nothing.
More platforms. Same key, same credits.
The official API
Meta’s Threads API lets an app publish to Threads for the people who sign in to it, manage their replies and read their insights, with an OAuth token for each user. Searching public posts and looking up other profiles need permissions that Meta grants through App Review.
As of 2026-11-14, Meta describes the Threads API as a way to publish content on a person’s behalf and to show those posts in your app solely to the person who created them.
Read on Threads API overview (developers.facebook.com) (opens in a new tab)You need a Meta app with the Threads use case and its Threads app ID and secret. People without a role on your app can only grant permissions that passed App Review, and the app must be published.
Read on Get started with the Threads API (developers.facebook.com) (opens in a new tab)Until the threads_keyword_search permission is approved, keyword search covers only the signed-in user’s own posts. A user can send at most 2,200 search queries in a rolling 24 hours, shared across every app (as of 2026-11-14).
Read on Threads keyword and topic tag search (developers.facebook.com) (opens in a new tab)With standard access, profile discovery can look up only @meta, @threads, @instagram and @facebook. Approved apps can look up public profiles with at least 100 followers, up to 1,000 requests per user per 24 hours.
Read on Threads profiles (developers.facebook.com) (opens in a new tab)Each Threads profile can publish 250 posts and 1,000 replies through the API in a rolling 24 hours, and text posts are limited to 500 characters (as of 2026-11-14).
Read on Threads API overview (developers.facebook.com) (opens in a new tab)Short-lived user tokens last 1 hour and long-lived tokens 60 days, and a long-lived token can be refreshed before it expires.
Read on Get started with the Threads API (developers.facebook.com) (opens in a new tab)Checked against Meta’s developer docs (opens in a new tab).
Yes. Meta’s Threads API publishes posts, manages replies and reads insights for accounts that sign in to your app with OAuth. Public search and lookups of other profiles need permissions approved through Meta App Review.
Meta’s Threads docs set rate limits per app and user rather than a price per call. The cost is the setup: a Meta app, OAuth for every user, and App Review for any permission used by people without a role on your app.
Only after Meta approves the threads_keyword_search permission; before that, search returns the signed-in user’s own posts. Approved apps get keyword and topic tag search, limited to 2,200 queries per user in a rolling 24 hours.
Create a Meta app with the Threads use case, send users through the Threads authorization window, and exchange the code it returns for a short-lived token. Swap that for a long-lived token, which lasts 60 days and can be refreshed.
Yes, with PrimaryAPI. Its Threads APIs return public profiles, single posts, a user’s latest posts and keyword search results as JSON with your PrimaryAPI key, and you only pay when data comes back.
Yes. Through PrimaryAPI’s MCP server or its SKILL.md an agent can find the Threads APIs and call them with its key, and the spend limit on that key keeps its costs where you set them.
Create an account, buy credits when you need them, and call every Threads API with the same key.