Requirements

Use a connected Threads account from GET /accounts with capabilities.publishPosts: true. The account must belong to the API key’s workspace.

Supported formats

Text posts and a thread chain of 1–25 posts. One request can target 1–5 supported text accounts. The public API does not accept image or video attachments for Threads.

Publish a post

Account and media UUIDs are illustrative; replace them with real IDs. Set your API key in the POSTEADY_API_KEY environment variable.

curl --request POST "https://www.posteady.com/api/v1/posts" \
  --header "Authorization: Bearer $POSTEADY_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "accountIds": [
    "11111111-1111-4111-8111-111111111111"
  ],
  "posts": [
    "Hello from Posteady!"
  ]
}'

Thread chain

{
  "accountIds": [
    "11111111-1111-4111-8111-111111111111"
  ],
  "posts": [
    "Here is our announcement.",
    "And here is the next part."
  ]
}

Confirm success

Inspect each account’s success and postIds, plus summary.failed, in the HTTP 200 response. Other targets or later chain items can fail, so the HTTP code alone does not prove full success.

To schedule, send the same platform input to /scheduled-posts with a future scheduledAt and optional timezone. For asynchronous platforms, generate a UUID requestId per operation and retain it for retries.

Schedule and cancel · Read posts and metrics · Retries · MCP tools

Limits and errors

Each post allows up to 500 Unicode characters. Each text item must be non-empty. Multiple items publish as a reply chain, and a later item can fail after earlier items were published. Inspect returned postIds before retrying. Threads supports reposting and synchronized post metrics.

Publishing reference · Troubleshooting

Threads