Posts today
POST to a channel webhook — genuinely live now.
Discord · Community
The Discord API, a webhook and you're posting
Broadcast to a Discord channel right now. Create a channel webhook, paste the URL, and PostMyIsh posts to it — no bot, no OAuth, no review.
Live nowWebhooksEmbeds2,000 chars
Live now · no reviewup to 2,000 charsDiscord Webhooks
publish-discord.ts
curl https://postmyish.com/api/v1/posts \
-H "Authorization: Bearer $POSTMYISH_KEY" \
-H "Content-Type: application/json" \
-d '{"caption":"🚀 v2 is live — full changelog in the thread","platforms":["discord"]}'201 · { id: "9f2c8b1e…", status: "published" }JSON
Why not raw?
Discord Webhooks is powerful — and painful
The official API can do this. It just makes you do a lot first. Here's what raw Discord publishing costs you, and what PostMyIsh absorbs.
Raw Discord API
With PostMyIsh
Setup
Build a bot, invite it, manage a gateway connection
One webhook URL — no bot at all
Auth
Bot token, intents, permission scopes
The webhook URL is the whole credential
Review
None — but you still wire the HTTP call
We POST it and read back the message id
Channels
One webhook per channel to manage
Connect a webhook per Discord account slot
Capabilities
Everything Discord supports, one endpoint
Post types, limits, and scheduling — all through the same POST /v1/posts call, formatted the way Discord expects.
Image embeds
Pass a media URL and we attach it as an embed.
2,000 characters
Discord's real message ceiling, respected on send.
Message id
We use ?wait=true so the real message id comes back.
Copy, paste, ship
Real calls, not pseudocode
Every snippet hits the live API — same base URL, Bearer auth, plain JSON. Add your key and it runs.
Publish to Discord now
One POST fans out to Discord. The response carries the id and status the moment it ships.
publish.txt
curl https://postmyish.com/api/v1/posts \
-H "Authorization: Bearer $POSTMYISH_KEY" \
-H "Content-Type: application/json" \
-d '{"caption":"🚀 v2 is live — full changelog in the thread","platforms":["discord"]}'How it works
Live in three steps, not three weeks
Connect Discord, call one endpoint, and we run the Discord Webhooks plumbing behind it.
Step 01
Connect the account
Link it once from the Accounts page through its official login. The credential is stored encrypted.
Step 02
POST /v1/posts
Send one caption and the platform id. Add schedule_at to queue it, or media for a URL.
Step 03
We handle the rest
Container flows, token refresh, rate limits, and the real post id — all on our side.
Straight talk: Fully live with no app review — a channel webhook is the entire setup. Great for changelogs, ships, and community broadcasts today.
One API, eleven more
Discord is one entry in the same array
Add another id to platforms and the identical call posts there too. One request already covers Discord, Telegram, and X — no second integration.
Discord API FAQ
The honest answers
What's real, what needs review, and what Discord itself requires — no hand-waving.
Is this really live?
Yes. A Discord webhook needs no bot, OAuth, or review — paste the URL and a publish appears in the channel immediately.
How do I get a webhook URL?
In Discord: channel → Edit → Integrations → Webhooks → New Webhook → Copy URL. Paste it when connecting.
Can I post images?
Yes — pass a media URL and we attach it as an image embed on the message.
Do I get a message id?
Yes — we call the webhook with ?wait=true, so Discord returns the created message and we store its id.
Ready to post your ish everywhere?
Connect your accounts, write one caption, and be live on every feed in minutes. The free plan is genuinely free.