Threads

Threads Content Publishing API

An overview of the Threads publishing API and what it requires from an integrating app.

Quick answer

Threads content publishing sits behind Meta's app review: beyond baseline account access, an app needs a content-publishing permission approved at production scope before it can publish to real customers' profiles — until then it can only post to its own developer and tester accounts. PostGate already holds that reviewed permission, so connecting through its OAuth flow skips the review.

Publishing to Threads on a user's behalf sits behind Meta's app review, the same gate Instagram and Facebook publishing go through. This page is about what that permission actually covers, what it takes to get it, and why a managed API like PostGate lets you skip most of that process.

01

Which permission does publishing need?

Every Threads API call needs baseline account access, and publishing specifically needs an additional content-publishing permission on top of it. Until an app is approved for that permission at production scope, it can only publish to its own developer and tester accounts — not to real customers' Threads profiles.
02

What does the publishing permission actually let you do?

Text posts, single image or video posts, and carousels of 2–20 items — everything covered in the Threads posting API overview. Reply threading (posting into an existing Thread as a child) is included; comment moderation on published posts is gated behind a separate reply-management permission, and direct messages are not exposed on Threads at all.
03

What does app review actually ask for?

Meta reviews the publishing permission independently from other Threads permissions your app might request, and typically wants a screencast showing the exact flow a user goes through to connect their account and have your app publish on their behalf. Building that connection screen, keeping it in sync with Meta's current OAuth flow, and re-submitting when Meta changes review requirements is ongoing work, not a one-time task.
04

Is approval shared with Instagram and Facebook?

Threads, Instagram, and Facebook Pages all connect through the same Meta OAuth consent screen and the same underlying app review infrastructure. An app already approved to publish to Instagram or Facebook Pages still needs Threads' publishing permission reviewed separately — Meta doesn't bundle approval across products.
05

Can you skip the review by publishing through PostGate?

PostGate already holds the reviewed Threads publishing permission on its own Meta app. Connecting a customer's Threads profile through PostGate's OAuth flow means your product can publish to Threads today, without waiting weeks for your own app to clear Meta's review queue.

Frequently asked questions

What does the Threads content-publishing permission cover?

Text posts, single image or video posts, and carousels of 2–20 items. Reply threading — posting into an existing Thread as a child — is included. Comment moderation on published posts is gated behind a separate reply-management permission, and direct messages are not exposed on Threads at all.

What does Meta's app review ask for on Threads?

Meta reviews the publishing permission independently from other Threads permissions your app might request, and typically wants a screencast showing the exact flow a user goes through to connect their account and have your app publish on their behalf. Building that connection screen, keeping it in sync with Meta's current OAuth flow, and re-submitting when requirements change is ongoing work, not a one-time task.

If my app is approved for Instagram publishing, can it publish to Threads too?

No. Threads, Instagram, and Facebook Pages all connect through the same Meta OAuth consent screen and the same underlying app review infrastructure, but an app already approved to publish to Instagram or Facebook Pages still needs Threads' publishing permission reviewed separately — Meta does not bundle approval across products.

Can I publish to Threads without my own Meta app review?

Yes. PostGate already holds the reviewed Threads publishing permission on its own Meta app, so connecting a customer's Threads profile through PostGate's OAuth flow means your product can publish to Threads today, without waiting weeks for your own app to clear Meta's review queue.

Build it with PostGate

One API for every social platform your customers care about — sandboxed, documented, and ready today.

Start building Read the docs