Discord webhook tester

Send a test message or embed

{
  "content": "Test message from webhook-toolkit.com ✅",
  "embeds": [
    {
      "title": "Deployment succeeded",
      "description": "Build `#1287` shipped to production in 42s.",
      "color": 5793266,
      "fields": [
        {
          "name": "Environment",
          "value": "production",
          "inline": true
        },
        {
          "name": "Commit",
          "value": "a1b2c3d",
          "inline": true
        }
      ]
    }
  ]
}

curl -X POST "https://discord.com/api/webhooks/ID/TOKEN?wait=true" \
  -H "Content-Type: application/json" \
  -d '{"content":"Test message from webhook-toolkit.com ✅","embeds":[{"title":"Deployment succeeded","description":"Build `#1287` shipped to production in 42s.","color":5793266,"fields":[{"name":"Environment","value":"production","inline":true},{"name":"Commit","value":"a1b2c3d","inline":true}]}]}'

await fetch("https://discord.com/api/webhooks/ID/TOKEN?wait=true", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "content": "Test message from webhook-toolkit.com ✅",
  "embeds": [
    {
      "title": "Deployment succeeded",
      "description": "Build `#1287` shipped to production in 42s.",
      "color": 5793266,
      "fields": [
        {
          "name": "Environment",
          "value": "production",
          "inline": true
        },
        {
          "name": "Commit",
          "value": "a1b2c3d",
          "inline": true
        }
      ]
    }
  ]
}),
});

Anatomy of a Discord webhook URL

Every Discord webhook is fully identified by two values baked into its URL. There is no separate API key and no signature — whoever has the URL can post, which is exactly why you should treat it like a password and regenerate it if it leaks.

https://discord.com/api/webhooks/1234567890123456789/aBcDeF...68-char-token
                                 └────────┬────────┘ └──────────┬──────────┘
                                    webhook id (snowflake)   webhook token

Where to find it: Server Settings → Integrations → Webhooks → New Webhook, then Copy Webhook URL. You need the Manage Webhooks permission on the target channel. The older discordapp.com host and canary./ptb. subdomains resolve to the same API.

The errors you will actually hit

Discord replies with a numeric HTTP status and a JSON code field. The JSON code is the precise one — two different problems can both surface as a 400.

Hard limits (they reject, they don't truncate)

These are enforced by Discord — go over and the whole message is rejected with a 400, nothing is silently cut. The 6000-character total is the one that bites: it sums every text field across all embeds in a single message.

Copy-paste from your own code

The tool above already emits curl and Node for your exact payload. Here are the canonical forms to keep in a script — note the decimal color and ?wait=true.

curl -X POST "https://discord.com/api/webhooks/ID/TOKEN?wait=true" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Deploy finished",
    "username": "CI",
    "embeds": [{
      "title": "Build #1287",
      "description": "Shipped to production in 42s",
      "color": 5793266,
      "fields": [
        { "name": "env", "value": "production", "inline": true },
        { "name": "commit", "value": "a1b2c3d", "inline": true }
      ]
    }]
  }'

const res = await fetch(process.env.DISCORD_WEBHOOK + "?wait=true", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    content: "Deploy finished",
    embeds: [{ title: "Build #1287", color: 0x5865f2 }], // hex literal → int
  }),
});
if (res.status === 429) {
  const { retry_after } = await res.json();
  await new Promise((r) => setTimeout(r, retry_after * 1000));
}

Capture what flows INTO Discord

Sending is only half the loop. When you wire GitHub → Discord, an alerting service, or a cron to a Discord webhook and the message never shows up, you need to see the exact bytes and headers the source is producing. Point that source at a Receiver URL first, inspect the raw request, then swap in the real Discord URL once it looks right.

Questions fréquentes