How to make a webhook in Discord
A Discord webhook is a channel-specific URL that lets external apps post messages to your server automatically, with no bot to write or host. You create one in a channel’s integration settings, name it, choose the channel it posts to, and copy the generated URL into the service you want to receive messages from.
The steps below walk through creating a Discord webhook from the desktop app.
-
First, open Discord and pick the server where you want to create your webhook.
-
Click the arrow next to your server name in the upper left corner and choose Server Settings from the drop down menu.
-
In the side bar, choose Integrations, then click on Create Webhook.

-
The Integrations > Webhooks window allows creating a new webhook.

-
Choose your preferred icon and name your webhook.

-
Pick the channel you want to post to from the drop down menu.

- Your webhook is ready! Click on the Copy Webhook URL button and a webhook URL will be copied to your pasteboard. You’ll need to enter this URL into the 3rd party service you’re receiving messages from.

The webhook URL has the following format, where example-hash is a unique hash that identifies your channel webhook:
https://discord.com/api/webhooks/example-hash
If for any reason you would like to delete the webhook, click on the Delete Webhook button.

Webhook Security
Please note that webhooks have been a common vulnerability for Discord servers. Be very careful about who has webhook permissions on your Discord server and guard the webhook URL closely. If a hacker gets your webhook URL, they will be able to post messages in your server while impersonating your team.
Create a Discord webhook on mobile
The mobile apps can do this too, and the URL they produce is identical to the one the desktop app generates. Open the server, tap its name at the top of the channel list to open the server menu, then tap Settings, Integrations, and Webhooks. Tap New Webhook, then tap the webhook that appears to rename it, choose the channel it posts to, and copy the URL.
You need the Manage Webhooks permission in that server either way, so if the Integrations entry is missing on mobile it is a permission problem rather than a limitation of the app.
Send a message to your Discord webhook
Discord webhooks accept an HTTP POST with a JSON body, and the only required field is content, the message text:
curl -X POST \
-H 'Content-Type: application/json' \
--data '{"content": "Hello from your app!"}' \
https://discord.com/api/webhooks/example-hash
Discord replies with 204 No Content and the message appears in the channel you picked. Send an embeds array instead of content when you want a title, a colored stripe, and labelled fields rather than plain text, which how to format a Discord webhook message covers field by field along with the size limits Discord enforces. Discord rate-limits each webhook without publishing a fixed number, and answers with 429 and a Retry-After header when you go over, so an app that fires often has to batch its messages or queue them behind a rate limit of its own. If you are pointing GitHub at a Discord webhook and the requests come back rejected, see webhook error 400 from GitHub to Discord.
Discord webhook quick reference
The details most integrations need, in one place:
| Detail | Value |
|---|---|
| URL format | https://discord.com/api/webhooks/{id}/{token} |
| Request | HTTP POST with a JSON body; content, embeds, or files must be present |
| Message limits | content up to 2,000 characters, up to 10 embeds per message |
| Success response | 204 No Content, or 200 with the created message when you append ?wait=true |
| Permission needed | Manage Webhooks on the server or channel |
| Rate limit | Per webhook, not published; on 429, wait for Retry-After |
Discord webhook vs Discord bot: what a webhook can and cannot do
A Discord webhook can only post into the one channel it was created for: text, up to ten embeds, file attachments, and a per-message username and avatar override. It cannot read messages, react, answer slash commands, or receive events. Anything that needs to listen or reply is a bot, which needs a bot token, a Gateway connection, and a process you host.
That split is why a webhook is the right tool for one-way notifications from CI, monitoring, forms, and GitHub. A webhook can still edit or delete the messages it posted through the same URL, and it can post into a thread if you append ?thread_id= with the thread’s ID. Creating webhooks from code instead of Server Settings is the one place a bot comes in: the create-webhook endpoint needs a bot token with the Manage Webhooks permission, after which the webhook itself works with no token at all. Discord’s webhook resource documentation lists every field the POST accepts.
Find an existing webhook URL
To get the URL again later, reopen Server Settings > Integrations > Webhooks, click the webhook, and use Copy Webhook URL. Discord does not display the token anywhere else, and there is no way to rotate it in place, so a URL that leaks has to be deleted and recreated.
Now that you have successfully created your first Discord webhook for a dedicated channel, you can use third-party applications to automate message posting to Discord.
You should also checkout our tutorial on how to send webhooks with Python.