Threads API integration guide
Publish supported text and media posts to Threads and normalize available post performance and conversation signals.
Publish supported text and media posts to Threads and normalize available post performance and conversation signals.
Threads integration overview
Publish supported text and media posts to Threads and normalize available post performance and conversation signals.
Threads capabilities evolve with the provider API, so clients should not infer parity with Instagram despite shared account ecosystems.
A provider appearing in this guide does not guarantee that every operation is enabled for every account. Use capability discovery before showing a control or promising automation.
Publishing workflows
- Text-first posts
- Supported image or video attachments
- Account-specific publishing validation
Model a post as one parent workflow with a separate target for each Threads account. This preserves the resolved content, delivery attempt, provider identifier, error, and retry state for every destination.
Connection and setup checklist
- 1
Configure the supported Threads provider app path.
- 2
Connect the Threads profile and confirm granted permissions.
- 3
Use capability discovery before enabling media, reply, or analytics features.
Media and validation
Validate attachment count, type, size, and any reply or conversation fields returned for the account.
Validate before dispatch as well as during composition because account permissions and provider constraints can change after a draft is saved. Return target-level provider errors with a safe message, stable error code, and request ID.
Feeds, analytics, and engagement
Expose only the feed, analytics, replies, and mention behavior the current connection reports.
Normalized analytics use null when a metric is unavailable. A missing provider metric is not the same as a measured zero, and client reports should preserve that distinction.
Frequently asked questions
Does App9 Post support every Threads feature?
No. Support is determined by the connected account's current capability response, provider permissions, account type, provider review, and App9 Post certification status.
Should my composer hardcode Threads limits?
No. Use the capability matrix for live validation and treat documentation as design guidance rather than a substitute for account-level constraints.
Can I use my own Threads OAuth app?
App9 Post supports managed and customer-provided provider credentials where the provider connection is available. Customer-owned apps remain subject to the provider's review and policy requirements.