Toornament API

Name: Toornament API API
Brand: Toornament API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey, oauth210 EndpointsREST

For Agents

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

Connect the Toornament API to your agent

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Toornament API API.

Create a tournament

List tournaments

Get a tournament

Update a tournament

Delete a tournament

GET STARTED

Start building with Toornament API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Toornament API 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

Key Endpoints

10 endpoints — the toornament api provides programmatic access to manage esports tournaments, including creating tournaments, managing registrations, participants, matches, and standings.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Toornament API apiKey, oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a tournament') and Jentic returns the matching Toornament API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Toornament API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Toornament API 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.