Skip to content

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.

From the channel's settings: Integrations, Webhooks, Copy Webhook URL.

23 / 2,000
optional

Shown as the sender of this one message. Empty keeps the webhook's own name.

Check URL posts nothing to the channel.

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.

FieldWhat it doesLimit
contentThe message textUp to 2,000 characters
usernameReplaces the webhook's name for this one message
embedsRich 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_mentionsWhich mentions may notify. The tester sends an empty list unless you tick the box, so a test pings no one.
thread_idIn 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.

StatusMeaning
200The message was saved. With wait=true the body is the message itself.
204The request was accepted. This is the answer without wait=true.
400The 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).
401Invalid Webhook Token (50027). The webhook exists, but the token in the URL is not its token.
404Unknown Webhook (10015). No webhook has this id: it was deleted, or the URL is wrong.
429Rate limited. The body's retry_after is the number of seconds to wait before sending again.
5xxAn 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

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.

More free tools