Publish to Bluesky, read the replies under your posts, track mentions of your handle, and read and send DMs through the same unified API you already use for every other platform. Connect an account once with its handle and an app password, and every interaction comes back in the same schema, on the same webhook endpoint, with the same error codes.
Publish a post to Bluesky
1curl -X POST https://api.social-api.ai/v1/posts \
2 -H "Authorization: Bearer <your-api-key>" \
3 -H "Content-Type: application/json" \
4 -d '{
5 "targets": [{ "account_id": "<bluesky-account-id>" }],
6 "text": "Shipped Bluesky support today. Same API, one more platform."
7 }' | jq
8
9# Response
10{
11 "id": "<post-id>",
12 "status": "published",
13 "platforms": {
14 "bluesky": {
15 "status": "published",
16 "platform_post_id": "at://...",
17 "published_at": "2026-09-14T18:00:00Z"
18 }
19 }
20}
The same POST /v1/posts endpoint you already use for every other platform. Add a Bluesky account to the targets array and nothing else in your publishing code changes.
Read the replies under your Bluesky posts and reply back through the same comment endpoints used on every other platform.
Read DM conversations and send messages through the same unified inbox you use for Instagram and Facebook messaging.
Fetch posts mentioning your connected handle through the same dedicated mentions endpoint used for Instagram and X.
Publish through the same POST /v1/posts call as every other platform. GET /v1/constraints returns what a Bluesky post accepts before you send it.
New Bluesky interactions arrive on your single configured webhook endpoint, in the same envelope as every other platform.
Bluesky is built on the AT Protocol, and its own per-post limits are the platform's rather than SocialAPI.ai's. Read them from GET /v1/constraints instead of hard-coding them, so your app follows the platform when they change.
Accounts connect with a handle and an app password rather than OAuth, which is what the AT Protocol offers. Revoking the app password in Bluesky settings surfaces as a 401 and the account has to be reconnected before calls succeed again.
Platform throttling surfaces as a 429 and does not consume your SocialAPI.ai quota. Retry with backoff rather than treating it as a failed write.
Anything Bluesky does not support returns 501 rather than failing quietly, so an unsupported call is visible in your logs instead of looking like a silent no-op.
Bluesky posts go out through the same POST /v1/posts request as Instagram, LinkedIn, or Threads. Add a Bluesky account to the targets array and the rest of your publishing code is untouched. Ask GET /v1/constraints what a Bluesky post accepts instead of hard-coding the platform's limits into your app.
Read the replies on your Bluesky posts and reply back through the same comment endpoints used across every other connected platform. A reply on Bluesky arrives in the same shape as a comment on Instagram, so your moderation and support queues need no Bluesky-specific branch.
Fetch posts mentioning your connected handle through the same mentions endpoint used for Instagram and X. Poll it on a schedule, or let the mentions land on your webhook, and build brand monitoring or a support queue once for every platform at the same time.
List DM conversations, read message history, and send replies through the unified inbox endpoint, the same request and response shape you already use for Instagram and Facebook messaging. Bluesky does not need its own code path.
Posts, replies, mentions, and DMs on Bluesky come back in the same unified interaction schema as every other platform, arrive on the same single webhook endpoint in the same envelope, and fail with the same HTTP sentinels: 401 for an expired token, 429 when the platform throttles you, 501 for something a platform does not support. Bluesky is a new target for code you have already written.
Reading comments, DMs, and mentions is free and unlimited on every plan. Paid plans start at $29/mo with unlimited posts and interactions. The free tier needs no credit card.
FAQ
Yes. Bluesky is built on the AT Protocol and SocialAPI.ai exposes it through the same REST API as every other platform: publish posts, read and write replies, fetch mentions of your handle, and read and send DMs with one API key.
Yes. Send a POST /v1/posts request with a Bluesky account in the targets array, exactly as you would for Instagram or LinkedIn. Call GET /v1/constraints first if you want to check what a Bluesky post accepts before publishing.
Yes. Replies under your Bluesky posts are read and answered through the same comment endpoints used on every other platform, and each one comes back in the same normalized schema as a comment from Instagram or Facebook.
Yes. List conversations and send messages through the same /v1/inbox/conversations endpoints used for Instagram and Facebook DMs. There is no separate Bluesky messaging integration to build.
With the handle, for example @yourname.bsky.social, and an app password generated in Bluesky settings. There is no OAuth flow: the AT Protocol does not offer one. The app password is encrypted at rest, is scoped to what you grant it, and can be revoked from Bluesky at any time.
Yes. The built-in MCP server exposes publishing and inbox reads as tools, so Claude and other MCP-capable agents can draft Bluesky posts and replies inside your existing approval flow.
Get started today
Free tier available · No credit card required · Ships with MCP server
We use essential cookies for security, and analytics cookies with your consent. Privacy Policy.