Do I need my Bluesky account password?
No, and you should not use it. An app password only posts. You create it under Settings, App Passwords, and you can revoke it at any time without touching your account.
How to sendfrom
Follow these steps to connect Bluesky post, send from Next.js, and track delivery.
Bluesky speaks the AT Protocol, so there is no OAuth dance to sit through. You create an app password in your own Bluesky settings, paste it into yeetpost with your handle, and delete it whenever you like: every session made from that password dies with it, and your account password is never involved. From Next.js you call it through the yeetpost npm package, from a route handler, a server action or a scheduled job.
What Bluesky takes
| How you connect | An app password from Bluesky Settings, App Passwords, plus your handle |
|---|---|
| Connection slug | bluesky for the first account, then a slug built from the handle |
| Text limit | 300 graphemes, so a multi-codepoint emoji counts once |
| Images | Up to 4 per post, 1 MB each, png, jpeg, gif or webp |
| Alt text | Yes, sent with each image |
| Threads | Yes, up to 24 replies under the head post |
| First comment | No, LinkedIn only |
| Scheduling | Yes |
| Permalink | https://bsky.app/profile/<handle>/post/<record key> |
| Per-post fee | None |
1
Connect your platform
Connect your Bluesky account to yeetpost with an app password, never your account password:
- In Bluesky, open Settings, then App Passwords, and create one
- Go to app.yeetpost.com
- Click Add connection and select Bluesky
- Paste your handle (
you.bsky.social) and the app password (xxxx-xxxx-xxxx-xxxx) - Running your own PDS? Open On your own server? Set the service URL and give the host. It has to be
https, and the default ishttps://bsky.social
The account is identified by its DID, not by the handle, so renaming your handle later does not break the connection.
Paste your connection slug here and we'll auto-fill it into the code examples below.
2
Get your API key
Get your API key from the yeetpost dashboard:
- Go to app.yeetpost.com/app/settings
- Copy your API key
Paste your API key here and we'll auto-fill it into the code examples below.
3
Send your post
Install the yeetpost package:
npm install yeetpostSet your API key as an environment variable in .env.local. Keep it out of any name that starts with NEXT_PUBLIC_, because those are inlined into the browser bundle:
YEETPOST_API_KEY=<your-api-key>Send the post from a route handler, a server action or a scheduled job, never from a client component:
// app/api/announce/route.ts
import { yeetpost } from "yeetpost";
export async function POST(request: Request) {
const { text } = await request.json();
await yeetpost({
connection: "<your-connection-slug>",
text,
});
return Response.json({ ok: true });
}Deploying on Vercel? Add YEETPOST_API_KEY under Project Settings, Environment Variables, so the server build has it as well as your machine.
4
Track your posts
Monitor all your posts from the yeetpost dashboard:
- Go to the Feed tab in the yeetpost dashboard
- View all posts sent via yeetpost, including status and timestamps
5
Review the security checklist
Review the Security Checklist to ensure your implementation is secure.
When a Bluesky post is refused
Each of these fails only the Bluesky item. Every other connection on the same request still goes out. The full vocabulary is in the errors reference.
| Code | Status | When |
|---|---|---|
| invalid_request | 400 | Text over 300 graphemes, in the post or in any thread segment |
| media_unsupported | 400 | More than 4 images, or an image over 1 MB |
| shape_unsupported | 400 | A firstComment was given. Bluesky has no first comment |
| unauthorized | 401 | The app password was revoked. Create a new one and reconnect |
| platform_rejected | 422 | The server said no, for example a duplicate post |
| internal_server_error | 500 | Our fault. Quote the req_id when you report it |
Bluesky FAQ
Why is my emoji-heavy Bluesky post accepted when it looks longer than 300?
The limit is graphemes, not code points. A flag or a skin-tone emoji is several code points and one grapheme, so it counts once. The check runs before anything is published.
My thread came back sent but only two replies are there. Why?
Bluesky cannot delete a half-published thread on our behalf, so a refused reply stops the chain and leaves what already went out standing. Read threadCount in the result instead of assuming the whole thread landed.
Does an image over 1 MB fail the whole post?
No. Only the Bluesky item comes back failed with media_unsupported. Every other connection named in the same request still goes out.
Where should this run in a Next.js app?
On the server: a route handler, a server action or a cron job. The API key has to stay there, so read it from process.env and never put it behind a NEXT_PUBLIC name, which would ship it to the browser.
Related guides
Related resources
Copy this guide (with your values) for use with LLMs or sharing with colleagues.