SocialOAuth 2.0 — Threads app ID + secretConfirm pricing before publishing
Threads
Publish text and image posts to Threads.
AProvider definition
- Provider
- Threads
- What it does
- Publish text and image posts to Threads.
- Why we need it
- Publish text and image posts to Threads.
- Used in
- Social (publish)
- Official site
- https://developers.facebook.com/docs/threads
BAccount requirements
- Account type
- Meta developer app with the Threads use case
- Prerequisites
- Threads profile
CConnection method
- Authentication
- OAuth 2.0 — Threads app ID + secret
- Where to enter it
- Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
- Per brand: App → Integrations → Connected accountsAnyone who manages the brand. Each brand connects its own accounts.
Setup steps
- 1developers.facebook.com → Create app → choose the “Access the Threads API” use case.
- 2Add the redirect callback URL shown below.
- 3Copy the Threads app ID and secret, enter them, then connect a Threads account.
DPermissions & API scopes
| Scope / permission | Why it's needed | Requested by |
|---|---|---|
| threads_basic | Read the profile. | Threads connection |
| threads_content_publish | Publish posts. | Threads connection |
| threads_manage_replies | Moderate replies. | Threads connection |
| threads_read_replies | Read replies for the inbox. | Threads connection |
| threads_manage_insights | Read post insights. | Threads connection |
This list is generated from the scopes the application's code requests.
EFree vs paid
- Free account / free API access
- Yes — no fee for API access.
- Card or billing account required?
- No.
- Paid plan / costs
- None.
- Quota and usage limits
- Per-profile posting limits per 24 hours.
Not yet verified. Confirm on the provider's official pricing page before publishing.
FSetup screenshots
Capture each step with real values masked. Save images as public/docs/integrations/threads/1.png … 10.png and they appear here automatically.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Screenshot to add3. Project / app creationCreating the app or project used for this integration.
- Screenshot to add4. API enablementThe API or product enabled for the project.
- Screenshot to add5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Screenshot to add7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe green Test result or the connected account listed.
GApplication configuration
Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.
| Field | Required | Example / default | Notes |
|---|---|---|---|
| Threads app ID | Yes | — | |
| Threads app secret | Yes | •••••••• | Stored encrypted; shown masked after saving. |
Paste these into the provider's console
- Redirect callback URL
https://api.socialmati.com/api/oauth/threads/callback
HTesting
- 1Connect a Threads profile and publish a test post.
ITroubleshooting
| Problem | What to do |
|---|---|
| Invalid credentials | Check the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure. |
| Missing permissions | Reconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved). |
| OAuth failure | Sign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app. |
| Redirect URI mismatch | Copy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| App review required | Permissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions. |
| Billing required | Add a payment method or prepaid credits on the provider account (see section E). |
JDisconnect & security
- Revoke access at the provider
- Threads → Settings → Account → Website permissions → remove the app.
- Disconnect in the application
- App → Integrations → Providers & API keys or App → Integrations → Connected accounts → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
- Rotate credentials
- Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
- How credentials are stored
- Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
- What data the application can access
- The connected profile's posts, replies and insights.
Other Social providers
Facebook / Meta
OAuth 2.0 (Facebook Login) — App ID + App secret
Setup guide Instagram
OAuth 2.0 through the Meta app (Facebook Login)
Setup guide LinkedIn
OAuth 2.0 — Client ID + Client secret
Setup guide X (Twitter)
OAuth 2.0 with PKCE — Client ID + Client secret (+ app bearer token for listening)
Setup guide YouTube
OAuth 2.0 (Google) + optional API key
Setup guide TikTok
OAuth 2.0 — Client key + Client secret
Setup guide 
