Threads API App Review: Permissions and Approval Checklist
Every Threads API permission, what each one needs to show in App Review, and a pre-submission checklist for threads_content_publish, replies, insights and keyword search.
The Threads API follows the same App Review process as Facebook and Instagram, but with its own login and its own permissions. Here’s what each needs and what reviewers look for.
The permissions
| Permission | What it does | Show in the screencast |
|---|---|---|
threads_basic | Profile and posts, required by all others | Login, then profile shown in your app |
threads_content_publish | Publish text, image, video, carousel | Publish, then the live post on Threads |
threads_read_replies | Read replies to your posts | A reply from a test account appearing in your app |
threads_manage_replies | Reply, hide, control who can reply | Reply or hide, then the result on Threads |
threads_manage_insights | Views, likes, followers | An insights screen with real numbers |
threads_keyword_search | Search public posts | A search and what the user does with results |
threads_manage_mentions | Posts that mention the account | A mention from a test account in your app |
Pre-submission checklist
- Threads tester accounts added and accepted in the Threads app
- Login uses the Threads authorization window, not Instagram or Facebook
- Every requested permission has its own captioned section in the video
- Published posts are shown live on Threads, not just a success message
- Insights demo uses an account with real activity
- Keyword search explains a user benefit (brand monitoring, customer care), not data collection
- Privacy policy mentions Threads data
- Data deletion callback works
Where Threads submissions fail
threads_keyword_search gets the most scrutiny, because it can look like surveillance. Frame it around a business finding conversations about its own brand or products, and show the action it takes: replying or flagging for support.