Threads API for Text Posts and Thread Sequences

Threads is the platform in this workflow that publishes text without media, which makes it useful for announcements, changelogs, and multi-part posts. Wahdx Connection supports single text posts and thread sequences of up to 10 linked items, with scopes, character limits, and reply settings handled through the same API used for the other platforms. This page covers the capabilities, the connection and scopes, the limits, and the publish sequence.

Get Started Free Read API Docs

What the Threads API can do

The API publishes text-only posts, thread sequences, and posts with an image or video. A thread sequence chains up to 10 items, linking each one to the previous so the chain reads as a single conversation. Text posts carry up to 500 characters, and reply settings apply to a whole sequence rather than one item. Threads analytics then return views, likes, replies, reposts, and quotes for the connected account.

Text-only posts up to 500 characters.
Thread sequences of up to 10 linked items.
Photo or video attached per thread item.
Reply settings applied to the whole sequence.
Views, likes, replies, reposts, and quotes in analytics.

Threads character limits

Threads has three separate limits, and mixing them up is the usual cause of a rejected batch. A single text post carries up to 500 characters. A thread sequence can hold up to 10 items, and each item has its own 500-character budget, so the sequence is not one long post cut into pieces. Every item also counts against the account rate limit of 250 posts per user per 24 hours, which means a 10-item thread uses ten of that budget. The API rejects an over-length post before it is sent, so the ceiling is worth checking at the point where content is prepared rather than after a publish attempt.

Threads character and publishing limits
Limit	Value	What it applies to
Post length	500 characters	One text post
Thread item length	500 characters	Each item in a sequence
Thread sequence size	10 items	One linked chain
Daily publishing cap	250 posts per user per 24 hours	Every post and thread item
Scheduling window	Up to 30 days ahead	Scheduled posts and sequences

Scopes and authentication

Threads publishing requires the threads_content_publish scope, granted through Threads OAuth when the account is connected. The scope is visible when the user approves the connection, and the account appears in the account listing endpoint afterward. Publishing requests use the same X-API-Key header as the rest of the API, kept server-side. Analytics need the insights permission; without it, metric fields come back as null. Because the connection is consent-based, a user can disconnect at any time.

Text posts

A text post is a standard content request without media. The content field is required and cannot be empty or whitespace-only, and the length ceiling is listed in the limits table above. TikTok and Instagram reject media-less requests, so text-only publishing targets Threads and Facebook Pages. A whitespace-only caption counts as empty, so validate content server-side before submitting. If a scheduled text post targets a media-only platform, the request is rejected before anything is queued.

Thread sequences

A thread sequence posts up to 10 items through POST /api/content/post/threads. Each item can be text-only or include an image or video, and the platform links them automatically: the publish result of item N becomes the reply target for item N+1. Reply settings, such as who can reply, apply to the entire sequence. The response returns a publish ID per item, which you can track through the batch status endpoint.

const API_BASE_URL = 'https://api.wahdx.com';
const API_KEY = process.env.WAHDX_API_KEY;

const headers = {
  'X-API-Key': API_KEY,
  'Content-Type': 'application/json'
};

// Threads thread sequence
await fetch(API_BASE_URL + '/api/content/post/threads', {
  method: 'POST',
  headers,
  body: JSON.stringify(
    {
      "accountId": "THREADS_ACCOUNT_ID",
      "threadItems": [
        {
          "content": "Thread pertama dengan gambar",
          "mediaItems": [
            {
              "url": "https://your-domain.com/threads-photo-1.jpg"
            }
          ]
        },
        {
          "content": "Thread kedua hanya teks"
        },
        {
          "content": "Thread ketiga dengan video",
          "mediaItems": [
            {
              "url": "https://your-domain.com/video-threads.mp4"
            }
          ]
        }
      ],
      "threadsSettings": {
        "who_can_reply": "everyone"
      }
    }
  )
});

import os
import requests

API_BASE_URL = 'https://api.wahdx.com'
API_KEY = os.environ['WAHDX_API_KEY']

headers = {
    'X-API-Key': API_KEY,
    'Content-Type': 'application/json',
}

# Threads thread sequence
response = requests.post(
    API_BASE_URL + '/api/content/post/threads',
    headers=headers,
    json={
    'accountId': 'THREADS_ACCOUNT_ID',
    'threadItems': [
        {
            'content': 'Thread pertama dengan gambar',
            'mediaItems': [
                {
                    'url': 'https://your-domain.com/threads-photo-1.jpg'
                }
            ]
        },
        {
            'content': 'Thread kedua hanya teks'
        },
        {
            'content': 'Thread ketiga dengan video',
            'mediaItems': [
                {
                    'url': 'https://your-domain.com/video-threads.mp4'
                }
            ]
        }
    ],
    'threadsSettings': {
        'who_can_reply': 'everyone'
    }
},
    timeout=30,
)

# Threads thread sequence
curl -X POST "https://api.wahdx.com/api/content/post/threads" \
  -H "X-API-Key: $WAHDX_API_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{
  "accountId": "THREADS_ACCOUNT_ID",
  "threadItems": [
    {
      "content": "Thread pertama dengan gambar",
      "mediaItems": [
        {
          "url": "https://your-domain.com/threads-photo-1.jpg"
        }
      ]
    },
    {
      "content": "Thread kedua hanya teks"
    },
    {
      "content": "Thread ketiga dengan video",
      "mediaItems": [
        {
          "url": "https://your-domain.com/video-threads.mp4"
        }
      ]
    }
  ],
  "threadsSettings": {
    "who_can_reply": "everyone"
  }
}'

Scheduling Threads content

Scheduling follows the same 30-day window as the other platforms, and scheduled thread sequences post in order when the queue fires. The daily publishing cap is enforced by Threads, not by this API: every item in every sequence draws from the same per-account budget, and once the account is over 250 posts in 24 hours, the publish step fails at the provider rather than at submit.

Publish sequence: endpoint to endpoint

A Threads integration is four steps: list connected accounts to find the Threads accountId, build the payload (a single text post to POST /api/content/post with no media, or a sequence to POST /api/content/post/threads with up to 10 items), submit it, then poll the batch status endpoint with the returned publish IDs until every item reaches published or failed. The same account listing call covers all five platforms, so the integration does not need separate discovery logic.

Reading metrics back

Threads analytics cover views, likes, replies, reposts, and quotes for the connected account. Because the publishing workflow is also the reporting layer, the same account used to post is the account you read metrics from. Values the platform does not expose return null rather than a partial or estimated number, which keeps a multi-platform report honest.

FAQ

Common questions about the Threads API

Can I post text-only to Threads through an API?

Yes. Threads accepts text-only posts up to 500 characters through the standard content publishing endpoint when no mediaItems are sent.

How many items can a thread sequence contain?

Up to 10 items per sequence. Items post sequentially and link automatically, and each one counts toward the 250 posts per user per day limit.

How many characters can a Threads post have?

A single Threads text post carries up to 500 characters. In a thread sequence, each of the 10 items gets its own 500-character budget, so a sequence is not one long post split across items.

What scope does Threads publishing need?

The threads_content_publish scope, granted through Threads OAuth when the account is connected. Analytics also need the insights permission.

What does Threads analytics include?

Views, likes, replies, reposts, and quotes. Values come from the platform for the connected account, and unavailable metrics return null.

Go deeper on this workflow.

Back to homepage

From the blogThreads API Guide: Text Threads, Scopes, and Metrics

Related API docs

TikTok Content Publishing API: Video, Photos & Carousels

Publish video and photo carousels to TikTok through an official API. Media specs, posting limits, QR login, scheduling, and status tracking in one workflow.

Instagram Graph API Content Publishing for Business Accounts

Publish photos, reels, and carousels to Instagram with the Content Publishing API. Business account requirements, media limits, and metrics.

YouTube API: Upload Videos and Read Channel Analytics

Upload videos to YouTube with per-video settings, then read subscribers, views, and video metrics through one API workflow.

Facebook Graph API Page Publishing and Insights

Publish to Facebook Pages and read back unique impressions, post engagements, page views, and follows through one API workflow for content teams.