Threads — how to connect

Posts text and image threads to a personal Threads profile via the Threads API (500 char limit, up to 10 images per post). Connect with OAuth after adding your Threads app's App ID and secret below. Note: the threads_content_publish scope requires Meta App Review for non-test users.

The Threads integration uses Threads' own OAuth (not Facebook Login) to publish text and image threads to a personal Threads profile. You need one app-level App ID + App secret (registered once per workspace), then each account connects by clicking Connect and approving the OAuth prompt.

Before you start

A Threads profile (personal, not a Page) — Threads uses its own OAuth, not Facebook Login, so there's nothing to link via a Facebook Page or Business Manager
A Meta developer app with the Threads use case added (Business app type), giving you the App ID and App secret this integration asks for (THREADS_APP_ID / THREADS_APP_SECRET)
For anyone other than the app's own registered test users: Meta Tech Provider verification (~1 week) plus a passed App Review for the threads_content_publish scope (screencast of the exact publish flow) — without this, publish calls will only work for accounts added as Threads testers on the app
Redirect URI for the app registered exactly matching what this tool sends during connect, since Threads OAuth validates it strictly

Step by step

1
Create a Meta developer app
Go to the Meta for Developers dashboard, click Create App, and choose the "Access the Threads API" use case.
Open
2
Copy the Threads App ID and App secret
In App Dashboard > Settings, copy the "Threads app ID" and "Threads app secret" values — these are the two values this app asks for as App ID and App secret.
Open
3
Add the Threads API use case and content-publish permission
Under Use cases, select the Threads API use case and click Add next to the threads_content_publish permission (threads_basic is included by default).
4
Configure the OAuth redirect URI
In Settings > Client OAuth Settings, add this app's redirect URI to the Valid OAuth Redirect URIs list and save.
5
Enter App ID and App secret in this app, then click Connect
Paste the App ID into the App ID field and the App secret into the App secret field, save, then click Connect to run the Threads OAuth flow and approve access for the profile you want to publish as.
6
Add yourself as a Threads tester if the app isn't approved yet
Under Use cases > Threads API > Add or Remove Threads Test Users, add the profile as a Threads Tester so it can authorize before App Review is complete.
Open

App keys (set once in Settings)

App ID (client ID)
Meta app with the "Access the Threads API" use case → App Dashboard → Settings → Basic → "Threads app ID". This is Threads' own OAuth — a plain Facebook app is not enough.
App secret (client secret)secret
Same page → "Threads app secret". Not your Facebook app secret. Register this tool's redirect URI under Settings → Client OAuth settings.

Good to know

threads_content_publish requires Meta App Review before it works for non-tester accounts — until then only accounts added as Threads Testers can connect and publish.
Text posts are capped at 500 characters; media containers support up to 10 images or 1 video per post.
Publishing is rate-limited to roughly 250 posts per 24 hours per account.
Threads uses its own OAuth endpoints (threads.net / graph.threads.net), not the standard Facebook Login flow, so a Facebook app alone is not sufficient — the app must have the Threads API use case added.

Troubleshooting

Connect succeeds but publishing fails with a permission/scope error (or works only for you, not clients): threads_content_publish is review-gated — until Meta approves it (or the target account is added as a Threads tester on your app), only test users can publish. Submit App Review with a screencast, or add the account under App Roles > Testers for local/dev use.
Posts stop publishing after ~60 days with an expired/invalid token error: The OAuth exchange returns a token that needs to be upgraded to a long-lived token (60-day expiry) and refreshed before it lapses; re-run Connect for that account to get a fresh token if it already expired — there is no silent auto-refresh in this adapter.
Publish returns a 4xx from the threads_publish step even though the container (step A) was created fine: This is almost always a rate limit (250 published posts per rolling 24h per account) or the container not being ready yet; back off and retry the threads_publish call after a short delay rather than immediately re-creating a new container.
Image/video posts fail with a media fetch error while text-only posts work: Threads fetches media by URL server-side, so the image_url/video_url must be a public, directly-fetchable HTTPS URL (no auth wall) matching a supported aspect ratio (1:1, 4:5, or 1.91:1); a private or expiring signed URL will fail the container-creation step.

Threads developer docs

Before you start

A Threads profile (personal, not a Page) — Threads uses its own OAuth, not Facebook Login, so there's nothing to link via a Facebook Page or Business Manager

A Meta developer app with the Threads use case added (Business app type), giving you the App ID and App secret this integration asks for (THREADS_APP_ID / THREADS_APP_SECRET)

For anyone other than the app's own registered test users: Meta Tech Provider verification (~1 week) plus a passed App Review for the threads_content_publish scope (screencast of the exact publish flow) — without this, publish calls will only work for accounts added as Threads testers on the app

Redirect URI for the app registered exactly matching what this tool sends during connect, since Threads OAuth validates it strictly

Step by step

Create a Meta developer app

Go to the Meta for Developers dashboard, click Create App, and choose the "Access the Threads API" use case.

Open

Copy the Threads App ID and App secret

In App Dashboard > Settings, copy the "Threads app ID" and "Threads app secret" values — these are the two values this app asks for as App ID and App secret.

Open

Add the Threads API use case and content-publish permission

Under Use cases, select the Threads API use case and click Add next to the threads_content_publish permission (threads_basic is included by default).

Configure the OAuth redirect URI

In Settings > Client OAuth Settings, add this app's redirect URI to the Valid OAuth Redirect URIs list and save.

Enter App ID and App secret in this app, then click Connect

Paste the App ID into the App ID field and the App secret into the App secret field, save, then click Connect to run the Threads OAuth flow and approve access for the profile you want to publish as.

Add yourself as a Threads tester if the app isn't approved yet

Under Use cases > Threads API > Add or Remove Threads Test Users, add the profile as a Threads Tester so it can authorize before App Review is complete.

Open

App keys (set once in Settings)

App ID (client ID)

Meta app with the "Access the Threads API" use case → App Dashboard → Settings → Basic → "Threads app ID". This is Threads' own OAuth — a plain Facebook app is not enough.

App secret (client secret)secret

Same page → "Threads app secret". Not your Facebook app secret. Register this tool's redirect URI under Settings → Client OAuth settings.

Good to know

threads_content_publish requires Meta App Review before it works for non-tester accounts — until then only accounts added as Threads Testers can connect and publish.

Text posts are capped at 500 characters; media containers support up to 10 images or 1 video per post.

Publishing is rate-limited to roughly 250 posts per 24 hours per account.

Threads uses its own OAuth endpoints (threads.net / graph.threads.net), not the standard Facebook Login flow, so a Facebook app alone is not sufficient — the app must have the Threads API use case added.

Troubleshooting

Connect succeeds but publishing fails with a permission/scope error (or works only for you, not clients)

threads_content_publish is review-gated — until Meta approves it (or the target account is added as a Threads tester on your app), only test users can publish. Submit App Review with a screencast, or add the account under App Roles > Testers for local/dev use.

Posts stop publishing after ~60 days with an expired/invalid token error

The OAuth exchange returns a token that needs to be upgraded to a long-lived token (60-day expiry) and refreshed before it lapses; re-run Connect for that account to get a fresh token if it already expired — there is no silent auto-refresh in this adapter.

Publish returns a 4xx from the threads_publish step even though the container (step A) was created fine

This is almost always a rate limit (250 published posts per rolling 24h per account) or the container not being ready yet; back off and retry the threads_publish call after a short delay rather than immediately re-creating a new container.

Image/video posts fail with a media fetch error while text-only posts work

Threads fetches media by URL server-side, so the image_url/video_url must be a public, directly-fetchable HTTPS URL (no auth wall) matching a supported aspect ratio (1:1, 4:5, or 1.91:1); a private or expiring signed URL will fail the container-creation step.