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

# TheSportsDB API

This API allows you to search for sports teams by their name. It returns detailed information about the team, including its leagues, stadium, and social media links. The API exposes 35 endpoints.

## For AI agents

Programmatically search teams, search events. Covers 35 operations.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- Search Teams
- Lookup League
- Integrate TheSportsDB API into automated workflows
- Query and filter TheSportsDB API records by parameters
- Monitor TheSportsDB API operational status and events

## Use cases

### Social Media Operations

Use the TheSportsDB API to perform social media operations programmatically. The API provides 35 endpoints covering core functionality including search teams, search events, search players.

Example prompt: Call GET /searchteams.php to search teams

### Automated V1 API Search Management

Automate v1 API search operations by combining multiple TheSportsDB API endpoints. Agents can search events and then search players in a single workflow.

Example prompt: Call GET /searchevents.php to search events, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'search teams', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /searchteams.php | Search Teams |
| GET | /searchevents.php | Search Events |
| GET | /searchplayers.php | Search Players |
| GET | /searchvenues.php | Search Venues |
| GET | /lookupleague.php | Lookup League |
| GET | /lookuptable.php | Lookup Table |
| GET | /lookupteam.php | Lookup Team |
| GET | /lookupequipment.php | Lookup Equipment |

## Key resources

- **V1 API Search** — Most API requests will start with a string search. Examples of this may be to find a team  or player
- **V1 API Lookup** — While the string search is useful above to find things, it is actually much quicker and simpler to r
- **V1 API List** — Using the list API means we can return more than one record. This can be useful for example to list
- **V1 API Schedule** — The Schedule API allows you to look up past, present and future events. It includes the ability to l
- **V1 API Video** — The video API allows you to list any YouTube highlights associated with an event. Please be aware th

## Why Jentic

- **Setup:** Wiring TheSportsDB by hand means dropping your key into the base path (the key sits in the URL as /api/v1/json/{api-key}), stitching together its many search and lookup routes, and handling your own retries. Through Jentic you install once, import TheSportsDB from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** TheSportsDB is read-only search and lookup, so scope it by operations: limit the agent to the calls it needs, such as searching teams or looking up a league table, and leave out any route you do not want it using. Every operation you credit it with stays inside that allowed set.
- **Credential handling:** Your TheSportsDB 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 'search for a team' or 'get a league table', and Jentic returns the matching TheSportsDB operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the TheSportsDB API use?

The TheSportsDB API uses no 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 search teams with the TheSportsDB API?

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

### What are the rate limits for the TheSportsDB 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 search teams through Jentic?

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

### How many endpoints does the TheSportsDB API have?

The TheSportsDB API exposes 35 endpoints covering v1 API search, v1 API lookup, v1 API list operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TheSportsDB operations and credentials the agent can touch. TheSportsDB is read-only search and lookup, so you scope it by operation: allow only the calls the agent needs, such as GET /searchteams.php to search teams or GET /lookuptable.php to look up a league table, and leave out any route you do not want it using. Only the operations you grant stay inside that allowed set.