canonical: https://jentic.com/apis/sportsdata.io/sportsdata

# SportsData.io NFL API

SportsData.io NFL Scores API providing access to NFL teams, players, standings, and other related data. The API exposes 9 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get regular season standings for all teams, get all active team profiles. Covers 9 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get regular season standings for all teams
- Manage developer tools data programmatically
- Integrate SportsData.io NFL API into automated workflows
- Query and filter SportsData.io NFL API records by parameters
- Monitor SportsData.io NFL API operational status and events

## Use cases

### Developer Tools Operations

Use the SportsData.io NFL API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including get regular season standings for all teams, get all active team profiles, get all teams regardless of active status.

Example prompt: Call GET /json/Standings/{season} to get regular season standings for all teams

### Automated Standings Management

Automate standings operations by combining multiple SportsData.io NFL API endpoints. Agents can get all active team profiles and then get all teams regardless of active status in a single workflow.

Example prompt: Call GET /json/Teams to get all active team profiles, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SportsData.io NFL 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 regular season standings for all teams', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /json/Standings/{season} | Get regular season standings for all teams |
| GET | /json/Teams | Get all active team profiles |
| GET | /json/AllTeams | Get all teams regardless of active status |
| GET | /json/Teams/{season} | Get team profiles active in a specified season |
| GET | /json/TeamsBasic | Get basic team information for all teams |
| GET | /json/PlayersBasic/{team} | Get all player profiles for a team |
| GET | /json/PlayersByAvailable | Get all available players with biographical info |
| GET | /json/PlayersByFreeAgents | Get all free agent players |

## Key resources

- **Standings** — League standings
- **Teams** — Team profiles
- **Players** — Player profiles

## Why Jentic

- **Setup:** Wiring the SportsData.io NFL API by hand means provisioning its API key, attaching it to every request, and pointing calls at the api.sportsdata.io/v3/nfl/scores host yourself. Through Jentic you install once, import the SportsData.io NFL API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The season and team values here travel as filters in the URL rather than as owned resources, and every endpoint is a read, so limit the agent to the operations it needs, such as fetching standings or listing teams. Naming operations, not a single team, is the honest boundary here.
- **Credential handling:** Your SportsData.io 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 regular season standings' or 'list active players for a team', and Jentic returns the matching SportsData.io NFL API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the SportsData.io NFL API use?

The SportsData.io NFL API uses an API key passed in the `key` query. 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 regular season standings for all teams with the SportsData.io NFL API?

Yes. Use the GET /json/Standings/{season} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SportsData.io NFL 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 regular season standings for all teams through Jentic?

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

### How many endpoints does the SportsData.io NFL API have?

The SportsData.io NFL API exposes 9 endpoints covering standings, teams, players operations.

### Can I limit what my agent is allowed to do with the SportsData.io NFL API?

Yes. Because you run Jentic One yourself, your own rules decide which SportsData.io NFL operations your agent may call, so you can grant only read endpoints such as GET /json/Standings/{season}, GET /json/Teams, or the player lookups and withhold the rest. Every operation is a read, and values like season and team are URL filters rather than owned resources, so the honest boundary is naming the operations the agent needs rather than scoping to one team. Your API key is stored encrypted by your own instance and injected at execution time, so a narrowed set of allowed operations is enforced without exposing the credential to the agent.