Skip to main content

Discord Conversions API

Send server-side application events to Discord for conversion tracking and Quest fulfillment.

API Documentation: Discord Application Events API specification.

Configuration​

To configure Discord Conversions API as a destination, you'll need a bot token for the Event Source Application that Discord created for your title or game.

Authentication​

This connector authenticates with Discord bot-token authentication:

Authorization: Bot <bot_token>

Connection validation does not send a synthetic event. Discord token or payload problems are reported during the first run that sends real events.

Events​

Each source record maps to one Discord application event. Extract sends events to:

POST https://discord.com/api/v9/applications/@me/events

@me is literal. Discord resolves it from the bot token's application.

For Discord app event types 1 and 2, include a non-empty app object. Discord rejects those events with app is required for app events when app metadata is missing.

Delivery Behavior​

  • Extract sends { "events": [...] }.
  • Discord may return HTTP 200 with a failures array. Extract counts those entries as failed records and logs their error messages.
  • HTTP 4xx and 5xx responses fail the batch unless continue_on_errors is enabled.
  • User identifiers are removed from network log payloads.

Data Contract​

Loading ....