Publishing API

Threads publishing API with one SocialClaw workspace.

Connect a Threads profile through Threads OAuth from SocialClaw. SocialClaw stores a long-lived token and refreshes it before it expires. SocialClaw publishes Threads text posts, a single image or video, and mixed image/video carousels, on a schedule or right away.

Works with Claude, ChatGPT, OpenClaw ClaudeChatGPTOpenClaw

What SocialClaw supports for this workflow

A quick overview of what this workflow supports.

Account target Threads profile SocialClaw publishes Threads text posts, a single image or video, and mixed image/video carousels, on a schedule or right away.
Auth model OAuth Connect a Threads profile through Threads OAuth from SocialClaw. SocialClaw stores a long-lived token and refreshes it before it expires.
Media envelope Threads posts can be text only (up to 500 characters), one image or video, or a carousel of up to 20 images and videos. The provider pulls a public media URL, including SocialClaw-hosted media URLs.
Inspection Validate, apply, inspect Analytics snapshots are available, but Threads provider-native analytics are not implemented yet. SocialClaw records the real Threads post ID and permalink after publishing.

What the payload needs

The main fields and constraints to account for.

How the workflow runs

Connect the account, validate the post, then publish.

01

Authenticate the workspace

Use the workspace API key with the CLI or hosted HTTP API so the publishing workflow stays attached to the same customer workspace.

02

Connect Threads

Connect a Threads profile through Threads OAuth from SocialClaw. SocialClaw stores a long-lived token and refreshes it before it expires.

03

Inspect account capabilities and settings

Read the current settings surface, including replyControl, before generating the final payload.

04

Validate before apply

Validation should happen before create-run or apply. Threads posts can be text only (up to 500 characters), one image or video, or a carousel of up to 20 images and videos.

05

Inspect the resulting run or post

SocialClaw records the real Threads post ID and permalink after publishing. Analytics snapshots are available, but Threads provider-native analytics are not implemented yet.

CLI and HTTP examples

Example commands and requests for this route.

socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider threads --open
socialclaw accounts capabilities --provider threads --json
socialclaw validate -f schedule.json --json
socialclaw apply -f schedule.json --idempotency-key launch_1 --json
socialclaw runs inspect --run-id <run-id> --json

Current limitations

A few practical limits to keep in mind.

Related routes

Related integrations and use cases.

What builders are saying

Real quotes from Reddit, G2, Trustpilot, and Instagram.

Works with every major platform

Connect once, then schedule and publish everywhere from the same workspace.

Frequently Asked Questions

Threads uses the Threads profile route in SocialClaw. Connect a Threads profile through Threads OAuth from SocialClaw. SocialClaw stores a long-lived token and refreshes it before it expires.

Run the Threads publishing API workflow in SocialClaw

Connect the account once, validate before publish, and keep everything in one workspace.

Supported social platforms
Schedule to social media Works with Claude ChatGPT Codex OpenClaw
Start free