Threads Integration
Threads APP_ID and APP_SECRET Setup Guide
Prepare your Threads account, create a Meta app, find Threads app credentials, invite a tester and check your integration.
Open Meta developer app console1. Prepare your Threads account
Prepare the Threads profile you will connect and the Meta developer account that will manage the app.
- Sign in through the Threads app or threads.com and check the profile and username. Create your profile first if needed.
- Sign in to the Meta developer console above. Complete developer registration and any requested verification.
- Use an account and contact email controlled by the service owner, and confirm app admin access.
Official documentation: Get started with Threads API
2. Credentials to prepare
Supply these Threads credentials for APP_ID and APP_SECRET. User access tokens are separate and are issued after authorization.
| Handover item | Value to copy | Where to find it |
|---|---|---|
| APP_ID | Threads app ID | Use cases > Access the Threads API > Customize > Settings |
| APP_SECRET | Threads app secret from the same app | Threads app secret in the same Threads settings |
| Redirect URI | Exact HTTPS return address from your developer | Client OAuth Settings > Valid OAuth redirect URIs |
Official documentation: Configure the Threads use case
3. What to get from your developer
- Obtain HTTPS Redirect URIs for development and production, service and privacy policy URLs, and the data deletion endpoint. Do not invent addresses.
- Agree on publishing, replies, insights and other required features. Add only the permissions those features need.
- Confirm the Deauthorize callback URL and Data Deletion Requests URL with the developer implementing them.
4. Create the app and find credentials
Create a Meta developer app
Open My Apps > Create App, enter the app name and contact email, and select Access the Threads API. Supply the ownership information requested by the console.
Customize the Threads use case
Open Use cases > Access the Threads API > Customize. Check threads_basic and add agreed permissions, such as threads_content_publish for publishing.
Copy the Threads ID and secret
Open Settings for that use case and copy the complete Threads app ID and Threads app secret. The account owner completes any authentication needed to reveal the secret.
Save OAuth return addresses
Enter the developer’s HTTPS address under Client OAuth Settings > Valid OAuth redirect URIs. Check and save the Deauthorize callback URL and Data Deletion Requests URL.
Invite a Threads tester
Select Add or Remove Threads Test Users, or open App roles > Roles > Add People. Add the test Threads username with the Threads Tester role.
Official documentation: Configure the Threads use case
5. Check redirect addresses and permissions
- The saved Redirect URI and login request redirect_uri must match in protocol, domain, path and trailing slash. Distinguish development and production addresses.
- Use threads_basic for basic access and threads_content_publish for publishing. Review threads_read_replies, threads_manage_replies and threads_manage_insights for reading replies, managing replies and insights.
- Your developer implements Threads authorization and server-side token exchange. Keep APP_SECRET off the browser and check token expiration, refresh and reauthorization handling.
Official documentation: Access tokens and permissions · Long-lived tokens and refresh
5-1. API permissions and approval requirements
Before external users can connect, obtain Meta App Review approval for each permission your app uses below. threads_basic is required; add and submit other permissions for the features you offer.
| Permission | Feature | Approval requirement |
|---|---|---|
threads_basic | Basic access to profiles and posts | App Review approval required for external users |
threads_content_publish | Publish content | App Review approval required to offer publishing |
threads_read_replies | Read replies | App Review approval required to offer reply retrieval |
threads_manage_replies | Write and manage replies | App Review approval required to offer reply management |
threads_manage_insights | Read insights | App Review approval required to offer analytics |
- Add required permissions under Use cases > Access the Threads API > Customize. Adding a permission does not obtain Meta approval.
- Submit each permission your app uses through the console’s App Review or Publish review requirements. Provide the requested use-case explanation, test instructions and demonstrations, and check each approval status.
- Once all required permissions are approved, complete the app publishing requirements. Obtain user consent during authorization and verify the features using the granted token.
Official documentation: Get started with Threads API · Configure the Threads use case
6. Accept the invitation, test and publish
- Sign in with the invited Threads account. Accept the tester invitation under Settings > Account > Website permissions.
- Use your service’s Threads connection button to sign in and grant permissions. Check profile retrieval and the requested publishing, reply or insights features with your developer.
- For users without an app role, obtain App Review approval for required permissions and publish the app. Complete app details, policy URLs, review and verification requirements shown under Publish.
Official documentation: Get started with Threads API · Configure the Threads use case
7. What to send your developer
- App name and complete Threads app ID (APP_ID) and Threads app secret (APP_SECRET).
- Saved Redirect URIs, deauthorization and data deletion endpoints, development/production distinction and required permissions.
- Threads username, tester invitation acceptance, and app publishing and permission review status. Hide secrets in screenshots.
Missing settings or a failed connection?
- Credentials missing: check the Access the Threads API use case, its Settings page and your app admin role.
- Tester connection fails: check the invited Threads username, invitation acceptance and signed-in account.
- Authorization or API requests fail: check the matching Threads ID and secret, Redirect URI, granted permissions and token expiration.
Documentation checked November 22, 2026. Menu labels and available features may vary by console version and language.