Custom fields
List the custom fields used when registering for a tournament.
Participant API Legacy
The Participant API is in legacy mode. Global access to participant data will soon be forbidden and
the Participant API deprecated. If you start a new project or are using the Participant API to
access your own competition data, you have to use the current API (previously named Organizer API).
API reference ›
Overview
The Participant API allows you to register users for tournaments that you do not organize. If you want to register users for your tournaments, please use the Organizer API.
The Participant API is appropriate if you want to:
- Allow users to register for tournaments that you do not organize.
- Allow users to modify their registrations.
- Allow users to check in to their tournament.
The API is divided into several sections. Each section provides the different access points related to a single entity.
Sections
- Disciplines
Access to discipline-related metadata in order to implement a registration that integrates the specificities of several disciplines. If you only want to implement a single discipline, you should not use this section and directly implement the specificities of the discipline in your application.
- Matches
Access matches.
- Participants
Manage the user participation in tournaments. Allow the participant to check in to the tournament.
- Registrations
Manage the user registrations in tournaments.
- Tournaments
Access detailed tournament information including information for the players.
OpenAPI 3.0 specification
We also provide you with the OpenAPI 3.0 specification schema of our API. This specification allows us to describe our API with a standard format. Developers can import these files into interactive REST clients (such as Postman or Insomnia) or use these files to generate code and quickly perform calls to our API.
You can find more information on the OpenAPI initiative website.
You can also find a list of tools developed for OpenAPI on the OpenAPI tools website.