Getting Started

The Tournament Suite API is the programmable surface behind the same platform that powers public esports portals, organizer dashboards, and white-label tournament operations. It exposes tournament structure, participant management, registration flows, match results, circuits, and live operational data so you can integrate competitive programs into your own products and services.

The API is built for tournament organizers who need to automate large competitive programs, esports studios that want their own branded portals, agencies that operate events on behalf of publishers, and integration partners who embed bracket views, live standings, or registration flows into existing websites and applications. If your product needs structured tournament data — whether for internal operations or audience-facing features — this is the surface to build against.

To get started, sign up for an organizer account on the Tournament Suite Platform, create a project for your program, and open the developer dashboard inside that project. Each project has its own isolated set of API credentials and webhook endpoints, so you can build, test, and ship one program without affecting another. Your sandbox environment works a little differently: it's tied to your developer account rather than to a single project, so you have one active sandbox that you reuse across every project you operate.

Before you generate credentials

A few prerequisites are easy to miss on your first pass through the developer dashboard:

• Your project's plan must include API access. Generating an API key does not, by itself, guarantee that requests will succeed — your project's subscription plan needs to include API access as well. If it doesn't, keyed requests are rejected even with a valid key. Check your plan's included features before you start integrating.
• Rate limits vary by plan tier. The requests-per-minute ceiling for the API is not a single flat number across all projects — it scales with your subscription tier. See Rate Limits for details.
• API keys can be restricted to specific IP addresses. If you configure an IP allowlist on a key, requests from any other address are rejected. Leave it unrestricted while you're still developing, and lock it down once you know where production traffic will originate from.

Next step: Create your first project and generate API credentials

Documentation

• Overview — get access, pagination, response codes, webhooks, rate limits
• Security — authentication, authorization, scopes, OAuth 2
• Core Concepts — the data model: projects, tournaments, participants, matches, circuits
• Reference — quick start and full endpoint catalog