For Agents
Programmatically create a tournament, list tournaments. Covers 10 operations with apiKey, oauth2 authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Toornament API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftoornament.com%2Ftoornament" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftoornament.com%2Ftoornament" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Toornament API.
Create a tournament
List tournaments
Get a tournament
Update a tournament
GET STARTED
Use for: I need to a tournament, I want to tournaments, Search for a tournament, Find all a tournament
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
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.
Delete a tournament
Patterns agents use Toornament API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'create a tournament', load the operation schema, and execute with Jentic-managed credentials
10 endpoints — the toornament api provides programmatic access to manage esports tournaments, including creating tournaments, managing registrations, participants, matches, and standings.
METHOD
PATH
DESCRIPTION
/tournaments
Create a tournament
/tournaments
List tournaments
/tournaments/{id}
Get a tournament
/tournaments/{id}
Update a tournament
/tournaments/{id}
Delete a tournament
/tournaments/{tournament_id}/registrations
List registrations
/tournaments/{tournament_id}/participants
List participants
/tournaments/{tournament_id}/custom-fields
List custom fields
/tournaments
Create a tournament
/tournaments
List tournaments
/tournaments/{id}
Get a tournament
/tournaments/{id}
Update a tournament
/tournaments/{id}
Delete a tournament
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Toornament API through Jentic.
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.
/tournaments/{tournament_id}/registrations
List registrations
/tournaments/{tournament_id}/participants
List participants
/tournaments/{tournament_id}/custom-fields
List custom fields