Source type

Discord Event Source Configuration Reference

Configure a dedicated FastHook source for signed Discord application lifecycle, entitlement, lobby, and Social SDK notifications.

DISCORD_EVENTSPOSTApplication Public KeyCommunication
Discord Webhook Events documentationAll source types
Discord sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.DiscordProviderPOSTSetup + eventsFastHookSource URLDISCORD_EVENTSProvider credentialPING/204Verify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.Provider setupValidate firstPING / 204

Discord Event Webhooks configuration

Create a Discord Event Webhooks source, keep POST enabled, and provide the configured Application Public Key values for provider signature. FastHook uses these settings to validate each Discord delivery before it enters the routing workflow.

Source Type

DISCORD_EVENTS

Allowed methods

POST

Authentication

Provider signature

Credential fields

Application Public Key

Discord Event Webhooks source config
{
  "type": "DISCORD_EVENTS",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "DISCORD_EVENTS",
      "public_key": "hex-application-public-key"
    },
    "allowed_http_methods": ["POST"]
  }
}

PING validation before event delivery

  1. Discord sends a signed Event Webhook PING payload with type 0.
  2. FastHook verifies the Ed25519 signature and returns the required empty 204 response.
  3. After validation succeeds, Discord sends signed event payloads with type 1; FastHook queues them and acknowledges each delivery with 204.

Discord Event Webhooks request contract

FastHook verifies the Ed25519 signature over timestamp + raw body using the Discord application public key before acknowledging or queueing the request.

POST

Special response: Discord Event Webhook PING payloads with type 0 receive an empty 204 response. Verified event payloads are queued and also acknowledged with 204.

Discord headers

Preserve x-signature-ed25519, x-signature-timestamp when sending Discord test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

x-signature-ed25519

Ed25519 signature in hex.

x-signature-timestamp

Timestamp concatenated with the raw body before verification.

Discord setup

  1. In Discord Developer Portal > General Information, copy the Application Public Key into FastHook.
  2. In Discord Developer Portal > Webhook Events, set Webhook Events Endpoint URL to the generated FastHook Source URL.
  3. Enable Events in the Discord Developer Portal and subscribe only to the event families your application needs.
  4. Use a separate source from Discord Interactions because the two endpoint protocols assign different meanings to payload type values.
  5. Confirm the signed type 0 endpoint test receives an empty HTTP 204 response.

Discord routing hints

  • Discord Event Webhooks route by event.type, application_id, installation context, entitlement id, lobby id, or user id.
  • Keep Event Webhooks on a separate source from Interactions because payload type values have different protocol meanings.

Continue with Discord Event Webhooks