Bluesky

Bluesky is supported via the AT Protocol. OmniSocials posts to the specific account that completed OAuth. Both bsky.social and self-hosted PDS accounts work.

Channel ID: bluesky

Supported content types

Minimal example

Code
curl -X POST https://api.omnisocials.com/v1/posts/create \
  -H "Authorization: Bearer $OMNISOCIALS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": { "default": "Skeeting from the API 🦋" },
    "accounts": ["your-bluesky-account-id"]
  }'

Platform-specific options

Bluesky has no required option fields.

Media requirements

Bluesky has tighter image size limits than most platforms. Pass pre-compressed images to avoid rejections.

Character limit

Bluesky enforces a 300 grapheme limit per post (emoji count as 1 grapheme, not their UTF-8 byte length). OmniSocials counts graphemes correctly when validating.

Limitations

• Threading (reply chains) is not supported through the API
• Hashtags render as plain text, not clickable entities, unless detected by Bluesky's client
• Bluesky does not expose post scheduling as a first-class concept. Scheduled OmniSocials posts are held on our side and published at the scheduled time.