canonical: https://jentic.com/apis/toornament.com/toornament

# Toornament API

The Toornament API provides programmatic access to manage esports tournaments, including creating tournaments, managing registrations, participants, matches, and standings. The API exposes 10 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically create a tournament, list tournaments. Covers 10 operations with apiKey, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create a tournament
- List tournaments
- Get a tournament
- Update a tournament
- Delete a tournament

## Use cases

### Developer Tools Operations

Use the Toornament API to perform developer tools operations programmatically. The API provides 10 endpoints covering core functionality including create a tournament, list tournaments, get a tournament.

Example prompt: Call POST /tournaments to create a tournament

### Automated CustomFields Management

Automate customfields operations by combining multiple Toornament API endpoints. Agents can list tournaments and then get a tournament in a single workflow.

Example prompt: Call GET /tournaments to list tournaments, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Toornament API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, oauth2 tokens manually.

Example prompt: Search Jentic for 'create a tournament', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/tournaments` | Create a tournament |
| GET | `/tournaments` | List tournaments |
| GET | `/tournaments/{id}` | Get a tournament |
| PATCH | `/tournaments/{id}` | Update a tournament |
| DELETE | `/tournaments/{id}` | Delete a tournament |
| GET | `/tournaments/{tournament_id}/registrations` | List registrations |
| GET | `/tournaments/{tournament_id}/participants` | List participants |
| GET | `/tournaments/{tournament_id}/custom-fields` | List custom fields |

## Key resources

- **CustomFields** — Operations related to CustomFields
- **Disciplines** — Operations related to Disciplines
- **Participants** — Operations related to Participants
- **Registrations** — Operations related to Registrations
- **Standings** — Operations related to Standings

## Why Jentic

- **Setup:** Wiring Toornament by hand means sending its API-key request header alongside an OAuth2 token, tracking the organizer v2 host, and coding your own request handling for tournament and participant management. Through Jentic you install once, import the Toornament API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Toornament puts the tournament id in the URL path (`/tournaments/{id}`), so a rule can pin your agent to one tournament and the operations it needs there. You choose which operations it may call, so destructive ones like deleting a tournament are not included unless you add them.
- **Credential handling:** Your Toornament key and OAuth2 token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a tournament' or 'list participants', and Jentic returns the matching Toornament operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Toornament API use?

The Toornament API uses apiKey, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a tournament with the Toornament API?

Yes. Use the POST /tournaments endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Toornament API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a tournament through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a tournament'. Jentic returns the matching Toornament API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Toornament API have?

The Toornament API exposes 10 endpoints covering customfields, disciplines, participants operations.

### Can I limit what my agent is allowed to do with the Toornament API?

Yes. Because you run Jentic One yourself, your own rules decide which Toornament operations and credentials the agent may use. Toornament puts the tournament id in the URL path (`/tournaments/{id}`), so you can pin the agent to a single tournament and to just the operations it needs there, such as GET /tournaments to list or GET `/tournaments/{tournament_id}/participants` to read entrants. Destructive calls like DELETE `/tournaments/{id}` stay off unless you explicitly allow them.