How do I test a Discord webhook?

Paste your webhook URL into a webhook tester tool and click Check. The tool will validate the URL, show you the webhook's name and avatar, and let you send a test message to verify it's working. You can also test manually by sending a POST request with curl or Postman.

How do I create a Discord webhook?

Go to your Discord server settings, click Integrations, then Webhooks, and click New Webhook. Give it a name, select the channel it should post to, and click Copy Webhook URL. You can then use this URL to send messages to that channel from external services.

Is it safe to paste my webhook URL into a tester?

Webhook URLs should be treated like passwords - anyone with the URL can send messages to your channel. Only use trusted webhook testers. Our tool proxies the request through our server but never stores or logs your webhook URL. If you suspect a webhook URL has been compromised, delete it in Server Settings > Integrations > Webhooks.

Why is my Discord webhook not working?

Common reasons: the webhook was deleted, the channel it's linked to was deleted, the webhook token expired or was regenerated, or you're hitting Discord's rate limit (30 requests per minute per webhook). Use a webhook tester to check if the URL is still valid.

Discord Webhook Tester

Test your Discord webhook in seconds. Paste the URL, validate it, and send a test message to make sure it works.

What is a Discord webhook?

A Discord webhook is a unique URL that lets you send messages to a specific Discord channel without needing a bot. Webhooks are commonly used for GitHub notifications, server monitoring alerts, CI/CD pipeline updates, and custom integrations. Each webhook has its own name, avatar, and is linked to a specific channel.

How to create a Discord webhook

Open your Discord server and go to Server Settings
Navigate to Integrations > Webhooks
Click New Webhook
Set a name and select the target channel
Click Copy Webhook URL
Paste the URL into the tester above to verify it works

How this tester works

Paste your webhook URL and click Check. The tool validates the URL against Discord's API and shows the webhook's name, avatar, and linked channel. If valid, you can type a custom message and send it through the webhook to confirm it's working. Your webhook URL is proxied through our server for security (browsers can't call Discord's API directly due to CORS) but is never stored or logged.

Common Discord webhook error codes

When a webhook request fails, Discord returns an HTTP status with a JSON body containing a numeric code and message. These are the ones you will actually hit:

400 Bad Request - Malformed JSON body, embed exceeds 6,000 total characters, or a field length is over its limit. Validate your payload locally before sending.
401 Unauthorized - Webhook token is wrong or has been regenerated. Regenerating a webhook in Server Settings invalidates the old URL immediately.
404 Not Found - The webhook was deleted, the channel was deleted, or the URL contains a typo. Re-copy the URL from Server Settings > Integrations.
429 Too Many Requests - You hit a rate limit. Discord returns a retry_after field (in seconds) telling you when to retry. Honor it.
Code 50027 (Invalid Webhook Token) - Same root cause as 401, returned when the token segment of the URL is corrupted or truncated.
Code 50006 (Cannot send empty message) - Your payload has no content, no embeds, and no files. At least one is required.
Code 50035 (Invalid Form Body) - Most common cause: embed.color sent as a hex string instead of a decimal integer. Convert #9B59B6 to 10181046 before sending.

Discord webhook rate limits

Discord enforces per-webhook and per-channel rate limits, and the exact bucket sizes are determined server-side and surfaced in response headers rather than as a fixed number. Every successful response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset-After - read these to schedule your next request, do not hard-code a fixed rate. A 429 response body also carries a retry_after value (seconds). For high-volume integrations (build pipelines, log aggregation), batch multiple events into a single message - one webhook call can carry up to 10 embeds with up to 6,000 combined characters per embed, which is usually enough to consolidate a burst of events into one request.

Webhook security best practices

A webhook URL is a bearer credential. Anyone with the full URL can post to your channel as the webhook bot, with no further authentication. Treat it like a password:

Never commit webhook URLs to a public Git repository. GitHub's secret scanning detects and revokes leaked Discord webhooks automatically, but only after they have already been exposed.
Store webhook URLs in environment variables or a secrets manager, not in source code or config files checked into version control.
If a webhook is exposed, delete it in Server Settings > Integrations > Webhooks immediately. Recreating it generates a new token; the old URL stops working.
For client-side use (a browser app posting to Discord), proxy the call through your own backend so the URL never reaches the user's browser. A leaked URL from a browser app is a vandalism magnet.
Discord webhooks ignore the @everyone and @here mentions unless allowed_mentions explicitly permits them. Set "parse": [] to disable all mention pings if you do not need them.

Manual webhook test with curl

If you would rather test from the terminal, the minimal payload is one content field. A successful POST returns HTTP 204 with an empty body, or HTTP 200 with the created message JSON if you append ?wait=true to the URL. Use ?wait=true when you need the message ID back (for example, to edit or delete the message later through the /webhooks/<id>/<token>/messages/<message_id> endpoint).

More free Discord tools

Snowflake Checker - Check any Discord account's age
Colored Text Generator - Create colored messages with ANSI codes
Message Length Counter - Check if your message fits Discord's limits
Color Role Previewer - Preview role colors on all Discord themes