Discord Source

When to use this source type

Choose the DISCORD source type when Discord is the system sending webhook requests into FastHook. The source type keeps sender-specific setup close to the source: accepted methods, verification headers, challenge handling, and the exact credential fields are documented together so operators do not need to translate a generic HMAC form into a provider-specific contract.

FastHook verifies the source before accepted traffic is queued. A valid request is stored with verified: true, then connections route it to destinations. A bad signature, wrong token, or missing provider header is rejected as SOURCE_AUTH_FAILED. A method outside the allowed set is rejected as SOURCE_METHOD_NOT_ALLOWED.

FastHook configuration

In the dashboard, create a source, set Source Type to Discord, keep Authenticate enabled when verification is required, and fill the fields below.

{
  "type": "DISCORD",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "DISCORD",
      "public_key": "hex-application-public-key"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Discord production",
  "type": "DISCORD",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "DISCORD",
      "public_key": "hex-application-public-key"
    },
    "allowed_http_methods": [
      "POST",
      "PUT",
      "PATCH",
      "DELETE"
    ]
  }
}'

PING validation before interaction callbacks

Some providers do not send normal event payloads first. They validate the callback URL or subscription contract before delivery starts, so keep the methods listed below enabled during setup.

1. Discord sends a signed PING interaction to the endpoint URL.
2. FastHook verifies the Ed25519 signature and returns the required PONG response.
3. After validation succeeds, Discord sends normal signed interaction callbacks.

HTTP methods

This source accepts only the methods listed below. Keep the set narrow so provider mistakes and accidental test calls are visible as rejected requests instead of being silently accepted.

Special response: Discord PING payloads receive JSON { type: 1 }.

Headers and verification

FastHook verifies the provider-specific values below before the request is accepted. The comparison is done against the raw inbound request body or the exact provider-specific signing input described here.

FastHook verifies the Ed25519 signature over timestamp + raw body using the Discord application public key.

Provider setup checklist

1. Set the Discord Interactions Endpoint URL to the generated FastHook Source URL.
2. Copy the application public key from Discord into FastHook.
3. Use the Requests view to confirm the first PING is answered before expecting normal interaction events.
4. Open Discord interactions security documentation when you need the provider's event list, dashboard steps, or retry policy.

Supported event types and payload shape

FastHook stores the original Discord request before routing so filters, transformations, retries, and replay decisions can use the same provider evidence. Use stable headers and payload fields for routing rather than relying on receiver-side logs alone.

• Discord interaction callbacks route by interaction type, command name, guild id, or channel id.
• The initial PING/PONG validation must succeed before normal interaction traffic is accepted.

Troubleshooting

• No request appears: the provider is not calling the generated FastHook Source URL, the source URL was copied before saving, or the provider has not completed its setup validation.
• 405 method rejected: the provider sent a method outside POST, PUT, PATCH, DELETE. Edit the source only if the provider documentation says that method is expected.
• 401 source auth failed: check the configured FastHook field, the provider signing secret, and the header names listed on this page.
• Signature mismatch: make sure the provider signs the same public Source URL it calls and that no proxy, parser, or manual resend changed the raw request body before FastHook received it.

Discord source FAQ

Related docs

• Sources
• Source authentication
• Webhook signature validation
• Custom source responses
• Provider event routing