Threads API

Threads API for posting and scheduling without the Meta permissions puzzle

Add Threads publishing to products that need Meta text publishing and conversation-led distribution with one API for scheduling, media, status, and reporting workflows.

Last updated: May 2026

API key authScheduled publishing14 platforms
Quick start
API request
1await fetch("https://api.bundle.social/api/v1/post", {2  method: "POST",3  headers: {4    "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5    "Content-Type": "application/json"6  },7  body: JSON.stringify({8    teamId: "team_123",9    title: "Threads campaign",10    postDate: "2026-05-14T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["THREADS"],13    data: {14      THREADS: { text: "Scheduled from bundle.social." }15    }16  })17});

Building directly on Meta Threads API

Threads uses Meta's permission and account model, so OAuth and app review still matter.
Scheduling Threads posts takes more than adding a publish date to a text field.
Teams need Threads in the same plan as Instagram, Facebook, LinkedIn, X, and other channels.

What bundle.social handles

Schedule Threads posts through the same API pattern used for your other social accounts.
Use upload IDs and media metadata for Threads content when the API supports it.
Connect Threads analytics and post history to broader reporting when data is available.

Threads publishing without another Meta-side quest

Threads is conversation-led, but the setup still runs through Meta accounts, permissions, media rules, and status handling. bundle.social keeps it close to Instagram and the rest of your launch plan.

Workflow

How it works

Connect accounts once, then create and schedule posts with channel-specific fields from one API.

01

Create an API key

Generate an organization API key in the dashboard and use it with the x-api-key header.

02

Connect accounts

Connect each social account once. bundle.social keeps the account mapping ready for future posts.

03

Create or schedule posts

Send one request with the publish date, selected channels, and the fields each platform needs.

Capabilities

Threads API workflows for text-first campaigns

Text posts, media references, Meta account connection, scheduling, status, and reporting context for Threads publishing.

Threads-specific payload fields

Control the fields that matter on Threads: captions, media types, privacy settings, and more, using the same post endpoint as every other channel.

API key authentication

Use one bundle.social API key for server-to-server requests. Your users still connect social accounts once through the hosted OAuth flow; bundle.social handles token storage and refresh.

Scheduling built in

Set a postDate to schedule Threads content in advance, or create drafts and queue posts through the dashboard.

Media library integration

Upload Threads-compatible media once and reference the same upload ID across multiple posts or campaigns.

Post status and retry tracking

Track Threads posts through scheduled, processing, posted, retrying, and error states from the API or the shared dashboard.

Cross-platform publishing

Add other channels to the same post payload when Threads is part of a multi-platform campaign. No separate API calls needed.

Developer example

Schedule a Threads post

Examples use bundle.social's public API shape: API key authentication, a post date, selected social account types, and platform-specific data.

TypeScript
API request
1await fetch("https://api.bundle.social/api/v1/post", {2  method: "POST",3  headers: {4    "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5    "Content-Type": "application/json"6  },7  body: JSON.stringify({8    teamId: "team_123",9    title: "Threads campaign",10    postDate: "2026-05-14T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["THREADS"],13    data: {14      THREADS: { text: "Scheduled from bundle.social." }15    }16  })17});

Supported content

Text postsImagesVideosCarousel mediaAlt textReplies where supported

Honest limitations

  • Threads is controlled by Meta account, permission, and API availability rules.
  • Global search, DMs, and broad discovery workflows are not the same as owned-account publishing.
  • Some reply and moderation features may require separate comment workflows.

Guarantees

Developer-first infrastructure

2% error rate

We handle the platform edge cases, media processing, and rate limits so your requests succeed.

Verbose errors

When native APIs fail, we return human-readable error messages and actionable recovery steps.

Flat pricing

No per-post counting. Predictable pricing for teams managing many users, workspaces, and connected accounts.

Same-day support

Direct access to the engineers building the API. We respond to technical issues the same day. Sometimes the same hour. Test us c;

Resources

Technical guides & documentation

FAQ

Questions developers ask before building

Can I publish to Threads through bundle.social?

Yes, for supported Threads account types and permissions. bundle.social exposes the Threads fields you need inside a broader scheduled post workflow.

Does this replace Meta Threads API?

No. bundle.social runs on top of native platform APIs and reduces the work around publishing, scheduling, status, media, and reporting.

Can I schedule Threads posts?

Yes. Send a future postDate, set status to SCHEDULED, and include the THREADS payload.

Can I use Threads with other platforms?

Yes. Threads can run in the same workflow as your other supported social channels.

Are Threads analytics supported?

Threads analytics are available when the connected account and native API expose the data.