Skip to main content
Publish text, images, videos, mixed carousels and linked reply sequences to team-owned Threads accounts.

​
Connect an account

1

Configure the provider

The installation operator supplies POSTED_THREADS_CLIENT_ID and POSTED_THREADS_CLIENT_SECRET to both API and worker. Configure a Threads application with permission to read the account identity and publish content. Complete the provider’s approval or account-access steps for the accounts you intend to connect.
2

Authorize the account

A team administrator opens Connections → Add connection, chooses Threads, and completes the provider’s sign-in and consent flow.
3

Choose it in the composer

After returning to Posted, confirm that the account is Connected. Select it through Choose Accounts, review its preview and customize its text or media if needed.
Accounts belong to the team. Connecting the same provider account again refreshes the existing connection. Members can compose for connected accounts; only administrators can add or disconnect them.

​
Application configuration

Register the exact API callback in your provider application:
Replace the example origin with your API origin. For the hosted installation, it is https://posted-api.avgeek.ltd/api/social/callback/threads. Posted requests threads_basic,threads_content_publish. Configure a Threads application with permission to read the account identity and publish content. Complete the provider’s approval or account-access steps for the accounts you intend to connect. See configuration for the shared runtime environment and Towbar provider setup for private value entry. Follow the provider’s official authorization documentation for its registration and approval process.

​
Limits enforced by Posted

These are Posted’s current delivery limits. Use list_providers or the provider API endpoint to inspect the running installation’s capabilities. Uploaded originals are prepared for the provider at delivery time; provider account permissions and quotas still apply.

​
Posts, media and threads

A Threads post can use the first 20 attachments in its chosen order, including a mixture of images and videos. For a sequence, each later post replies to the previous confirmed post on that account. Each post has independent text and attachment order. Account-specific edits affect only that account and post. Reset to master restores text and media inheritance after confirmation. Image or video publishing requires private media storage. Read Compose a post for single posts and Compose threads for insertion, ordering, reply links and failure handling.

​
Reconnect and troubleshoot

If the account needs reauthentication, an administrator repeats the official authorization flow. If Threads is missing from Add connection, ask the operator to check the complete provider configuration and deploy the saved runtime values. A callback mismatch must be corrected in the provider application using the API origin, not the UI or documentation domain. Inspect Publish history for each account’s result. A confirmed provider publication stays published if another account fails. An Uncertain result needs provider-side inspection before another posting request. Disconnecting prevents later use of the account and does not remove existing provider posts.