Threads BulkPublish

Threads API

Publish, schedule and manage Threads from your own code. One REST API and one key cover Threads and every other network you connect, so you write the integration once.

Get a free API key Read the API reference

What the Threads API covers

Everything below is part of the published API and works with Threads today.

Capability	Endpoint
Create, schedule, update and publish posts	`POST /api/posts`
Upload images and video	`POST /api/media`
Find the next free slot in your queue	`GET /api/posts/queue-slot`
Create repeating schedules	`POST /api/schedules`
Publish new items from an RSS feed	`POST /api/rss-feeds`
Look up Threads places for a channel	`GET /api/channels/{id}/options`
Post a first comment automatically	`platformSpecific._firstComment`
Publish multi-part threads	`postFormat: "thread"`
Read per-post metrics	`GET /api/posts/{id}/metrics`
Read and reply to comments on published posts	`GET /api/posts/{id}/engagement, POST /api/posts/{id}/comments/reply`
Check that the connection is healthy	`GET /api/channels/{id}/health`
Check your plan usage	`GET /api/quotas/usage`

Post types you can publish to Threads

Choose the type with postTypeOverrides. A type Threads does not offer is rejected before anything is queued.

Post type	Media
`text` Text	Text only
`image` Image	Required: 1 image
`video` Video	Required: 1 video
`carousel` Carousel	Required: 2 to 20 images or videos

Schedule Threads posts with curl

Three requests: find your channel, upload the file if the post has one, then create the post. Replace the key with one from Settings, then API keys, and 12 with your own channel id.

1. List your channels and note the id of your Threads account.

curl https://app.bulkpublish.com/api/channels \
  -H "Authorization: Bearer bp_your_key_here"

2. Create the post.

curl -X POST https://app.bulkpublish.com/api/posts \
  -H "Authorization: Bearer bp_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "content": "What did you ship this week?",
  "channels": [{ "channelId": 12 }],
  "status": "scheduled",
  "scheduledAt": "2026-12-01T09:00:00Z",
  "platformSpecific": {
    "threads": {
      "topicTag": "buildinpublic"
    }
  }
}'

The response is the created post, with its id and status. Fetch it later with GET /api/posts/{id} to see how it went.

Threads options

Send these inside platformSpecific, under the key for Threads.

Option	What it does	Accepts
`quotePostId`	Post to quote	text
`topicTag`	Topic tag	text
`locationId`	Place to tag	text

To find the valid places for a channel, call GET /api/channels/{id}/options.

Threads analytics through the API

These metrics come back for each Threads post on GET /api/posts/{id}/metrics, with snapshots over time.

Impressions
Likes
Comments
Shares
Engagement rate

Comments and messages

Through the API you can read and reply to comments on published posts.

Reading comments works on every plan. Replying to comments needs a paid plan, and the inbox is part of Pro and Business. Until a feature is switched on for your account the API answers 403 with a code you can check for.

API access on every plan

Every plan includes API keys, the Free plan included. Here is what each one allows.

Plan	API keys	Requests per day
Free	1	30
Pro	5	5,000
Business	10	50,000

Build on Threads directly, or use BulkPublish

Going direct is a fair choice, especially if you need something BulkPublish does not expose. This is what Threads API asks of you, checked against its documentation in October 2026.

Documented limit: 250 API-published posts in 24 hours.
A post with media takes several calls: upload or create, wait for processing, then publish.
Media is fetched from a public URL that you have to host.
Access tokens last about 60 days, so you need your own way to refresh or reconnect before they lapse.

BulkPublish keeps the connection for you: it refreshes tokens, checks each post against Threads's rules before it is queued, and reports a failed destination on the post, so your code makes one request.

Read the official documentation

Prefer to ask an assistant?

Claude, ChatGPT and Cursor can do the same through the Threads MCP server, with prompts instead of code.

See the Threads MCP server

Prefer a calendar to code?

The same Threads account can be scheduled from the app, with a content calendar and bulk upload.

See the Threads scheduler

Frequently asked questions

Common questions about the Threads API.

Is there a ready-made API for Threads, so I do not have to build the integration myself?

Yes. BulkPublish exposes Threads through its REST API. Connect your Threads account once, then publish, schedule and manage it with a key. The same key works for every other network you connect.

What can I publish to Threads through the API?

The post types are Text, Image, Video, and Carousel. Each is checked against Threads's media rules before anything is queued, so a request Threads would reject fails straight away with a clear error.

Can I schedule Threads posts through the API?

Yes. Send status "scheduled" with a scheduledAt time and a timezone, or ask for the next free slot in your queue first. Repeating schedules and RSS feeds are available too.

Can I read Threads analytics through the API?

Yes. Per-post metrics include Impressions, Likes, Comments, Shares, and Engagement rate, with snapshots over time.

Can I read and answer Threads comments or messages through the API?

Yes. You can read and reply to comments on published posts. Replying to comments needs a paid plan, and the inbox is part of Pro and Business.

Does the Threads API cost extra?

No. API access is on every plan. Free includes 1 key and 30 requests a day, Pro 5 keys and 5,000 a day, Business 10 keys and 50,000 a day.

Do I need a Threads developer account or an app review?

Not to use BulkPublish. You connect your Threads account on the Channels page and publish with a BulkPublish key. If you build on Threads's own API instead, the section above lists what it asks of you.

Can an AI assistant do this too?

Yes. The Threads MCP server page shows how to connect Claude, ChatGPT or Cursor and what to ask for.

The same key and the same request shape work for 15 networks.