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

# Sportmonks Football API

Comprehensive football data API providing access to fixtures, livescores, standings, teams, players, coaches, referees, odds, predictions, and more. Covers over 2,500 leagues worldwide. Authentication via API token in Authorization header. The API exposes 24 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get inplay livescores, get all livescores. Covers 24 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- GET Inplay Livescores
- Manage ai ml data programmatically
- Integrate Sportmonks Football API into automated workflows
- Query and filter Sportmonks Football API records by parameters
- Monitor Sportmonks Football API operational status and events

## Use cases

### AI and Machine Learning Operations

Use the Sportmonks Football API to perform ai ml operations programmatically. The API provides 24 endpoints covering core functionality including get inplay livescores, get all livescores, get all fixtures.

Example prompt: Call GET /livescores/inplay to get inplay livescores

### Automated Coaches Management

Automate coaches operations by combining multiple Sportmonks Football API endpoints. Agents can get all livescores and then get all fixtures in a single workflow.

Example prompt: Call GET /livescores to get all livescores, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sportmonks Football 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 tokens manually.

Example prompt: Search Jentic for 'get inplay livescores', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /livescores/inplay | GET Inplay Livescores |
| GET | /livescores | GET All Livescores |
| GET | /fixtures | GET All Fixtures |
| GET | /fixtures/{id} | GET Fixture by ID |
| GET | /fixtures/date/{date} | GET Fixtures by Date |
| GET | /leagues | GET All Leagues |
| GET | /leagues/{id} | GET League by ID |
| GET | /leagues/search/{name} | GET Leagues Search by Name |

## Key resources

- **Coaches** — Operations related to Coaches
- **Fixtures** — Operations related to Fixtures
- **Leagues** — Operations related to Leagues
- **Livescores** — Operations related to Livescores
- **News** — Operations related to News

## Why Jentic

- **Setup:** Wiring the Sportmonks Football API by hand means provisioning its API key, attaching it to every request, and pointing calls at the api.sportmonks.com/v3/football host yourself. Through Jentic you install once, import the Sportmonks Football API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Sportmonks puts the fixture and league ids in the URL path (/fixtures/{id}, /leagues/{id}), so a rule can pin your agent to reading one fixture or league. The endpoints here are all reads, so you choose which livescore and lookup operations it may call and nothing writes back.
- **Credential handling:** Your Sportmonks API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get inplay livescores' or 'look up a fixture', and Jentic returns the matching Sportmonks Football API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

### What authentication does the Sportmonks Football API use?

The Sportmonks Football API uses an API key passed in the `Authorization` header. 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 inplay livescores with the Sportmonks Football API?

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

### What are the rate limits for the Sportmonks Football 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 get inplay livescores through Jentic?

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

### How many endpoints does the Sportmonks Football API have?

The Sportmonks Football API exposes 24 endpoints covering coaches, fixtures, leagues operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sportmonks operations and credentials the agent may use. Every endpoint here is read-only, so you can permit just the livescore and lookup calls it needs, such as GET /livescores/inplay or GET /leagues, and nothing can write data back. Since Sportmonks carries fixture and league ids in the URL path, like /fixtures/{id} and /leagues/{id}, you can even pin the agent to reading a single fixture or league.