Discord webhook tester
Paste a webhook URL, write a message, and send it. The request goes from your browser straight to Discord, and the answer is explained in plain words.
A webhook URL is a credential. This tool sends it to discord.com and nowhere else: nothing you type reaches webhooks.cc, and nothing is stored.
How a Discord webhook works
A Discord webhook is a URL that posts messages into one channel. It needs no bot and no login: the URL itself carries the webhook's id and a secret token, as in https://discord.com/api/webhooks/{id}/{token}. You create one in a channel's settings under Integrations, Webhooks, and copy its URL from there.
To post, send a POST request with a JSON body to that URL. Discord needs at least one of content, embeds, a file, components or a poll. The tester sends the fields below, and adds wait=true to the URL so that Discord answers with the message it saved; without it, Discord answers 204 with no body, and a message that could not be saved is not reported as an error.
| Field | What it does | Limit |
|---|---|---|
| content | The message text | Up to 2,000 characters |
| username | Replaces the webhook's name for this one message | |
| embeds | Rich blocks with a title, description, link and colour. The tester sends one. | Up to 10 per message; title 256 and description 4,096 characters; 6,000 characters across the text fields of all embeds |
| allowed_mentions | Which mentions may notify. The tester sends an empty list unless you tick the box, so a test pings no one. | |
| thread_id | In the URL's query string: posts into a thread of the webhook's channel. Keep it on the URL you paste and the tester passes it on. |
Source: Discord: Webhook resource, Message resource.
What Discord's answers mean
Discord answers a webhook request with an HTTP status and, on an error, a JSON body holding a message and a numeric code. These are the ones a webhook meets.
| Status | Meaning |
|---|---|
| 200 | The message was saved. With wait=true the body is the message itself. |
| 204 | The request was accepted. This is the answer without wait=true. |
| 400 | The body was refused: an empty message (code 50006), a field over its limit or malformed (50035, with the field named in errors), or JSON that could not be read (50109). |
| 401 | Invalid Webhook Token (50027). The webhook exists, but the token in the URL is not its token. |
| 404 | Unknown Webhook (10015). No webhook has this id: it was deleted, or the URL is wrong. |
| 429 | Rate limited. The body's retry_after is the number of seconds to wait before sending again. |
| 5xx | An error on Discord's side. These are rare; wait and send again. |
Source: Discord: Opcodes and status codes, Rate limits.
A webhook in a forum or media channel answers 400 (code 220001) unless the request names a thread: every message there belongs to one. Add ?thread_id= and the thread's id to the webhook URL to post in an existing thread, or send a thread_name in the body to start a new one (this tester does not).
Webhooks and interaction endpoints are different things
The webhook tested here is a URL you post to. Discord also sends requests the other way: slash commands and button presses go to your app's interactions endpoint, signed with Ed25519. Those are covered on the Discord webhooks page, which shows how to capture and inspect them.
Discord webhook questions
Paste the webhook URL into the tester above, write a message and press Send message. The message appears in the webhook's channel, and the page shows the status code and the body Discord answered with. From a terminal the same test is one POST request with a JSON body; the tester shows the matching curl command after each send.
Press Check URL. It sends a GET request to the webhook URL, which Discord answers without any other authentication: a working URL returns the webhook's name and its channel and server ids, a deleted webhook returns 404 Unknown Webhook, and a wrong token returns 401 Invalid Webhook Token. Nothing is posted.
404 with the message Unknown Webhook (code 10015) means Discord has no webhook with that id. Either it was deleted in the channel's Integrations settings, or the URL was mistyped or cut short. Create a new webhook and replace the URL wherever it is used. Discord's documentation asks that a webhook answering 404 is not used again, and temporarily restricts clients that keep trying.
You are being rate limited: the webhook has been used faster than Discord allows. The JSON answer carries retry_after, the number of seconds to wait before the next request, and the response headers X-RateLimit-Remaining and X-RateLimit-Reset-After say how many requests are left and when the limit resets. Wait that long and send again. Clients that keep sending into 401, 403 or 429 answers can be blocked for a while: Discord counts 10,000 such requests in 10 minutes as the limit.
The URL is a credential: anyone who has it can post to the channel. This page sends it to discord.com from your browser and nowhere else. There is no webhooks.cc server behind the tool, the page does not store what you type, and its analytics never record the fields. You can confirm this in your browser's network tab, which shows one request, to discord.com. If a webhook URL has leaked, delete the webhook in Discord and create a new one.
Give your app a webhooks.cc endpoint URL in place of the Discord webhook URL. Each message it would have posted is captured with its full JSON body, so you can read the content and embeds before anything reaches a channel. When the payload looks right, turn on forwarding to the Discord webhook URL to pass captured requests on to the channel.
See what your app sends before Discord does
This tester posts a message you write. To test the messages your code writes, point it at a webhooks.cc endpoint: every request is captured with its headers and JSON body, can be replayed, and can be forwarded on to the real Discord webhook or to your machine.