Posting to Threads through the API

Conversational, and closer to X than to Instagram. The request shape is the same one every network here uses — only the limits on this page change.

Our business is verified with Meta and the Threads app is live; publishing still needs Meta's approval before we can post to your profile. The status page tracks it.

Connecting a Threads account

Needs a Meta app with the Threads API enabled. Once connected, we hold the credential and keep it alive; your code only ever sends the API key.

The limits we enforce before publishing

What pre-flight rejects, verbatim

A request that breaks a Threads rule comes back as a 422 naming the network and the number — before anything is scheduled, not after the other networks published. The error strings are these:

• 632 chars — Threads allows 500.
• 22 attachments — Threads allows 20.
• Video is 10m — Threads allows 5m.

The request

curl -X POST https://attentionpilot.com/api/v1/posts \
  -H "Authorization: Bearer $PILOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "caption": "Written for Threads, under 500 characters.",
    "accounts": ["threads"]
  }'

Omit schedule for the next free queue slot, send "now" to publish immediately, or send an ISO timestamp.

When Threads fails

Each network is delivered on its own. A revoked token or a rejected upload on Threads never blocks your other targets: the post returns "partial", the Threads target carries the error text, and you can retry just this delivery.

Worth knowing

• ✓500 characters
• ✓Carousels up to 20 items
• ✓Video up to 5m

The same call reaches the rest