Postproxy × Threads

Publish posts to Threads with support for images, videos, and mixed media. Simple API, powerful results.

One API call handles Threads posts with flexible media support.

Get API key — free See pricing

Free plan · No credit card · Live in under 5 minutes

Mixed Media

Combine videos and images in a single post

Flexible Posts

Publish text-only or media-rich content

Image Carousels

Create carousel posts with up to 20 images

Video Support

Upload videos up to 1 GB and 5 minutes long

POST /v1/posts
Terminal window
curl -X POST "https://api.postproxy.dev/api/posts" \
     -H "Authorization: Bearer YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "post": {
         "body": "Exciting announcement coming soon! Stay tuned."
       },
       "profiles": ["threads"],
       "media": ["https://example.com/image.jpg"],
       "platforms": {
         "threads": {}
       }
     }'

View full documentation for all platform-specific features for Threads

View documentation
INTEGRATION COST

Skip weeks of Threads integration work

One test post against a sandbox account is the easy part. Production Threads publishing means app verification, OAuth across many accounts, media pipelines, dozens of edge cases, and a permanent on-call rotation for "why didn't this one go through this time?"

5 min
Time to your first Threads post via API
Weeks → Hours
Engineering time saved on integration work
$0
Free plan, no credit card required
Build it yourself
  • Submit a Threads app for verification — review cycles, screencasts, business docs
  • Implement OAuth, token refresh, secure credential storage per account
  • Build media upload pipelines (chunked, async, multi-step) for every format
  • Handle rate limits, quotas, retries, and partial failures across accounts
  • Cover dozens of edge cases: expired tokens, scope drift, regional restrictions, policy changes
  • Triage every silent failure: "Why didn't this one post go through?"
Ship with Postproxy
  • One REST endpoint. One payload schema. SDKs for popular languages
  • OAuth, tokens, and refresh handled for you — across all accounts
  • Media upload, chunking, and format detection — automatic
  • Retries, rate-limit windows, and per-platform receipts built in
  • Edge cases are our problem. Failures come back with an explicit reason
  • We track the API changes. You ship features
Start posting to Threads via API See pricing

Free plan includes the Threads API. No credit card.

Why Postproxy for Threads?

Skip Threads API complexity

No need to handle Threads API, OAuth flows, or rate limits. Postproxy handles it all.

Handle rate limits automatically

Threads rate limits are managed automatically with intelligent retry logic.

Support all formats

Publish text posts, images, videos, or mixed media through one unified API.

Supported formats:
Feed posts

Reliable delivery

Automatic retries and clear status reporting ensure your content reaches Threads.

How Threads Publishing Works with Postproxy

Threads' publishing model

Threads uses Meta's Threads API, which follows a container-based publishing flow similar to Instagram's. You create a media container with your content (text, image, or video), wait for it to process, then publish it. Unlike Instagram, Threads supports text-only posts without media attachments. The API is tied to Instagram accounts — you publish to Threads through the Instagram user ID. Postproxy handles the container creation and publishing steps in a single request.

Text, images, video, and carousel posts

Threads supports four content types: text-only posts (up to 500 characters), single image posts, single video posts, and carousel posts with up to 10 mixed media items. Each type uses a slightly different container creation flow, and carousels require creating individual item containers before wrapping them in a carousel container. Postproxy detects the content type from your request and handles the correct flow automatically.

Common gotchas Postproxy handles for you

Threads' API has a few non-obvious constraints: the 500-character text limit, a rate limit of 250 posts per 24-hour window, and a requirement that media containers finish processing before you can publish them (with no webhook — you must poll). Videos have specific format requirements and a 5-minute maximum duration. The API also returns different error codes for rate limiting vs. content policy violations, which can be confusing. Postproxy validates content constraints upfront, manages polling, and provides clear error messages.

Reply controls and content settings

Each Threads post can specify who can reply: everyone, accounts_you_follow, or mentioned_only. This is set at container creation time and can't be changed after publishing. Postproxy exposes this as a simple reply_control parameter, defaulting to everyone if not specified.

Frequently Asked Questions

Common questions about Threads integration

Can I mix videos and images in a single Threads post?

Yes! Threads is one of the few platforms that supports mixing videos and images in a single post. You can include up to 20 images or 1 video, or combine them as needed.

What are the media constraints for Threads?

Threads supports images (jpg, png, gif, webp) up to 8 MB with up to 20 images per post, and videos (mp4, mov) up to 1 GB with a maximum duration of 5 minutes. Minimum dimensions are 200x200 pixels.

Are there any platform-specific parameters for Threads?

No, Threads does not have custom parameters. Postproxy handles all formatting automatically based on the content and media you provide.

Can I post text-only content on Threads?

Yes! Threads fully supports text-only posts without any media. Simply omit the media array from your post request.

What video formats are supported?

Threads supports mp4 and mov video formats. Videos can be up to 1 GB in size and must be between 0 and 5 minutes long.

Ready to get started?

Start with our free plan and scale as your needs grow. No credit card required.

Get started View documentation