Bluesky

Publish text, image, video and thread posts to Bluesky with POST /v1/posts and platform: "bluesky".

Bluesky connects with an app password instead of OAuth. The same account also serves DMs and comments.

Quick reference

Before you start

Bluesky requires an app password for the account, created in Bluesky's settings, and a handle. Custom domain handles work (brand.com as well as brand.bsky.social).

The 300-character count includes text, URLs and mentions.

Cross-posting from a platform with a longer limit? Set customContent on the Bluesky entry with a shorter version, or the Bluesky entry fails.

Connect

Call POST /v1/connect/bluesky/credentials with the handle, the app password and state (Connect Bluesky account).

state is {userId}-{profileId}. userId is currentUserId from GET /v1/users, and profileId comes from GET /v1/profiles.

The full sample is under Bluesky in the connecting accounts guide.

curl -X POST https://zernio.com/api/v1/connect/bluesky/credentials \
  -H "Authorization: Bearer $ZERNIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "identifier": "yourhandle.bsky.social",
    "appPassword": "xxxx-xxxx-xxxx-xxxx",
    "state": "66a0e8b1c2d3e4f5a6b7c8d9-66a1f0c2a4b9d3e8f1a2b3c4"
  }'

Response (200):

{
  "message": "Bluesky connected successfully",
  "account": {
    "platform": "bluesky",
    "username": "yourhandle.bsky.social",
    "displayName": "Your Name",
    "isActive": true
  }
}

There are no OAuth scopes. The app password grants API access to the account over the AT Protocol, without exposing the main password.

The user can revoke it at any time from Bluesky's settings.

In this section

Related

• Connecting accounts: the app-password flow.
• Create post: every field of the request.
• Media uploads: upload images and videos instead of hosting them.
• Analytics: post performance metrics.
• Messages and Comments: the inbox API.