Knx Sports And Media API Demo
Community OpenAPI document · agent-readyMaps GeolocationGeocodingbasic2 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
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.
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. <br><br> player_id: Kinexon internal, unique identifier<br> league_id: Secondary identifier. Can be set to 3rd party player identifier.<br><br> Units: <br> Speeds: meters/second <br> Accelerations: meters/second^2 <br> Distances/Coordinates: . The API exposes 2 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the API Demo to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Demo, 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.
1
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%2Fswaggerhub.knx-sports-and-media%2Fswaggerhub-knx-sports-and-media" | sh2
Step 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%2Fswaggerhub.knx-sports-and-media%2Fswaggerhub-knx-sports-and-media" | 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.
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
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 Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring API Demo by hand means encoding HTTP basic auth against sports-demo.kinexon.com and threading session ids through its statistics routes yourself. Through Jentic you install once, import API Demo from the API Directory, store the basic credentials once, and your agent calls it.
Permission scoping
API Demo puts the session id in the URL path (/statistics/players/in-entity/session/{sessionId}), so a rule can pin your agent to one session for reading player statistics and events. Both exposed operations are read-only, and you choose which of them the agent may call.
Credential isolation
Your API Demo basic credentials 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 'get player statistics for a session' or 'get events for a player in a session', and Jentic returns the matching API Demo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.
Can I limit what my agent is allowed to do with the API Demo?
Yes. Because you run Jentic One yourself, your own rules decide which API Demo operations and credentials the agent may use. Both exposed operations are read-only, so you can allow just one, such as GET /statistics/players/in-entity/session/{sessionId} for player statistics, while withholding the events endpoint. Since the session id lives in the URL path, you can also pin the agent to a single session so it only reads data for that one entity.
GET STARTED