For developers

Post to Bluesky with the 1Post API

Post to Bluesky from code with one request: POST /v1/posts with your account id, the text and a schedule_at time. Bluesky text is limited to 300 characters, counted by the characters a reader sees. 1Post allows up to 100 posts a day for each connected account, and a dry run checks a post against every rule first.

Updated 2026-10-26

Connect Bluesky first

  1. 01

    Create an app password in Bluesky's settings.

  2. 02

    Open Accounts in 1Post and choose Connect, then Bluesky.

  3. 03

    Enter your handle and the app password.

  4. 04

    Choose the account in the composer.

Then GET /v1/accounts returns the id of the Bluesky account to use in the request.

Send a post to Bluesky

Schedule a post
curl https://api.get1post.com/v1/posts \
  -H "Authorization: Bearer $ONEPOST_API_KEY" \
  -H "Idempotency-Key: bluesky-first-post" \
  -d '{"accounts":["ACCOUNT_ID"],"text":"Notes from the latest release.","schedule_at":"2026-11-02T15:00:00Z"}'

The reply is 202 with the post (status scheduled) and one destination for Bluesky, which moves from queued to published or failed.

What you can send to Bluesky

  • Text
  • Up to 4 images
  • One video
  • Threads
  • Alt text

Bluesky rules the request is checked against

RuleWhat 1Post checks
Text limit300 characters, counted by the characters a reader sees
Media acceptedImages, Video
Images per post4
Videos per post1
Images and video togetherNot in one post
ThreadsYes, as a chain of replies
First commentYes
Posts per day, per connected account (1Post)100

The same table with sources is on the Bluesky specs page.

Bluesky options in the request

  • Thread: send parts instead of text. Each part is one post in the chain, up to 100 parts, and each is counted on its own.
  • First comment: add first_comment with text to an account object, and delay_min if it should wait.
A two-part thread in the next free slot
{
  "accounts": [
    "ACCOUNT_ID"
  ],
  "parts": [
    {
      "text": "1/ The short version."
    },
    {
      "text": "2/ The detail.",
      "delay_min": 1
    }
  ],
  "use_next_free_slot": true
}

Check the post before it is queued

Add "dry_run": true to test a post: nothing is kept, a valid one answers 200 and a broken one answers 422 naming the rule.

A refused request, abridged
{
  "error": {
    "code": "invalid_for_platform",
    "message": "bluesky refuses this post: Bluesky counts 332 of 300 characters in part 1. (text_too_long).",
    "fix": "Fix the rule named in the message and send the post again.",
    "retryable": false,
    "request_id": "REQUEST_ID"
  }
}

An assistant connected to the MCP server sends the same fields to create_post; set one up.

Try it

Start a trial

7-day trial for $1. Connect your accounts and schedule a week of posts in one sitting.

Start a trial
Free in your browser

Free tools

Count characters the way each network does, split threads and preview posts. No account needed.

Open the tools
For builders

API and MCP

Post to every network from your own code or assistant with one key, signed webhooks and idempotent requests.

See the API

Questions

Can I post to Bluesky with an API key?

Yes. A key with write scope can create, change and cancel Bluesky posts for the workspace it belongs to, with the role of the member who made it. See API authentication.

What happens if a Bluesky post breaks a rule?

The request is refused with invalid_for_platform and the failing rule is named. Fix it and send the request again, or send it with dry_run to test the fix first.

How many Bluesky posts can I send in a day?

Up to 100 for each connected account. A request that would pass that answers daily_cap with the time the day frees up.

Get this week’s posts scheduled

Connect your accounts, write once and let 1Post publish on time while you get on with the rest of your day.