Skip to content
TAP Docs

API keys & webhooks

On Developer (/dashboard/developer) you manage API keys and webhooks for this tournament.

API keys

Section titled “API keys”

“Create key” → give it a name, then pick a scope:

  • Read & write — full access
  • Read only — read access only
  • Scores only — may only enter results

Right after creating a key, the full secret is shown once — “Copy your secret key now — for security it won’t be shown in full again.” After that you only see a masked version. In the table you can reveal a key’s value once per row, revoke it (block it), or delete it permanently.

Webhooks

Section titled “Webhooks”

“Add webhook endpoint” → target URL, then the format:

  • TAP JSON — POST body {event, tournament_uuid, data}, optionally with an X-TAP-Secret header for verification.
  • Discord — for a Discord channel webhook; no secret is sent here, Discord has no use for one.

Then you pick, via checkboxes, which events should be reported:

match.scheduled, match.checkin, match.called, match.started, score.created, match.finished, match.reported, match.disputed, veto.completed, bracket.updated, stage.completed, game.updated.

Each webhook can be tested, disabled, or deleted individually.