Does SkedCast's Bluesky adapter use the official AT Protocol client identity?

Yes — connecting a Bluesky account authenticates over the AT Protocol like any other AT Proto client; publishing calls the same `putRecord`-style write the protocol defines, so a published post is indistinguishable from one made in the Bluesky app.

Post to Bluesky via API — SkedCast developer guide

Browse docs

6 min read

Before you publish#

You need one already-connected account for the platform. Connect it yourself in the Agency Console, or — if a client owns the account — mint a self-serve connect link with POST /clients/:id/connect-invites and send it to them; they authorize from that page without ever getting a SkedCast login.

GET /v1/accounts lists what's connected, with each account's id — that id is what you pass in targets.accountIds below.

Compose and schedule#

bash

curl -X POST https://api.skedcast.com/v1/posts \
  -H "Authorization: Bearer sked_live_YOUR_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "<clientId>",
    "content": "Launch day is here 🚀",
    "mediaIds": ["<mediaAssetId>"],
    "targets": { "mode": "selection", "accountIds": ["<blueskyAccountId>"] },
    "schedule": { "type": "at", "scheduledAt": "2026-07-01T15:00:00Z" }
  }'

A minimal bluesky post, scheduled for a specific time.

The Bluesky API post fields#

Everything platform-specific goes in one variants entry with "platform": "bluesky" and an overrides object. The adapter reads only the keys it declares (below) and ignores the rest — send bluesky keys on a bluesky variant, nothing more.

Field	Type	Values / default	Notes
`link`	string (url)	—	External link for an embed preview card.
`labelSexual`	boolean	`false`	Self-labels the post as sexually suggestive.
`labelNudity`	boolean	`false`	Self-labels the post as containing non-sexual nudity.
`labelPorn`	boolean	`false`	Self-labels the post as adult/pornographic content.
`labelGraphicMedia`	boolean	`false`	Self-labels the post as violent or otherwise graphic media.
`firstComment`	string	—	Posted as a reply in the same thread, with link facets resolved like any other post. Posted right after publish. Best-effort: a failed comment never fails the post and is not reported, so verify on the published post.

Verbatim from the REST API reference's Bluesky table.

With the platform-specific overrides#

json

{
  "clientId": "<clientId>",
  "content": "New post on the blog — link below.",
  "mediaIds": [],
  "targets": { "mode": "selection", "accountIds": ["<blueskyAccountId>"] },
  "variants": [
    { "platform": "bluesky", "overrides": { "link": "https://example.com/blog/launch" } }
  ],
  "schedule": { "type": "at", "scheduledAt": "2026-07-01T15:00:00Z" }
}

The same POST /posts body, with a variants entry added.

Checking the result#

Publishing fans out into one post target per account. GET /post-targets/:id (or GET /posts/:id) reports status, plus externalId (bluesky's own post id) and permalink (its public URL) once published. Subscribe to the target.published / target.failed webhooks instead of polling if you can accept inbound HTTP — see the webhooks guide.

blueskyatprotoapipublish

FAQ

Does SkedCast's Bluesky adapter use the official AT Protocol client identity?: Yes — connecting a Bluesky account authenticates over the AT Protocol like any other AT Proto client; publishing calls the same `putRecord`-style write the protocol defines, so a published post is indistinguishable from one made in the Bluesky app.

How to post to Bluesky with the SkedCast API