API Demo

Name: API Demo API
Brand: API Demo
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationGeocodingbasic2 EndpointsREST

For Agents

Programmatically get-statistics-players-in-entity-session-by-sessionid, get-events-by-eventname-player-in-entity-session-by-sessionid. Covers 2 operations with basic authentication.

Quickstart

Get started with API Demo in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get-statistics-players-in-entity-session-by-sessionid"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with API Demo API.

get-statistics-players-in-entity-session-by-sessionid

get-events-by-eventname-player-in-entity-session-by-sessionid

Integrate API Demo into automated workflows

Query and filter API Demo records by parameters

Monitor API Demo operational status and events

GET STARTED

Start building with API Demo API

Explore with Jentic

View OpenAPI Document

Use for: I need to get-statistics-players-in-entity-session-by-sessionid, I want to get-events-by-eventname-player-in-entity-session-by-sessionid, Get the current status of API Demo resources, List all records from API Demo

Not supported: Does not handle payments, communications, or crm — use for maps and geolocation only.

Jentic publishes the only available OpenAPI document for API Demo, keeping it validated and agent-ready.

Basic API description for statistics and events. In case of a live session, fire requests every X seconds (depending on your needs) to get updated live data. player_id: Kinexon internal, unique identifier league_id: Secondary identifier. Can be set to 3rd party player identifier. Units: Speeds: meters/second Accelerations: meters/second^2 Distances/Coordinates: . The API exposes 2 endpoints secured with basic authentication.

Use Cases

Patterns agents use API Demo API for, with concrete tasks.

★ Maps and Geolocation Operations

Use the API Demo to perform maps geolocation operations programmatically. The API provides 2 endpoints covering core functionality including get-statistics-players-in-entity-session-by-sessionid, get-events-by-eventname-player-in-entity-session-by-sessionid.

Call GET /statistics/players/in-entity/session/{sessionId} to get-statistics-players-in-entity-session-by-sessionid

Data Retrieval and Monitoring

Query API Demo resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary API Demo endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call API Demo 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 basic tokens manually.

Search Jentic for 'get-statistics-players-in-entity-session-by-sessionid', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — basic api description for statistics and events.

METHOD

PATH

DESCRIPTION

GET

/statistics/players/in-entity/session/{sessionId}

get-statistics-players-in-entity-session-by-sessionid

GET

/events/{eventName}/player/in-entity/session/{sessionId}

get-events-by-eventname-player-in-entity-session-by-sessionid

GET

/statistics/players/in-entity/session/{sessionId}

get-statistics-players-in-entity-session-by-sessionid

GET

/events/{eventName}/player/in-entity/session/{sessionId}

get-events-by-eventname-player-in-entity-session-by-sessionid

Why though Jentic?

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

Credential isolation

API Demo basic 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., 'get-statistics-players-in-entity-session-by-sessionid') and Jentic returns the matching API Demo operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct API Demo 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

Here

Alternative maps geolocation API

Choose Here when you need a different approach to maps geolocation operations

Alternative

Tomtom

Alternative maps geolocation API

Choose Tomtom when you need a different approach to maps geolocation operations

Complementary

Googleapis

Complementary maps geolocation API

Choose Googleapis when you need a complementary approach to maps geolocation operations

FAQs

Specific to using API Demo API through Jentic.

What authentication does the API Demo use?

The API Demo uses HTTP Basic authentication with username and password. 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 get-statistics-players-in-entity-session-by-sessionid with the API Demo?

Yes. Use the GET /statistics/players/in-entity/session/{sessionId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the API Demo?

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 get-statistics-players-in-entity-session-by-sessionid through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get-statistics-players-in-entity-session-by-sessionid'. Jentic returns the matching API Demo operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the API Demo have?

The API Demo exposes 2 endpoints covering events, statistics operations.