Follow these steps to connect Discord message, send from TypeScript, and track delivery.
Discord posting goes through a webhook you create yourself in the channel's settings. There is no bot to install and no OAuth dance: Discord hands you a URL, yeetpost calls it once to read back the webhook's name and channel, and messages land under the name and avatar you gave it. The URL is a credential, so treat it like an API key. In plain TypeScript this is a few lines in any Node process: a worker, a one-off script or a deploy step that already knows what to say.
| How you connect | A webhook URL of the form https://discord.com/api/webhooks/<id>/<token> |
|---|---|
| Connection slug | discord for the first channel, then a slug built from the webhook name |
| Text limit | 2000 characters, counted in code points |
| Images | Up to 5 per post, png, jpeg, gif or webp, 8 MB each |
| Alt text | Yes, sent as each attachment's description |
| Threads | No, a webhook cannot reply to its own message |
| First comment | No, LinkedIn only |
| Scheduling | Yes |
| Permalink | https://discord.com/channels/<server>/<channel>/<message> |
| Per-post fee | None |
Connect a Discord channel to yeetpost with a webhook you create yourself:
The URL has to be a real Discord webhook URL, so https://discord.com/api/webhooks/<id>/<token>. Anyone holding it can post to that channel, so treat it like an API key. To revoke it, delete the webhook in Discord.
Paste your connection slug here and we'll auto-fill it into the code examples below.
Get your API key from the yeetpost dashboard:
Paste your API key here and we'll auto-fill it into the code examples below.
Install the yeetpost package:
npm install yeetpostExport your API key so the process can read it:
export YEETPOST_API_KEY=<your-api-key>Send a post:
import { yeetpost } from "yeetpost";
await yeetpost({
connection: "<your-connection-slug>",
text: "Hello from yeetpost!",
});To post to several connections in one call, use the JSON endpoint. It answers with one result per connection and accepts an Idempotency-Key, so a retry cannot double-post:
const response = await fetch("https://api.yeetpost.com/api/v2/posts", {
method: "POST",
headers: {
"x-api-key": process.env.YEETPOST_API_KEY!,
"content-type": "application/json",
"Idempotency-Key": crypto.randomUUID(),
},
body: JSON.stringify({
text: "Hello from yeetpost!",
connectionSlugs: ["<your-connection-slug>"],
}),
});
const { results } = await response.json();
for (const result of results) {
console.log(result.connectionSlug, result.status, result.url);
}Read each result.status rather than the HTTP status alone: one connection can fail while the rest go out.
Monitor all your posts from the yeetpost dashboard:
Review the Security Checklist to ensure your implementation is secure.
Each of these fails only the Discord 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 2000 code points |
| media_unsupported | 400 | The server refused the image, usually its own upload limit |
| shape_unsupported | 400 | A thread or a firstComment was given. Discord has neither |
| platform_rejected | 422 | The webhook is gone, is no longer allowed to post, is rate limited past 5 seconds, or Discord refused the message |
| internal_server_error | 500 | Our fault. Quote the req_id when you report it |
A webhook posts messages, it cannot reply to one. Ask for a thread on a Discord connection and that item is refused with shape_unsupported, while the connections that do have threads, X, Bluesky, Telegram and Mastodon, still go out.
Yes. One webhook per channel and one connection per webhook. Name them all in connectionSlugs and the same call fans out to every channel.
Somebody deleted it in Discord, or the channel's permissions changed. Posts come back platform_rejected with a message naming which of the two it was. Create a new webhook and paste the new URL.
No. It shows the name and the avatar you gave the webhook when you created it in Discord. Change them there and every later message follows.
It is a thin wrapper over the same HTTP endpoint, so anywhere you have fetch and can keep a secret it works. Do not run it in a browser bundle: the key would be readable by anyone loading the page.
Copy this guide (with your values) for use with LLMs or sharing with colleagues.