Integrations

Discord Webhooks Guide

Discord interaction webhooks power slash commands, components, modals, bot workflows, and community automation. The receiver has to verify every request and answer the initial PING validation correctly before normal interactions can flow.

FastHook verifies Discord Ed25519 signatures with the application public key, returns the required PING response, stores request evidence, and routes accepted interaction payloads to destinations.

Discord interaction webhook ingress with signature verification.
Verify Discord at ingress, then route interaction families to the services that own command handling.

Discord headers

  • x-signature-ed25519: Ed25519 signature in hex.
  • x-signature-timestamp: timestamp concatenated with the raw body before verification.

Create a Discord source

Create Discord source
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"]
    }
  }'

Routing strategy

  • Route command interactions to command handlers.
  • Route moderation or admin interactions to safer internal services.
  • Keep long-running work asynchronous so Discord receives a fast accepted response path.
  • Use replay for debugging failed internal automations, not for re-running unsafe side effects blindly.

Related guides