DataFeeds by Rolling Insights
API docs by Redocly

DataFeeds API (1.0.0)

Download OpenAPI specification:

Rolling Insights Support: support@rolling-insights.com

Welcome to the DataFeeds by Rolling Insights REST API — real-time and historical sports data, served as JSON over HTTPS, for NFL, NBA, MLB, NHL, NCAA Football, NCAA Basketball, PGA, European soccer (EPL, Serie A, La Liga), and darts.

Each sport exposes the same core building blocks wherever that sport supports them: daily, weekly, and season schedules, live game data, player and team info and stats, depth charts, injuries, play-by-play, and event/tournament fields. Browse the endpoint groups in the sidebar for the exact paths and per-sport response shapes.

Getting started: every request is authenticated with an RSC_token query parameter — see the Authentication section below for how to register, generate a token, and make your first request.

Agent Setup — connect your coding agent to DataFeeds

Authentication

Every request to the DataFeeds REST API is authenticated with an RSC_token passed as a query parameter.

Obtaining a token

Register for an account at the API Locker to generate your RSC_token. New accounts include a 30-day free trial.

Using the token

Pass RSC_token as a query parameter on every request to the base URL https://rest.datafeeds.rolling-insights.com/api/v1. For example:

https://rest.datafeeds.rolling-insights.com/api/v1/schedule/2024-01-01/NBA?RSC_token=YOUR_TOKEN

Security best practices

  • Always call the API over HTTPS so the token is never transmitted in clear text.
  • Treat the token as a secret — it grants access to your account's data.
  • Never commit it to source control, write it to logs, or expose it in shared URLs or browser/server request history.

GraphQL API

In addition to this REST API, DataFeeds offers a GraphQL API with its own separate credentials. Authentication uses the OAuth2 client-credentials flow: a client ID and secret are exchanged for a short-lived bearer token, which is then sent as an Authorization: Bearer <token> header. Because this is a transport-level concern it cannot be represented in an OpenAPI 3 spec.

Visit the interactive Apollo Sandbox at https://datafeeds.rolling-insights.com/graphql — the getting-started and authentication home for the GraphQL API, where you can explore the schema and run queries.

Support & Resources

  • Pricing — DataFeeds plan details and sign-up: price-plans.
  • Support — questions or issues: support@rolling-insights.com.
  • Agent Setup — building with a coding agent (Claude Code, Cursor, OpenAI Codex, and others)? The Agent Setup guide walks through connecting your agent to the DataFeeds MCP server so it can query live sports data as you work. To read more about the Sports AI Skill first, see its product page.

Schedule

Games scheduled on a given date, per sport.

Darts schedule

Retrieves the daily schedule for Darts games for a particular date specified in the endpoint.

Purpose of the endpoint

  • What it does: Retrieves game schedule data for a specified date for all games that started on that day as per GMT, including details such as season, player IDs, game IDs, and more.
  • Why it exists: Provides an overview of the Darts schedule for the specified date, offering users the information they need about games that happened during that date.

Use cases

  • Obtain the latest changes and updates to a daily schedule for today's upcoming games.
  • Ingest the daily schedule requested to avoid unnecessary days' worth of games when not required.
  • Use the schedule for more specific queries for game dates, game ID, etc.

Best practices and tips

  • Use the correct endpoint without any spaces. All endpoint naming is case-sensitive.
  • In the request URL, the DATE value is the required field.
  • For Darts games use DARTS as the sport identifier followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /schedule/2024-01-01/DARTS?RSC_token=...
  • /schedule/2024-01-01/DARTS?RSC_token=...&game_id=20240101-WDC-21-5

Special data point values

Field Description Example
season Year of the season "2026"
event_name Specific event or series within the season PDC World Championship, Premier League, World Matchplay, UK Open, European Tour, Players Championship, etc.
status Game status for the request date scheduled, delayed, postponed, suspended, cancelled, withdrawn, inprogress, final, completed
player_1 Name of the first player "Chris Dobey"
player_1_ID Unique identifier for the first player 21
player_1_rank Ranking of the first player 13
player_2 Name of the second player "Rob Cross"
player_2_ID Unique identifier for the second player 5
game_time Scheduled start time in GMT "Mon, 01 Jan 2024 12:45:00 GMT"
round Tournament round "Quarter-Final", "Last 16", "Last 127", "Last 64", "Final"

Status notes

  • withdrawn: player left the tournament.
  • cancelled: game in schedule due to a source error or player name error.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2024-01-01

Date (YYYY-MM-DD) for the daily schedule as per GMT.

query Parameters
player_id
integer >= 1
Example: player_id=21

One specified player ID. Filters to games involving this player.

game_id
string
Example: game_id=20240101-WDC-21-5

One specified game ID.

event_id
string
Example: event_id=20231215WDC

One specified event ID.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

MLB schedule

Retrieves the MLB schedule for a single date — games that started that day (GMT) — including season type, game IDs, game times, and probable starting pitchers.

Purpose: An overview of the MLB schedule for one date.

Use cases:

  • Get the latest changes and updates for a given day's games.
  • Ingest only the day you need instead of a full season of games.
  • Look up game dates and game_ID values for follow-up queries.

Best practices:

  • Re-request the current day's schedule through the day to pick up same-day changes and updates.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-04-22

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA schedule

Retrieves the NBA schedule for a single date — games that started that day (GMT) — including season type, game IDs, and game times.

Purpose: An overview of the NBA schedule for one date.

Use cases:

  • Get the latest changes and updates for a given day's games.
  • Ingest only the day you need instead of a full season of games.
  • Look up game dates and game_ID values for follow-up queries.

Best practices:

  • Re-request the current day's schedule through the day to pick up same-day changes and updates.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-03-19

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAABB schedule

Retrieve the daily schedule of College Basketball (NCAABB) games for the date in the path (games that started that day, GMT).

Purpose: Returns every game on the given date — season type, game IDs, team IDs, seeding/bracket details, and venue — for a focused view of a single day's slate.

Use cases:

  • Pull the latest schedule and updates for a given day's games.
  • Request only the date you need to avoid ingesting unnecessary days of games.
  • Feed game IDs into more specific queries such as box-score lookups.

Best practices:

  • For the current date, re-request periodically to pick up schedule changes and updates.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-03-20

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAAFB schedule

Retrieve the schedule of College Football (NCAAFB) games for a single date — every game that started on the given date in GMT (season type, game IDs, game times, and more).

Use cases:

  • Track the latest changes and updates for a given day's slate.
  • Resolve game dates and game_id values for more detailed queries.

Best practices: Request only the dates you need to avoid ingesting unnecessary days of games.

Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2025-11-15

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL schedule

Retrieves the NFL schedule for a single date — games that started that day (GMT) — including season type, week numbers, game IDs, game times, and venue details.

Purpose: An overview of the NFL schedule for one date.

Use cases:

  • Get the latest changes and updates for a given day's games.
  • Ingest only the day you need instead of a full season of games.
  • Look up game dates and game_ID values for follow-up queries.

Best practices:

  • Re-request the current day's schedule through the day to pick up same-day changes and updates.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2025-12-21

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL schedule

Retrieves all NHL games that started on the given date (GMT) — teams, game IDs, game times, season type and status.

Use cases:

  • Get the current day's games, with the latest schedule changes and updates.
  • Look up game IDs and dates to drive more specific queries such as live box scores or team/player stats.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-05-18

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

PGA schedule

Retrieves the daily schedule for PGA tournaments for a particular date specified in the endpoint.

Purpose of the endpoint

  • What it does: Retrieves tournament schedule data for a specified date, including details such as tournament ID, course, purse, status, and more.
  • Why it exists: Provides an overview of the PGA schedule for the specified date, offering users the information they need about tournaments that day.

Use cases

  • Obtain the latest changes and updates to a daily schedule for today's upcoming tournaments.
  • Ingest the daily schedule requested to avoid unnecessary days' worth of events when not required.
  • Use the schedule for more specific queries by tournament ID (game_id).

Best practices and tips

  • Use the correct endpoint without any spaces. All endpoint naming is case-sensitive.
  • In the request URL, the DATE value is the required field (YYYY-MM-DD).
  • For PGA tournaments use PGA as the sport identifier followed by your RSC_token (required).
  • When filtering with game_id, only a single PGA tournament ID may be specified.
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /schedule/2025-06-05/PGA?RSC_token=...
  • /schedule/2025-06-05/PGA?game_id=2025_41&RSC_token=...
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2025-06-05

Date (YYYY-MM-DD) for the daily schedule.

query Parameters
game_id
string
Example: game_id=2025_61

One specified tournament ID. Only PGA must be specified when using this parameter. If PGA is among multiple SPORT parameters, game_id cannot be specified.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER schedule

Daily schedule of SOCCER games that start on the given {date} (GMT) — team IDs, game IDs, kickoff time, venue, and season type.

Use cases:

  • Fetch the latest changes and updates to the day's upcoming games.
  • Ingest only the day you need, avoiding unnecessary days' worth of games.
  • Resolve game dates and IDs to drive more specific queries (e.g. live box scores).

Best practices: The {date} is matched in GMT, so a late local kickoff can land on the next day's feed.

Authorizations:
RSC_token
path Parameters
date
required
string
Example: 2026-03-19
query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Weekly Schedule

Games scheduled for a given week of a season.

Darts weekly schedule

Retrieves the weekly schedule for Darts games starting from the specified date in the endpoint, covering the following seven days.

Purpose of the endpoint

  • What it does: Retrieves the weekly game schedule data for a requested date, including details such as season, player IDs, game IDs, and more.
  • Why it exists: Provides an overview of the Darts season for the specified week, offering users the information they need about games that happened during that week.

Use cases

  • Analyze the schedule for a small and specific window to get more game information.
  • Use the schedule for more specific queries for game dates, game ID, etc.

Best practices and tips

  • Use the correct endpoint without any spaces. All endpoint naming is case-sensitive.
  • We recommend using this endpoint at the start of each week to retrieve the schedule for all games in the upcoming 7 days.
  • In the request URL, the DATE value is the required field.
  • For Darts games use DARTS as the sport identifier followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /schedule-week/2024-01-01/DARTS?RSC_token=...
  • /schedule-week/2024-01-01/DARTS?RSC_token=...&game_id=20240101-WDC-21-5
  • /schedule-week/2024-01-01/DARTS?RSC_token=...&player_id=21
  • /schedule-week/2024-01-01/DARTS?RSC_token=...&event_id=20231215WDC

Special data point values

Field Description Example
season Year of the season "2026"
event_name Specific event or series within the season PDC World Championship, Premier League, World Matchplay, UK Open, European Tour, Players Championship, etc.
status Game status for the request date scheduled, delayed, postponed, suspended, cancelled, withdrawn, inprogress, final, completed
player_1 Name of the first player "Chris Dobey"
player_1_ID Unique identifier for the first player 21
player_1_rank Ranking of the first player 13
player_2 Name of the second player "Rob Cross"
player_2_ID Unique identifier for the second player 5
game_time Scheduled start time in GMT "Mon, 01 Jan 2024 12:45:00 GMT"
round Tournament round "Quarter-Final", "Last 16", "Last 127", "Last 64", "Final"

Status notes

  • withdrawn: player left the tournament.
  • cancelled: game in schedule due to a source error or player name error.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2024-01-01

Anchor date (YYYY-MM-DD). Returns games for this date plus the following 7 days.

query Parameters
player_id
integer >= 1
Example: player_id=21

One specified player ID. Filters to games involving this player.

game_id
string
Example: game_id=20240101-WDC-21-5

One specified game ID.

event_id
string
Example: event_id=20231215WDC

One specified event ID.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

MLB weekly schedule

Retrieves the MLB schedule for the seven-day window beginning on the given date, including season type, game IDs, game times, and probable starting pitchers.

Purpose: An overview of MLB games for a specific week.

Use cases:

  • Analyze a small, specific window of games.
  • Look up game dates and game_ID values for follow-up queries.

Best practices:

  • Call at the start of each week to retrieve the upcoming seven days of games.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-04-22

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA weekly schedule

Retrieves the NBA schedule for the seven-day window beginning on the given date, including season type, game IDs, and game times.

Purpose: An overview of NBA games for a specific week.

Use cases:

  • Analyze a small, specific window of games.
  • Look up game dates and game_ID values for follow-up queries.

Best practices:

  • Call at the start of each week to retrieve the upcoming seven days of games.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-03-19

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAABB weekly schedule

Retrieve the schedule of College Basketball (NCAABB) games for the seven-day window beginning on the date in the path.

Purpose: Returns all games in the 7 days from the given date — season type, game IDs, team IDs, and more — for an at-a-glance view of the week.

Use cases:

  • Review a specific week's slate to see which teams play and when.
  • Retrieve game dates and game IDs for more specific follow-up queries.

Best practices:

  • Fetch once at the start of each week — {date} is the first day of the 7-day window.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-03-20

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAAFB weekly schedule

Retrieve the schedule of College Football (NCAAFB) games for the seven-day window beginning on the given date — an overview of a single week of the season (season type, game IDs, game times, and more).

Use cases:

  • Analyze a small, specific window of upcoming games for team and matchup context.
  • Resolve game dates and game_id values for more detailed queries.

Best practices: Call at the start of each week to retrieve the upcoming seven days.

Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2025-11-15

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL weekly schedule

Retrieves the NFL schedule for the seven-day window beginning on the given date, including season type, week numbers, game IDs, game times, and venue details.

Purpose: An overview of NFL games for a specific week.

Use cases:

  • Analyze a small, specific window of games.
  • Look up game dates and game_ID values for follow-up queries.

Best practices:

  • Call at the start of each week to retrieve the upcoming seven days of games.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2025-12-21

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL weekly schedule

Retrieves the NHL schedule for the seven days beginning on the given date — teams, game IDs, game times, season type and status.

Use cases:

  • Analyze a focused, week-long window of games for team and player planning.
  • Look up game dates and IDs to drive more specific queries.

Best practices: Request once at the start of each week to cover the upcoming 7 days.

Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-05-18

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

PGA weekly schedule

Retrieves the weekly schedule for PGA tournaments starting from the specified date in the endpoint, covering the following seven days.

Purpose of the endpoint

  • What it does: Retrieves the weekly tournament schedule for a requested date, including details such as tournament ID, course, purse, status, and more.
  • Why it exists: Provides an overview of PGA events for the specified week, offering users the information they need about tournaments in that window.

Use cases

  • Analyze the schedule for a small and specific window to get more tournament information.
  • Use the schedule for more specific queries by tournament date or tournament ID (game_id).

Best practices and tips

  • Use the correct endpoint without any spaces. All endpoint naming is case-sensitive.
  • We recommend using this endpoint at the start of each week to retrieve the schedule for all tournaments in the upcoming 7 days.
  • In the request URL, the DATE value is the required field (now or YYYY-MM-DD).
  • For PGA tournaments use PGA as the sport identifier followed by your RSC_token (required).
  • When filtering with game_id, only a single PGA tournament ID may be specified.
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /schedule-week/2025-06-04/PGA?RSC_token=...
  • /schedule-week/2025-06-04/PGA?game_id=2025_41&RSC_token=...
Authorizations:
RSC_token
path Parameters
date
required
string
Example: 2025-06-04

Anchor date ("now" or YYYY-MM-DD). Returns tournaments for this date plus the following 7 days.

query Parameters
game_id
string
Example: game_id=2025_61

One specified tournament ID. Only PGA must be specified when using this parameter. If PGA is among multiple SPORT parameters, game_id cannot be specified.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER weekly schedule

Schedule of SOCCER games for the seven-day window beginning on the given {date} (GMT). Recommended at the start of each week to retrieve all games in the upcoming 7 days.

Use cases:

  • Analyze a small, specific window to gather more team and player information.
  • Resolve game dates and IDs for more specific queries.
Authorizations:
RSC_token
path Parameters
date
required
string
Example: 2026-03-19
query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Season Schedule

The full slate of games for a season.

Darts season schedule

Retrieves the season schedule for Dart games for a particular year specified in the endpoint.

Purpose of the endpoint

  • What it does: Retrieves the season schedule for a specified year, including details such as season, event_ID, game IDs, and more.
  • Why it exists: Provides a comprehensive overview of the Darts season for the requested year.

Use cases

  • Access the entire season schedule to gather information and conduct assessments. Recommended only once at the start of the year.
  • For a more detailed assessment of a tournament, also use the events endpoint.
  • Display when games are being played.
  • Use event_ID or game_ID for more specific detail queries.

Best practices and tips

  • Use the correct endpoint without any spaces. All endpoint naming is case-sensitive.
  • In the request URL, provide the season year (YYYY) for the schedule you need.
  • For Darts games use DARTS as SPORT followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /schedule-season/2024/DARTS?RSC_token=...&game_id=20240101-WDC-156-27
  • /schedule-season/2023/DARTS?RSC_token=...&event_id=20231215WDC
  • /schedule-season/2026/DARTS?RSC_token=...&player_id=3

Special data point values

Field Description Example
season Year of the season "2026"
event_name Specific event or series within the season PDC World Championship, Premier League, World Matchplay, UK Open, European Tour, Players Championship, etc.
status Game status for the request date scheduled, delayed, postponed, suspended, cancelled, withdrawn, inprogress, final, completed
player_1 Name of the first player "Chris Dobey"
player_1_ID Unique identifier for the first player 21
player_1_rank Ranking of the first player 13
player_2 Name of the second player "Rob Cross"
player_2_ID Unique identifier for the second player 5
game_time Scheduled start time in GMT "Mon, 01 Jan 2024 12:45:00 GMT"
round Tournament round "Quarter-Final", "Last 16", "Last 127", "Last 64", "Final"

Status notes

  • withdrawn: player left the tournament.
  • cancelled: game in schedule due to a source error or player name error.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2026

Season year (YYYY).

query Parameters
player_id
integer >= 1
Example: player_id=21

One specified player ID. Filters to games involving this player.

game_id
string
Example: game_id=20240101-WDC-21-5

One specified game ID.

event_id
string
Example: event_id=20231215WDC

One specified event ID.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

MLB season schedule

Retrieves the full MLB season schedule for the requested year, including season type, game IDs, game times, and probable starting pitchers.

Purpose: A comprehensive overview of the MLB season for the requested year — everything you need about that season's games in one call.

Use cases:

  • Pull the entire season schedule once to seed your own dataset.
  • Display when games are being played.
  • Use the returned game_ID values to drill into other endpoints (box scores, play-by-play, etc.).

Best practices:

  • Fetch the full season schedule once for the complete picture, then use the daily and weekly schedule endpoints to pick up changes going forward, rather than refetching the whole season.
Authorizations:
RSC_token
path Parameters
season
required
string^\d{4}$
Example: 2026

The year the season started (e.g. 2026), not a date.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA season schedule

Retrieves the full NBA season schedule for the requested year, including season type, game IDs, game times, and related details.

Purpose: A comprehensive overview of the NBA season for the requested year — everything you need about that season's games in one call.

Use cases:

  • Pull the entire season schedule once to seed your own dataset.
  • Display when games are being played.
  • Use the returned game_ID values to drill into other endpoints (box scores, play-by-play, etc.).

Best practices:

  • Fetch the full season schedule once for the complete picture, then use the daily and weekly schedule endpoints to pick up changes going forward, rather than refetching the whole season.
Authorizations:
RSC_token
path Parameters
season
required
string^\d{4}$
Example: 2025

The year the season started (e.g. 2025), not a date.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAABB season schedule

Retrieve the full-season schedule of College Basketball (NCAABB) games for the year in the path.

Purpose: Returns every game for the requested season — season type, game IDs, team IDs, seeding/bracket details, and venue — for a comprehensive view of the season.

Use cases:

  • Pull the entire season schedule to gather information and run assessments.
  • Drive displays of when games are played.
  • Feed game IDs into more specific queries such as box-score lookups.

Best practices:

  • Fetch the full season schedule once for the complete picture, then use the daily and weekly schedule endpoints to pick up changes and updates — rather than repeatedly refetching the whole season.
Authorizations:
RSC_token
path Parameters
season
required
string^\d{4}$
Example: 2025

The year the season started (e.g. 2025), not a date.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAAFB season schedule

Retrieve the full-season schedule of College Football (NCAAFB) games for a given year — a comprehensive overview of the requested season (season type, game IDs, game times, and more) in a single response.

Use cases:

  • Seed season-long assessments and analytics from one authoritative schedule.
  • Resolve game_id values to drive more specific queries such as box-score results.

Best practices: Fetch the full season schedule once for the complete picture, then track changes and updates via the daily and weekly schedule endpoints rather than repeatedly refetching the whole season.

Authorizations:
RSC_token
path Parameters
season
required
string^\d{4}$
Example: 2025

The year the season started (e.g. 2025), not a date.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL season schedule

Retrieves the full NFL season schedule for the requested year, including season type, week numbers, game IDs, game times, and venue details.

Purpose: A comprehensive overview of the NFL season for the requested year — everything you need about that season's games in one call.

Use cases:

  • Pull the entire season schedule once to seed your own dataset.
  • Display when games are being played.
  • Use the returned game_ID values to drill into other endpoints (box scores, play-by-play, etc.).

Best practices:

  • Fetch the full season schedule once for the complete picture, then use the daily and weekly schedule endpoints to pick up changes going forward, rather than refetching the whole season.
Authorizations:
RSC_token
path Parameters
season
required
string^\d{4}$
Example: 2025

The year the season started (e.g. 2025), not a date.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL season schedule

Retrieves the full NHL game schedule for a season — season type, teams, game IDs and game times for every game in the requested year.

Use cases:

  • Pull a complete-season overview for planning and analysis.
  • Discover game IDs and dates to drive more specific queries such as the daily schedule, live box scores, or team/player stats.

Best practices: Typically requested once near the start of the season; use the daily or weekly schedule to pick up in-season changes.

Authorizations:
RSC_token
path Parameters
season
required
string^\d{4}$
Example: 2025

The year the season started (e.g. 2025), not a date.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

PGA season schedule

Retrieves the season schedule for PGA tournaments for a particular year specified in the endpoint.

Purpose of the endpoint

  • What it does: Retrieves the season schedule for a specified year, including details such as tournament ID, event ID, course, purse, status, and more.
  • Why it exists: Provides a comprehensive overview of the PGA season for the requested year.

Use cases

  • Access the entire season schedule to gather information and conduct assessments. Recommended only once at the start of the year.
  • Display when tournaments are being played.
  • Use tournament_ID / game_id for more specific detail queries.

Best practices and tips

  • Use the correct endpoint without any spaces. All endpoint naming is case-sensitive.
  • In the request URL, provide the season year (YYYY) for the schedule you need.
  • For PGA tournaments use PGA as SPORT followed by your RSC_token (required).
  • When filtering with game_id, only a single PGA tournament ID may be specified.
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /schedule-season/PGA?RSC_token=...
  • /schedule-season/2025/PGA?RSC_token=...
  • /schedule-season/PGA?game_id=2025_61&RSC_token=...
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Season year (YYYY).

query Parameters
game_id
string
Example: game_id=2025_61

One specified tournament ID. Only PGA must be specified when using this parameter. If PGA is among multiple SPORT parameters, game_id cannot be specified.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER season schedule

Full-season schedule of SOCCER games for the given {season} (the four-digit year the season started, e.g. 2025).

Use cases:

  • Access an entire season's schedule for analysis and assessment — best fetched once at the start of the season.
  • Display when games are played, and use a returned game_ID for detailed per-game queries such as box scores.
Authorizations:
RSC_token
path Parameters
season
required
string^\d{4}$
Example: 2025

The year the season started (e.g. 2025), not a date.

query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Live

Real-time box scores and game status for games on a given date; past dates return historical live data.

Darts live games

Retrieves live updates for Darts games for a particular date specified in the endpoint.

Purpose of the endpoint

  • What it does: Retrieves real-time game updates for Darts games that started on the specified date, including details such as scoreboard, game_status, game ID, and more.
  • Why it exists: Provides a comprehensive overview of Darts games for the specified date and offers users real-time information on live or scoreboard data about ongoing and completed games.

Use cases

  • Player performance tracking: Monitor individual player statistics and metrics in real time.
  • Live and past data access: Obtain live data for the current date, as well as retrieve past live game statistics for previous dates.
  • Player performance analysis: Track player performance metrics during a game to adapt strategies on the fly.

Best practices and tips

  • Use the correct endpoint without any spaces. Endpoint names are case-sensitive.
  • In the request URL, the DATE value is the required field.
  • For Darts games use DARTS as the sport identifier followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /live/2023-03-04/DARTS?RSC_token=...
  • /live/2023-03-04/DARTS?RSC_token=...&game_id=20230304-UKOP-4-92

Special data point values

Field Description Example
event Name of the event "UK Open"
sport Type of sport "DARTS"
status Game status scheduled, delayed, postponed, suspended, cancelled, withdrawn, inprogress, final, completed
format Game format "set", "leg"
round Tournament round "Quarter-Final", "Last 16", "Last 127", "Last 64", "Final"
game_ID Unique game identifier "20230304-UKOP-4-92"
event_ID Unique event identifier "20230303UKOP"
game_time Scheduled start time in GMT "Sat, 04 Mar 2023 13:00:00 GMT"
current_box Current game state (leg, throwing, points to checkout)
game_status Display status of the game "Final"
series_name Name of the series "UK Open 2023"
leg_breakdown Detailed breakdown of each leg (see notes below)
legs_won Legs won by the player in the game 8
match_stats Player performance statistics for the game object

leg_breakdown notes

  • Each entry includes leg, set, and turns (player turn data keyed by player ID).
  • Set format is only used for these tournaments:
    • WDC — World Darts Championship (also mapped as PDC World Championship / World Championship)
    • WGP — World Grand Prix
  • For all other tournaments, set is kept as 0 in the live feed.
  • When the tournament is played in sets (WDC / WGP), set is updated to the actual set number.

Status notes

  • withdrawn: player left the tournament.
  • cancelled: game in schedule due to a source error or player name error.

What data is available in each tournament

  • European Tour Events
    • Includes game times for all matches
    • Throw data is available for all matches
    • Match stats are available for all matches
  • Premier League Events
    • Includes game times for all matches
    • Throw data is available for all matches
    • Match stats are available for all matches
  • Players Championship Events
    • Does not include game_times for most matches before the Quarter-Finals
    • Throw data is not available in the leg breakdown of the game object
    • Most match stats are not available for matches before the Quarter-Finals
      • Some matches from the Quarter-Finals and on have match stats available however it is not a guaranteed
  • Open Events
    • Does not include game_time for all matches
    • Throw data is not always available for all matches
    • Match stats are not available for all games
      • some games are missing certain data points such as checkouts_made
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2023-03-04

Date (YYYY-MM-DD) for live games as per GMT.

query Parameters
game_id
string
Example: game_id=20230304-UKOP-4-92

One specified game ID.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

MLB live games

Retrieves real-time MLB game updates for games that started on the given date — live box scores, game status, season, and game IDs — and also serves historical (past-date) live box scores.

Purpose: Real-time and historical live box scores for ongoing and completed games.

Use cases:

  • Player performance tracking — monitor individual player stats in real time.
  • Live and past data access — get live data for the current date, or retrieve past live game stats for previous dates.
  • Team performance analysis — track team metrics during a game.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-04-22

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA live games

Retrieves real-time NBA game updates for games that started on the given date — live box scores, game status, season, and game IDs — and also serves historical (past-date) live box scores.

Purpose: Real-time and historical live box scores for ongoing and completed games.

Use cases:

  • Player performance tracking — monitor individual player stats in real time.
  • Live and past data access — get live data for the current date, or retrieve past live game stats for previous dates.
  • Team performance analysis — track team metrics during a game.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-03-19

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAABB live games

Retrieve real-time (and historical live) box scores for College Basketball (NCAABB) games for the date in the path.

Purpose: Returns live updates for games that started on the given date — team and player box scores, game status, season, and game IDs.

Use cases:

  • Player performance tracking: monitor individual player stats and metrics in real time.
  • Live and past data access: get live data for the current date, or retrieve historical live box scores for past dates.
  • Team performance analysis: track team metrics during a game to adapt strategy.

Best practices:

  • Poll only while games are in progress; pass a past date to review completed games.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-03-20

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAAFB live games

Retrieve real-time — or historical live — updates for College Football (NCAAFB) games on the given date: box scores for games that started that date (game status, season, game ID, and more), covering both ongoing and completed games.

Use cases:

  • Monitor individual player performance and metrics in real time.
  • Track team performance during a game to adapt strategy on the fly.
  • Retrieve past live box scores for previous dates, not just the current day.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2025-11-15

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL live games

Retrieves real-time NFL game updates for games that started on the given date — live box scores, game status, week, season, and game IDs — and also serves historical (past-date) live box scores.

Purpose: Real-time and historical live box scores for ongoing and completed games.

Use cases:

  • Player performance tracking — monitor individual player stats in real time.
  • Live and past data access — get live data for the current date, or retrieve past live game stats for previous dates.
  • Team performance analysis — track team metrics during a game.

DraftKings fantasy points: live player and team box scores include DK_fantasy_points, computed with the same DraftKings scoring rules as the Player Stats and Team Stats endpoints — see those endpoints for the full calculation breakdown.

Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2025-12-21

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL live games

Retrieves real-time and historical box scores for NHL games that started on the given date — team and player box scores, game status and final results.

Use cases:

  • Track individual player statistics and metrics in real time.
  • Access live data for the current date, or retrieve past box scores for previous dates.
  • Analyze team performance during a game to adapt strategy on the fly.
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2026-05-18

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

PGA live tournaments

Retrieves live updates for PGA tournaments for a particular date specified in the endpoint.

Purpose of the endpoint

  • What it does: Retrieves real-time tournament updates for PGA events on the specified date. Supports both stroke-play events and cup-format team match-play events (e.g. Ryder Cup).
  • Why it exists: Provides a comprehensive overview of PGA tournaments for the specified date and offers users real-time leaderboard, scoring, and (for cup events) pairing data.

Use cases

  • Player performance tracking: Monitor individual golfer statistics and hole scores in real time.
  • Live and past data access: Obtain live data for the current date, as well as retrieve past live tournament statistics for previous dates.
  • Leaderboard analysis: Track positions, FedEx points, and round scores during a stroke-play tournament.
  • Cup pairings: For Ryder Cup–style events, use each Round's groupId (and optional matches[]) to relate USA vs EUROPE session pairings.

Best practices and tips

  • Use the correct endpoint without any spaces. Endpoint names are case-sensitive.
  • In the request URL, the DATE value is required (YYYY-MM-DD).
  • For PGA tournaments use PGA as the sport identifier followed by your RSC_token (required).
  • When filtering with game_id, only a single PGA tournament ID may be specified.
  • Detect format by shape: cup/Ryder Cup players have team and Round objects with groupId; stroke players have current and starting_holes.
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /live/2018-12-12/PGA?RSC_token=...&game_id=...
  • /live/2025-09-26/PGA?RSC_token=... (Ryder Cup / cup-format example date)

Tournament formats The live feed returns one of two tournament shapes in data.PGA[]:

  • Stroke play (regular PGA Tour events): field players with current, tee_times, starting_holes, optional Round hole maps (par / score numbers), plus tournament start_time.
  • Cup format (Ryder Cup): field players have team (USA / EUROPE), tee_times, and Round {N} session objects — not stroke current / starting_holes. Optional top-level matches[] lists USA vs EUROPE pairings by session.

Cup / Ryder Cup field player (verified)

  • team — player’s cup side (USA or EUROPE).
  • player — golfer name.
  • Round {N} — only rounds the player contested are present (e.g. Round 2 only). Each includes:
    • name — session label (e.g. Friday Morning Foursomes, Friday Afternoon Four-Balls, Sunday Singles)
    • team — side for that session
    • groupId — UUID for that pairing (unique per session; teammates/opponents share the same id)
    • Hole {N} — { "score": "0.5" } etc.; may be {} before the hole is scored (no par)
  • tee_times — tee time per Round {N} (Ryder Cup spans multiple sessions / rounds, e.g. Round 1–5).

Special data point values

Field Values
status "scheduled", "delayed", "suspended", "inprogress", "final", "completed"
game_status "Set Field", "Round {N} - Live", "Round {N} - Completed", "Round {N} - Suspended", "Final", "Playoff - Final"
current (stroke) Round {N} scores (numbers), earnings, position, fedex_points, score_overall, total_strokes
starting_holes (stroke) Starting hole number per round (e.g. 1 or 10)
Round {N} (stroke) {} when the player missed the cut or no hole data is available; otherwise hole / par / score for each hole
Round {N} (cup) { name, team, groupId, Hole {N}… } — match-play session; hole score is a string ("1", "0.5", "0") or hole is {}
team (cup) "USA", "EUROPE"
groupId (cup) UUID string per session pairing
matches[].session (cup) e.g. Friday Morning Foursomes, Friday Afternoon Four-Balls, Sunday Singles
Authorizations:
RSC_token
path Parameters
date
required
string <date>
Example: 2018-12-12

Date (YYYY-MM-DD) for live tournaments.

query Parameters
game_id
string
Example: game_id=2025_61

One specified tournament ID. Only PGA must be specified when using this parameter. If PGA is among multiple SPORT parameters, game_id cannot be specified.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER live games

Real-time and historical box scores for SOCCER games that started on the given {date} (GMT) — live team and player statistics for in-progress games and final box scores for completed ones.

Use cases:

  • Player performance tracking: monitor individual player statistics in real time.
  • Live and past data access: get live data for the current date, or retrieve past live game statistics for previous dates.
  • Team performance analysis: track team metrics during a game to adapt strategy on the fly.

Best practices: Poll on match days for live updates.

Authorizations:
RSC_token
path Parameters
date
required
string
Example: 2026-03-19
query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Play-by-Play

Chronological play-by-play event data for a game.

MLB play-by-play

Detailed, event-level play-by-play for a single MLB game. Each play includes the event sequence, inning and half-inning, event type, whether the play resulted in an out and the running out count, a text description, and every player involved with their role and action.

Purpose: Reconstruct exactly what happened in a game, play by play.

Use cases:

  • Analyze game flow.
  • Track player involvement.
  • Monitor scoring progression.
  • Reconstruct innings and play sequences.

Best practices:

  • Obtain game_id from the schedule endpoint (e.g. /schedule/{date}/MLB).
Authorizations:
RSC_token
query Parameters
game_id
required
string
Example: game_id=20260422-1-17

Game identifier from the schedule endpoint (e.g. /schedule/{date}/MLB)

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA play-by-play

Detailed, event-level play-by-play for a single NBA game. Each play includes the event sequence, period, game clock, running score, team in possession, event type, action, and every player involved with their role and action.

Purpose: Reconstruct exactly what happened in a game, play by play.

Use cases:

  • Analyze game flow.
  • Track player involvement.
  • Monitor scoring progression.
  • Reconstruct possessions and play sequences.

Best practices:

  • Obtain game_id from the schedule endpoint (e.g. /schedule/{date}/NBA).
Authorizations:
RSC_token
query Parameters
game_id
required
string
Example: game_id=20260319-99-99

Game identifier from the schedule endpoint (e.g. /schedule/{date}/NBA)

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL play-by-play

Detailed, event-level play-by-play for a single NFL game. Each play includes the event sequence, quarter, down, distance (yards to go), yard line, game clock, team in possession, scoring flags, and every player involved with their role, action, and position.

Purpose: Reconstruct exactly what happened in a game, play by play — from kickoff to the final whistle.

Use cases:

  • Analyze game flow.
  • Track player involvement.
  • Monitor scoring plays.
  • Reconstruct drives and play sequences.

Best practices:

  • Obtain game_id from the schedule endpoint (e.g. /schedule/{date}/NFL).
Authorizations:
RSC_token
query Parameters
game_id
required
string
Example: game_id=20251221-1-26

Game identifier from the schedule endpoint (e.g. /schedule/{date}/NFL)

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL play-by-play

Detailed, event-level play-by-play for a single NHL game. Each play includes the event sequence, period, game clock, running score, attributed team, event type, action, and every player involved with their role and action — plus hockey-specific state: faceoff winners, power-play details (start, scheduled end, actual end, manpower), skater counts while penalties are active, and empty-net indicators.

Purpose: Reconstruct exactly what happened in a game, play by play.

Use cases:

  • Analyze game flow.
  • Track player involvement.
  • Monitor scoring progression.
  • Follow penalties and power-play situations.

Best practices:

  • Obtain game_id from the schedule endpoint (e.g. /schedule/{date}/NHL).
  • null means a value is unavailable or cannot be safely derived; false means it is known to be false (e.g. playersOnIce: null is even strength at 5-on-5, emptyNet: false is a known non-empty net).
Authorizations:
RSC_token
query Parameters
game_id
required
string
Example: game_id=20260518-23-16

Game identifier from the schedule endpoint (e.g. /schedule/{date}/NHL)

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Player Info

Player rosters and biographical details.

Darts player info

Retrieves player information for Darts games.

Purpose of the endpoint

  • What it does: Retrieves player information related to Darts games for the season, including details such as player ID, dart used, and more.
  • Why it exists: Provides a comprehensive overview of player information for Darts games, helping users analyze performance and make informed decisions.

Use cases

  • Understanding player details for informative purposes.
  • Use player information for more specific detail queries like scoreboard results with the player_id.

Best practices and tips

  • Use the correct endpoint without any spaces. Endpoint names are case-sensitive.
  • For Darts games use DARTS as the sport identifier followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /player-info/DARTS?RSC_token=...
  • /player-info/DARTS?RSC_token=...&player_id=1
Authorizations:
RSC_token
query Parameters
player_id
integer >= 1
Example: player_id=1

One specified player ID.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

MLB player info

Retrieves information for MLB players, including player ID, team, jersey number, position, batting and throwing hands, and physical details (height, weight).

Purpose: A comprehensive overview of player information to support analysis and decision-making.

Use cases:

  • Understand a player's position and team.
  • Resolve players associated with a team for more specific queries (e.g. box scores by player_id).
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA player info

Retrieves information for NBA players, including player ID, team, jersey number, position, and physical details (height, weight).

Purpose: A comprehensive overview of player information to support analysis and decision-making.

Use cases:

  • Understand a player's position and team.
  • Resolve players associated with a team for more specific queries (e.g. box scores by player_id).
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAABB player info

Retrieve player information for College Basketball (NCAABB).

Purpose: Returns player details for the season — player ID, team, jersey number, position, physicals, and class/status — for a comprehensive roster view.

Use cases:

  • Understand a player's position and team affiliation.
  • Resolve players to their team and position for more specific follow-up queries.

Best practices:

  • Refresh roster data periodically rather than requesting it on every call.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAAFB player info

Retrieve player information for College Football (NCAAFB) — a comprehensive overview of players (player ID, team, position, and more) to support analysis and informed decisions.

Use cases:

  • Understand a player's position and team affiliation.
  • Associate players with a team via player_id for more specific queries such as box-score results.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL player info

Retrieves information for NFL players, including player ID, team, jersey number, position, physical details (height, weight), and college.

Purpose: A comprehensive overview of player information to support analysis and decision-making.

Use cases:

  • Understand a player's position and team.
  • Resolve players associated with a team for more specific queries (e.g. box scores by player_id).
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL player info

Retrieves reference information for NHL players — player ID, team, jersey number, position and biographical details.

Use cases:

  • Understand a player's team and position.
  • Resolve a player ID to pair with stats or box-score queries.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

PGA golfer info

Retrieves golfer information for PGA.

Purpose of the endpoint

  • What it does: Retrieves player information related to PGA golfers, including details such as player ID, weight, debut year, and more.
  • Why it exists: Provides a comprehensive overview of golfer biographical information, helping users analyze players and make informed decisions.

Use cases

  • Understanding golfer details for informative purposes.
  • Use player information for more specific detail queries with the player_id.

Best practices and tips

  • Use the correct endpoint without any spaces. Endpoint names are case-sensitive.
  • For PGA use PGA as the sport identifier followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /player-info/PGA?RSC_token=...
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER player info

Roster and biographical information for SOCCER players in the requested league — player ID, team, squad number, position, physical details, and roster status (e.g. ACT, INACT, QUES).

Use cases:

  • Understand a player's position and team.
  • Resolve players by team and position to drive detailed queries, such as box-score results by player_id.

Best practices: Roster status indicates availability — ACT (active), INACT (inactive), QUES (questionable).

Authorizations:
RSC_token
query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Player Stats

Season-level statistics for individual players.

Darts player stats

Retrieves player season stats for Darts games for a particular year specified in the endpoint.

Purpose of the endpoint

  • What it does: Retrieves player season stats related to Darts games for the year indicated in the request, including details such as player ID, scoreboard, and player performance.
  • Why it exists: Provides a comprehensive overview of player performance in the requested season, helping users analyze performance and make informed decisions.

Use cases

  • Strategic planning: Analyze player performance scoreboards and related information for statistical and strategic purposes.
  • Performance analysis: Track player performance trends over a season, identifying peak and poor performance periods.

Best practices and tips

  • Use the correct endpoint without any spaces. Endpoint names are case-sensitive.
  • In the request URL, provide the season year (YYYY) for the stats you need.
  • For Darts games use DARTS as the sport identifier followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

Player statistics are not updated in real-time. Stats are updated at the end of each leg and once the game has ended.

URL examples

  • /player-stats/2026/DARTS?RSC_token=...
  • /player-stats/2026/DARTS?RSC_token=...&player_id=1

Special data point values

Field Description Example
player_id Unique identifier for the player 5
player Name of the player Rob Cross
throws.100_plus Throws scoring 100 or more 149
throws.140_plus Throws scoring 140 or more 93
throws.180_plus Throws scoring 180 30
checkouts.made Successful checkouts 70
checkouts.total Total checkout attempts 174
checkouts.100_plus Checkouts of 100 or more 8
checkouts.percentage Checkout success percentage 40.23%
total_score Total score in the tournament 62067
total_throws Total throws made 1950
matches_played Matches played in the tournament 13
highest_checkout Highest single checkout 170
three_dart_average Average score per three darts 95.49
total_matches_played Total matches in the regular season 67
{tournament_name} Per-tournament stats keyed by event name (e.g. UK Open, PDC World Championship, Premier League) object
postseason Postseason statistics (not provided) null - No postseason statistics are available or provided for the player.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2026

Season year (YYYY).

query Parameters
player_id
integer >= 1
Example: player_id=1

One specified player ID.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

MLB player stats

Retrieves MLB player season statistics for the requested year, including player ID, position, and batting and pitching box scores for the regular season and postseason.

Purpose: A comprehensive overview of player performance for a season, via box scores.

Use cases:

  • Strategic planning — analyze player box scores and related stats.
  • Performance analysis — compare a player's regular-season and postseason totals.

Best practices:

  • Season totals accumulate as games are played; refresh periodically during the season rather than relying on a one-time pull.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA player stats

Retrieves NBA player season statistics for the requested year, including player ID, box scores, and performance metrics.

Purpose: A comprehensive overview of player performance for a season, via box scores.

Use cases:

  • Strategic planning — analyze player box scores and related stats.
  • Performance analysis — compare a player's regular-season and postseason totals.

Best practices:

  • Season totals accumulate as games are played; refresh periodically during the season rather than relying on a one-time pull.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAABB player stats

Retrieve player season statistics for College Basketball (NCAABB) for the requested season.

Purpose: Returns aggregated regular-season player stats — box-score totals such as points, rebounds, assists, minutes, and shooting — per player.

Use cases:

  • Strategic planning: analyze player box scores for statistical and strategic purposes.
  • Performance analysis: compare and rank players by their season-total box scores.

Best practices:

  • Season totals update as games are played; refresh periodically during the season rather than relying on a one-time pull.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

The year the season started (e.g. 2025), not a date.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAAFB player stats

Retrieve player season statistics for College Football (NCAAFB) for the requested year — each player's season box-score totals (games played plus passing, rushing, receiving, defensive, and special-teams stats), keyed by player ID and team.

Use cases:

  • Support strategic planning with season-level player box scores.
  • Assess player performance trends across a season to identify peak and poor stretches.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL player stats

Retrieves NFL player season statistics for the requested year, including player ID, box scores, and performance metrics.

Purpose: A comprehensive overview of player performance for a season, via box scores.

Use cases:

  • Strategic planning — analyze player box scores and related stats.
  • Performance analysis — compare a player's regular-season and postseason totals.

Best practices:

  • Season totals accumulate as games are played; refresh periodically during the season rather than relying on a one-time pull.

DraftKings fantasy points: DK_fantasy_points is the player's season total under DraftKings NFL scoring; DK_fantasy_points_per_game divides it by games played. Scoring rules:

  • Passing — 0.04 points per yard; 4 points per touchdown; −1 point per interception; 2 points per two-point conversion pass; +3 bonus for a 300+ yard game.
  • Rushing — 0.1 points per yard; 6 points per touchdown; 2 points per two-point conversion rush; +3 bonus for a 100+ yard game.
  • Receiving — 1 point per reception; 0.1 points per yard; 6 points per touchdown; 2 points per two-point conversion reception; +3 bonus for a 100+ yard game.
  • Special teams & miscellaneous — 6 points per kick, punt, field-goal, or fumble return touchdown; −1 point per fumble lost; 1 point per extra point made.
  • Kickers — 3 points per made field goal of 0–39 yards, 4 points for 40–49 yards, 5 points for 50+ yards; no deduction for misses.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL player stats

Retrieves season-level player statistics for NHL skaters and goalies — regular-season and postseason box-score totals for the requested season.

Use cases:

  • Strategic planning from player box scores.
  • Analyze a player's performance trends across a season, identifying peak and low periods.

Best practices: Season totals update as games are played; refresh periodically during the season rather than relying on a one-time pull.

Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

PGA golfer stats

Retrieves golfer season stats for PGA.

Purpose of the endpoint

  • What it does: Retrieves player season stats related to PGA golfers, including wins, events, points, rounds, top-ten finishes, cuts made, and world ranking.
  • Why it exists: Provides a comprehensive overview of golfer performance for the season, helping users analyze performance and make informed decisions.

Use cases

  • Strategic planning: Analyze golfer performance and related information for statistical and strategic purposes.
  • Performance analysis: Track golfer performance trends over a season.

Best practices and tips

  • Use the correct endpoint without any spaces. Endpoint names are case-sensitive.
  • For PGA use PGA as the sport identifier followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /player-stats?RSC_token=...
  • /player-stats/PGA?RSC_token=...
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER player stats

Season-long player statistics for the given {season} (the four-digit year the season started, e.g. 2025) — goals, assists, minutes, cards, shots, plus goalkeeper metrics like saves and clean sheets, per player, with a per-team breakdown for players who changed clubs mid-season.

Use cases:

  • Build player performance profiles and leaderboards.
  • Compare a player's split stats across teams after a mid-season transfer.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025
query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Team Info

Team identities, venues, and franchise details.

MLB team info

Retrieves information for all MLB teams, including team ID, name, abbreviation, mascot, and conference, plus venue and location details (city, state, arena, coordinates).

Purpose: A comprehensive overview of the teams participating in MLB.

Use cases:

  • Look up team details.
  • Resolve the team associated with a player for more specific queries (e.g. box scores by team_id or player_id).
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA team info

Retrieves information for all NBA teams, including team ID, name, abbreviation, mascot, and conference.

Purpose: A comprehensive overview of the teams participating in the NBA.

Use cases:

  • Look up team details.
  • Resolve the team associated with a player for more specific queries (e.g. box scores by team_id or player_id).
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAABB team info

Retrieve team information for College Basketball (NCAABB).

Purpose: Returns details for every NCAABB team — team ID, name, abbreviation, mascot, conference, AP ranking, and location/arena — for a comprehensive view of participating programs.

Use cases:

  • Look up team details for a fuller understanding of each program.
  • Reference team IDs and metadata when querying the game, player, or stats endpoints.

Best practices:

  • Refresh team info periodically rather than requesting it on every call.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAAFB team info

Retrieve team information for College Football (NCAAFB) — a comprehensive overview of participating teams (team ID, mascot, conference, venue, and more).

Use cases:

  • Look up team details such as mascot, conference, and venue for reference and display.
  • Associate teams with players via team_id for more specific queries such as box-score results.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL team info

Retrieves information for all NFL teams, including team ID, name, abbreviation, mascot, conference, and home-venue details (city, state, arena, playing surface, dome).

Purpose: A comprehensive overview of the teams participating in the NFL.

Use cases:

  • Look up team details.
  • Resolve the team associated with a player for more specific queries (e.g. box scores by team_id or player_id).
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL team info

Retrieves reference information for all NHL teams — team ID, name, abbreviation, conference/division, arena and location.

Use cases:

  • Look up team details for display or reference.
  • Resolve a team ID to pair with player, schedule, or box-score queries.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER team info

Directory of SOCCER teams — IDs, abbreviations, home venue, city, country, and coordinates — for every club in the requested league, including clubs previously relegated from it.

Use cases:

  • Look up team information for a more detailed understanding.
  • Combine with the schedule endpoints to build a breakdown of the two teams in an upcoming game.

Best practices: Filter with the relegated query parameter: TRUE for relegated clubs, FALSE for current clubs; omit it for both.

Authorizations:
RSC_token
query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Team Stats

Season-level statistics for teams.

MLB team stats

Retrieves MLB team season statistics for the requested season, including team ID, team name, and box-score totals (wins, losses, and batting counts such as hits, runs, home runs, and RBI) for the regular season and postseason.

Purpose: A comprehensive overview of teams' stats for a given season.

Use cases:

  • Strategic planning — analyze team box scores and related information.
  • Performance analysis — compare a team's regular-season and postseason totals.

Best practices:

  • Season totals accumulate as games are played; refresh periodically during the season rather than relying on a one-time pull.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA team stats

Retrieves NBA team season statistics for the requested season, including team ID, team name, and box-score totals.

Purpose: A comprehensive overview of teams' stats for a given season.

Use cases:

  • Strategic planning — analyze team box scores and related information.
  • Performance analysis — compare a team's regular-season and postseason totals.

Best practices:

  • Season totals accumulate as games are played; refresh periodically during the season rather than relying on a one-time pull.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAABB team stats

Retrieve team season statistics for College Basketball (NCAABB) for the requested season.

Purpose: Returns aggregated regular-season team stats — box-score totals such as points, rebounds, assists, and shooting — per team for the season.

Use cases:

  • Strategic planning: analyze team performance box scores for statistical and strategic purposes.
  • Performance analysis: compare and rank teams by their season-total box scores.

Best practices:

  • Season totals update as games are played; refresh periodically during the season rather than relying on a one-time pull.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

The year the season started (e.g. 2025), not a date.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAAFB team stats

Retrieve team season statistics for College Football (NCAAFB) for the requested season — each team's box-score totals (team ID, team name, and more).

Use cases:

  • Support strategic planning with season-level team box scores.
  • Assess team performance trends across a season to identify peak and poor stretches.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2024

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL team stats

Retrieves NFL team season statistics for the requested season, including team ID, team name, bye week, and box-score totals.

Purpose: A comprehensive overview of teams' stats for a given season.

Use cases:

  • Strategic planning — analyze team box scores and related information.
  • Performance analysis — compare a team's regular-season and postseason totals.

Best practices:

  • Season totals accumulate as games are played; refresh periodically during the season rather than relying on a one-time pull.

DraftKings fantasy points: DK_fantasy_points is the team's defense/special-teams season total under DraftKings NFL scoring; DK_fantasy_points_per_game divides it by games played. Scoring rules:

  • 1 point per sack; 2 points per defensive interception, fumble recovery, safety, blocked kick, or blocked punt.
  • 6 points per return touchdown — punt, kick, field-goal, interception, fumble, blocked-punt, or blocked-kick return.
  • 2 points per two-point conversion return.
  • Points-allowed modifier, from the points scored against the defense/special teams: 0 → +10, 1–6 → +7, 7–13 → +4, 14–20 → +1, 21–27 → 0, 28–34 → −1, 35+ → −4.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL team stats

Retrieves season-level team statistics for NHL teams — regular-season and postseason box-score totals for the requested season.

Use cases:

  • Strategic planning from aggregated team box scores.
  • Analyze team performance trends across a season, identifying peak and low periods.

Best practices: Season totals update as games are played; refresh periodically during the season rather than relying on a one-time pull.

Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER team stats

Season-long team statistics for the given {season} (the four-digit year the season started, e.g. 2025) — wins, draws, goals scored and conceded, cards, shots, corners, and more, per club. Clubs relegated from the league have regular_season returned as null.

Use cases:

  • Strategic planning: analyze team performance box scores for statistical and strategic purposes.
  • Performance analysis: power standings and team pages within a website.
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2025
query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Depth Charts

Positional depth charts per team.

MLB depth charts

Retrieves each MLB team's depth chart — the players at each fielding position and pitching role, ranked by depth with the starter (first string) listed first, followed by replacement and platoon players — including team, player ID, and position.

Purpose: A comprehensive overview of position assignments and team composition.

Use cases:

  • Performance tracking — track player performance relative to their position on the depth chart.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA depth charts

Retrieves each NBA team's depth chart — the players at each position, with the starter (first string) listed first, followed by replacement and platoon players — including team, player ID, and position.

Purpose: A comprehensive overview of position assignments and team composition.

Use cases:

  • Performance tracking — track player performance relative to their position on the depth chart.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NCAABB depth charts

Retrieve positional depth charts for College Basketball (NCAABB) teams.

Purpose: Returns each team's depth chart — for every position (PG, SG, SF, PF, C), players listed in depth order from the starter down. The response is keyed by team, then position, then depth index.

Use cases:

  • See projected starters and rotation order for each team.
  • Combine with player-info and player-stats to build lineup or matchup views.

Best practices:

  • Depth charts shift with lineup and roster changes — refresh before relying on starter/rotation order.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL depth charts

Retrieves each NFL team's depth chart — the players at each position, with the starter (first string) listed first, followed by replacement and platoon players — including team, player ID, and position.

Purpose: A comprehensive overview of position assignments and team composition.

Use cases:

  • Performance tracking — track player performance relative to their position on the depth chart.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL depth charts

Retrieves each NHL team's depth chart — the players at each position, ordered with the starter/first-string listed first, followed by backups.

Use cases:

  • Track a player's standing at their position on the depth chart.
  • Understand team composition and roster ordering.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER depth charts

Depth charts for SOCCER teams in the requested league — each club's players arranged by position (Goalkeeper, Defender, Midfielder, Forward) and depth-chart slot. Unfilled slots are returned as null.

Use cases:

  • See projected starters and squad depth by position.
  • Combine with player info or stats to scout a team's lineup.
Authorizations:
RSC_token
query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Injuries

Current injury reports per team.

MLB injuries

Retrieves MLB injury reports grouped by team, including each injured player, their player ID, the type of injury, the date injured, and their return status (e.g. a 60-day injured-list stint).

Purpose: A comprehensive overview of player injuries, to help you stay informed about player availability and health.

Use cases:

  • Gauge a player's availability for upcoming games from the injury type, date injured, and return status.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NBA injuries

Retrieves NBA injury reports grouped by team, including each injured player, their player ID, the date injured, and their expected return.

Purpose: A comprehensive overview of player injuries, to help you stay informed about player availability and health.

Use cases:

  • Gauge a player's availability for upcoming games from the date injured and their expected return.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NFL injuries

Retrieves NFL injury reports grouped by team, including each injured player, their player ID, the injury, the date injured, and their expected return.

Purpose: A comprehensive overview of player injuries, to help you stay informed about player availability and health.

Use cases:

  • Gauge a player's availability for upcoming games from the injury, date injured, and expected return.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

NHL injuries

Retrieves current injury reports for NHL players — injury type, return status and the date injured, plus the affected player and team.

Use cases:

  • Gauge player availability for upcoming games from the injury type and return status.
Authorizations:
RSC_token

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

SOCCER injuries

Current injury report for SOCCER teams in the requested league — injured player, injury type, date injured, and expected return, grouped by team.

Use cases:

  • Track player availability ahead of upcoming fixtures.
  • Flag squad changes when building lineups or projections.

Best practices: Check before each fixture and reconcile against depth-charts to gauge line-up impact.

Authorizations:
RSC_token
query Parameters
league
required
string (SoccerLeague)
Enum: "EPL" "SERIEA" "LALIGA"
Example: league=EPL

Soccer league to return data for.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Events

Darts event listings for a season.

Darts events

Retrieves event details for Darts games for a particular year specified in the endpoint.

Purpose of the endpoint

  • What it does: Retrieves event details data for a year for all events, including details such as event name, event IDs, and more.
  • Why it exists: Provides an overview of the events happening for the particular year, offering users the information they need about events in that season.

Use cases

  • Access the entire season events to gather information and conduct assessments. Recommended only once at the start of the year.
  • Display when events are happening and their dates.
  • Use event_ID for more specific detail queries like game score results.

Best practices and tips

  • Use the correct endpoint without any spaces. All endpoint naming is case-sensitive.
  • In the request URL, provide the season year (YYYY) for the events you need.
  • For Darts games use DARTS as the sport identifier followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /events/2026/DARTS?RSC_token=...
  • /events/2026/DARTS?RSC_token=...&event_id=202304PL10

Special data point values

Field Description Example
event_name Name of the event PDC World Championship, Premier League, UK Open, etc.
start_date Start date of the event GMT datetime string
end_date End date of the event GMT datetime string
event_ID Unique event identifier 202304PL10
Authorizations:
RSC_token
path Parameters
season
required
string
Example: 2026

Season year (YYYY).

query Parameters
event_id
string
Example: event_id=202304PL10

One specified event ID.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Field

The field of players for PGA tournaments.

PGA tournament field

Retrieves the field for a PGA tournament, including tee times, starting holes, and hole-by-hole data when available.

Purpose of the endpoint

  • What it does: Retrieves the tournament field for a specified tournament ID, including player names, tee times, starting holes, and per-round hole results (par, score, sequence).
  • Why it exists: Provides the confirmed field, tee sheet, and scoring detail for a tournament before and during play.

Use cases

  • Display the tournament field, tee times, and starting holes.
  • Use player IDs from the field keys for more specific live or stats queries.

Best practices and tips

  • Use the correct endpoint without any spaces. Endpoint names are case-sensitive.
  • A tournament ID (game_id) MUST be specified when requesting the field list.
  • For PGA tournaments use PGA as the sport identifier followed by your RSC_token (required).
  • For detailed information on obtaining and using the RSC_token, contact support.

URL examples

  • /field/PGA?RSC_token=...&game_id=2026_74

Special data point values

Field Description
Round {N}.Hole {N} { par, score, sequence } — par and score are strings; sequence is the hole order number
tee_times Tee time per round (RFC 2822 GMT)
starting_holes Starting hole number per round (e.g. 1 or 10)
Authorizations:
RSC_token
query Parameters
game_id
required
string
Example: game_id=2025_61

One specified tournament ID. Only PGA must be specified when using this parameter. If PGA is among multiple SPORT parameters, game_id cannot be specified.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}