Bluesky API integration guide
Publish supported text and media posts to Bluesky through its account and AT Protocol capabilities.
Publish supported text and media posts to Bluesky through its account and AT Protocol capabilities.
Bluesky integration overview
Publish supported text and media posts to Bluesky through its account and AT Protocol capabilities.
Identity, handle resolution, repository state, facets, links, reply references, and AT Protocol behavior require structured handling.
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 posts
- Supported image attachments and alt text
- Reply, quote, and thread patterns where enabled
Model a post as one parent workflow with a separate target for each Bluesky 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 Bluesky authorization approach for the brand.
- 2
Connect the intended account and verify identity.
- 3
Inspect posting, media, feed, reply, and analytics capabilities before enabling tools.
Media and validation
Validate blob types and sizes, keep accessible image descriptions, and generate facets from the final resolved text rather than stale offsets.
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
Author feeds, reactions, replies, and available metrics can be normalized while retaining AT Protocol record references and links.
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 Bluesky 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 Bluesky 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 Bluesky 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.