Fix "Threads API application does not have permission for this action"
The Threads API returned a permission error. Here are the exact scopes your app needs, how to add testers, and the easiest option: post through a scheduler that already has Threads approval.

On this page
You are trying to post to Threads from your own app or a scheduler, and the API returns an error: "application does not have permission for this action" or similar. The fix usually requires adding a permission to your app, getting it approved by Meta, and giving your app user the permission to grant it.
The short answer
- Missing scopes: Your app needs
threads_basicandthreads_content_publishto publish posts. Add them in the Threads use case in your app settings. - Standard Access vs Advanced Access: With Standard Access, only people with a role on your app (admins, developers, testers) can grant permissions. Some permissions require Advanced Access approval from Meta before anyone can grant them.
- Test users: While the app is in development, add testers as Threads Testers. A tester can grant any permission without waiting for Meta approval.
- Token from before permission was added: If you added a permission after creating your access token, the token still doesn't have it. Generate a new token after the permission exists.
- Easier option: Skip building an app. A scheduler like eksis has its own Meta app already approved for publishing. Connect your Threads profile and post from the browser or REST API without any app setup.
Permissions your app needs
The Threads API uses scopes (permissions) to control what an app can do. Here are the main ones:
| Permission | What it does | Required |
|---|---|---|
threads_basic |
Required for all Threads endpoints | Yes |
threads_content_publish |
Required for Threads publishing endpoints | Yes |
threads_manage_replies |
Required for making POST calls to reply endpoints | No |
threads_read_replies |
Required for making GET calls to reply endpoints | No |
threads_manage_insights |
Required for making GET calls to insights endpoints | No |
Your app needs both threads_basic and threads_content_publish to post. If you are writing replies, add threads_manage_replies. You ask for permissions in your app's settings under the Threads API use case.
Add a permission to your app
- Log in to the app dashboard at https://developers.facebook.com/apps.
- Pick your app, then click Use cases in the sidebar.
- Click the Threads API use case.
- Click Add next to the permission you need. Required permissions (
threads_basicandthreads_content_publish) are already added. - Click Save.
The permission now appears in your OAuth flow. Anyone who grants permission through your OAuth window can now allow it. If the permission requires Advanced Access, Meta's review is a separate step, described below.
Standard Access vs Advanced Access
Standard Access (default)
When you add a permission to your app, it is available under Standard Access. A person can grant the permission to your app if they have one of these roles on your app:
- Admin
- Developer
- Tester
- Threads Tester
While your app is in development, add testers with the Threads Tester role, and they can grant any permission immediately. This is the fastest way to test.
Advanced Access (requires Meta approval)
Some permissions need Meta's approval before anyone can grant them. Advanced Access is granted through App Review. Until then, only people with a role on your app can grant permissions.
Add testers while your app is in development
While your app is in development (before you publish it), you can add test users as Threads Testers. A tester can grant any permission without waiting for App Review.
- Open your app in the dashboard.
- Click Settings in the sidebar.
- Look for "Add or Remove Threads Test Users" and click it.
- Click Add People.
- Search for the person by email or name.
- Select Threads Testers as their role, then Assign.
Threads Testers can now log in with your app and grant any permission you request.
Tokens generated before the permission was added
If you generated an access token before adding a permission to your app, the token does not have it, even after the permission is added. Generate a new token after the permission exists in your app settings. The new token will include the permission.
Why you see this error
When the API rejects a request because the app lacks a permission, it returns error code 10 (API permission denied). This error means one of these:
- The app never asked for the permission. Add it to your use case and re-authorize.
- The permission was added after the access token was created. Generate a new token.
- The permission requires Advanced Access and it has not been approved yet. Check your app settings for the approval status.
- The user is not an admin, developer, or tester for the app. Add them as a Threads Tester if the app is in development, or wait for Advanced Access approval if the app is published.
Post to Threads without building an app
If you only want to post to your own Threads profile, you can skip app development altogether. Many schedulers, including eksis, have their own Meta app already approved for Threads publishing.
In eksis, click the + next to Channels, click Threads, and log in to the Threads profile you want to post to. You approve the same permissions (read and publish), but eksis handles the app part. Then you can schedule posts on the free plan (50 per day) or paid plans (250 per day, matching Threads' own limit). Posts go through the eksis REST API on paid plans or the MCP server on Free.
Posts to Threads through eksis go through the same Threads API, so the limits and features are the same. You just skip the app creation and review. See how to schedule Threads posts or post through the REST API.
Sources
- Meta for Developers: Threads API permissions (read November 11, 2026)
- Meta for Developers: Threads API overview (read November 11, 2026)
- Meta for Developers: Threads use case setup (read November 11, 2026)
- Meta for Developers: Graph API error handling (read November 11, 2026)
Frequently Asked Questions
What is threads_basic for?
threads_basic is a required permission that gives your app access to basic Threads data. Every Threads API endpoint needs it. It doesn't let you do anything by itself; you need threads_content_publish to post or threads_manage_replies to reply. It is always required.
Do I need to apply for App Review to use the Threads API?
Not if you are testing. While your app is in development, add yourself or testers as Threads Testers in the app settings and they can grant any permission. Once you publish your app to the public, you need App Review for each permission to be used by non-admin users, which is a longer process. If you are only posting to your own account, a scheduler like eksis saves you that step.
Why does my token not work even after I added the permission?
If you generated your token before adding the permission to your app, the token does not have it. Generate a new token after the permission is added in your app settings. The new token will have all permissions your app currently requests.
How many posts can I make a day on Threads?
Meta allows 250 posts per Threads profile in any rolling 24-hour period. On free social schedulers like eksis, you may see a lower limit (50 per day on the Free plan), but that is just the scheduler's own rule. The Threads API itself allows 250. Paid plans on eksis (Pro Eksis and Super Eksis) apply Threads' full 250-post limit.
What if Meta hasn't approved my app yet?
Advanced Access is granted through App Review. Until then, only people with a role on the app (admins, developers, testers, Threads Testers) can grant permissions. For posting to your own Threads account, you usually do not need App Review because you have a role on your own app.


