Fix Discord Webhook Errors: Every Message and Code

Every common webhook error, quoted exactly

Discord answers a failed request with an HTTP status and a JSON body such as {"message": "Unknown Webhook", "code": 10015}. The message is the text to search for; the code is the stable number behind it. Find yours in the table, then read the matching section below for the details.

Components V2 errors inside Invalid Form Body

A Components V2 payload that Discord rejects usually comes back as Invalid Form Body with a second, more specific error nested under the field at fault. The top-level message is the same for every validation failure; the nested code is what tells you what to change. This response comes from sending content together with the V2 flag:

{
  "message": "Invalid Form Body",
  "code": 50035,
  "errors": {
    "content": {
      "_errors": [
        {
          "code": "MESSAGE_CANNOT_USE_LEGACY_FIELDS_WITH_COMPONENTS_V2",
          "message": "The 'content' field cannot be used when using MessageFlags.IS_COMPONENTS_V2"
        }
      ]
    }
  }
}

The same errors in discord.js and discord.py

Bot libraries wrap the same response in their own exception, so the text in your terminal looks different from the raw JSON while carrying the same two facts. The number in brackets, or after “error code”, is the JSON code from the tables above; the text after the colon is Discord's message.

# discord.js — DiscordAPIError[code]: message
DiscordAPIError[50035]: Invalid Form Body
DiscordAPIError[10015]: Unknown Webhook
DiscordAPIError[50013]: Missing Permissions

# discord.py — status (error code: code): message
discord.errors.HTTPException: 400 Bad Request (error code: 50035): Invalid Form Body
discord.errors.NotFound: 404 Not Found (error code: 10015): Unknown Webhook
discord.errors.Forbidden: 403 Forbidden (error code: 50013): Missing Permissions

Find the status, code and failing field

First record whether you were sending a new post, restoring one, updating it or configuring a webhook. In DWEEB, the send error combines the response status with Discord's code and expands nested validation errors into readable paths. Keep those details together when diagnosing the failure.

For example, components[0].components[1].url means the URL on the second child inside the first top-level component. Array positions start at zero. Select that component in the builder and correct that field before changing the rest of the design. The editor's own issue list may already point to the same problem.

Discord webhook error codes and next steps

HTTP status and JSON code are separate fields, not interchangeable numbers. The table lists useful combinations and individual API codes; the actual response is the evidence. A status alone cannot tell you which field or resource failed.

Fix 400 Invalid Form Body in a Components V2 message

DWEEB's local validation catches supported layout and field constraints; Discord remains the final authority for current permissions, destination state and server-side rules. A clean local issue list narrows the investigation, but it cannot prove a remote post will succeed.

• Import the payload into the Discord message builder and resolve error-severity issues before another send.
• For a V2 design, place visible text inside Text Displays and remove legacy top-level content and embeds. Use the embed converter when the source is a legacy embed.
• Check that every Section has a button or thumbnail accessory, and inspect any empty media URLs, invalid link URLs or conflicting allowed-mentions settings named in the error.
• If your own code sends the export, use its JSON body as JSON. When uploading files with FormData, let the browser set the multipart Content-Type and boundary.

Why components disappear or buttons fail

When sending an exported design through your own webhook client, check the request URL as well as the payload. A person-created webhook needs with_components=true for Discord to respect its components. The JSON also needs the V2 flag. DWEEB's own send path supplies both; a script that copies only the components array can miss them.

A link button and a custom-ID button have different delivery requirements. If a static message works but an interactive control fails, review its setup badge and app-owned destination. A visually correct button does not create the application handler that responds to its click. The Components V2 guide explains the ownership boundary.

Diagnose restore and update separately from new sends

If sending a new message works but Restore fails, start with the message target. Copy its complete Discord link, select the webhook that originally posted it and inspect the optional Thread ID. Creating a new webhook does not transfer ownership of old posts. Follow the restore and update workflow before deciding to repost.

For forum and media channels, distinguish a new post title from an existing post's channel ID. In DWEEB, the Forum post fields create a post; the Send panel's Thread ID addresses an existing one. The forum and thread guide walks through both paths.

Handle rate limits, network failures and uncertain sends

On 429, wait for Discord's reported retry delay. DWEEB exposes that delay as a countdown. Stop other repeated sends using the same destination while you investigate, and consult the webhook limits guide for automation design.

A browser network error means DWEEB did not receive a readable response; it does not prove Discord rejected the message. Check the destination channel before sending again, then inspect connectivity and extensions that block discord.com. A lost response after a successful post can otherwise turn one intended announcement into duplicates.

When asking for help, share the operation, status, code and a redacted field error. Remove webhook tokens, message content and private identifiers from screenshots and network logs. Keep a local draft of the design so the diagnostic process does not become a rebuild.