X API integration guide
Publish supported posts, media, threads, and polls to X while respecting account tier, provider limits, and capability changes.
Publish supported posts, media, threads, and polls to X while respecting account tier, provider limits, and capability changes.
X integration overview
Publish supported posts, media, threads, and polls to X while respecting account tier, provider limits, and capability changes.
API access tier, account permissions, text length, media processing, polls, and thread behavior must be checked for the connected account.
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 and media posts
- Capability-dependent polls
- Structured multi-post thread workflows
Model a post as one parent workflow with a separate target for each X account. This preserves the resolved content, delivery attempt, provider identifier, error, and retry state for every destination.
Connection and setup checklist
- 1
Configure an approved X provider app or eligible managed connection.
- 2
Authorize the intended profile with the required read and write scopes.
- 3
Inspect thread, poll, media, feed, and analytics capabilities before building controls.
Media and validation
Validate upload category, image or video limits, processing status, alt-text support, and poll compatibility before dispatch.
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
Feed and analytics access can differ by API tier; comments and direct-message operations remain capability-driven.
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 X 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 X 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 X 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.