NFL Insights v1

Frequently Asked Questions ## NFL Insights API Overview Sportradar’s NFL Insights product delivers data points and text outputs specifically tailored to create additional context around a game. We provide player highs, milestones, leaderboards, predictions, player and team betting trends, and more. These insights help drive tune-in, facilitate the placement of real money bets, and empower deeper sports stories. Sportradar Insights can be accessed via our radar360 user interface or directly from the API. For trial access to this product, feel free to reach out to our sales team.
API API Version Postman Collection
Advanced Insights - NFL Insights v1
Note: Authentication is required for all API calls.

Authorization must be passed within the header of all calls to the API as: Authorization: {your_auth_token}
## Insights ```ruby require "uri" require "net/http" url = URI("https://api.radar360.sportradar.com/insights/v1/nfl") https = Net::HTTP.new(url.host, url.port) https.use_ssl = true request = Net::HTTP::Get.new(url) request["Authorization"] = "{your_auth_token}" response = https.request(request) puts response.read_body ``` ```python import http.client conn = http.client.HTTPSConnection("api.radar360.sportradar.com") payload = '' headers = { 'Authorization': '{your_auth_token}' } conn.request("GET", "/insights/v1/nfl", payload, headers) res = conn.getresponse() data = res.read() print(data.decode("utf-8")) ``` ```shell curl --location --request GET 'https://api.radar360.sportradar.com/insights/v1/nfl' \ --header 'Authorization: {your_auth_token}' ``` > The API returns json structured like this. This endpoint retrieves Insights. https://api.radar360.sportradar.com/insights/`{version}`/nfl Replace placeholders with the following query parameters: | Parameter | Description | | --------- | ----------- | | `version` | Version number of the API you are accessing (Current Version: v1). | ### Optional Query String Parameters >Example including optional query string parameters:
require "uri"
require "net/http"

url = URI("https://api.radar360.sportradar.com/insights/v1/nfl?types=highs&index=50")

https = Net::HTTP.new(url.host, url.port)
https.use_ssl = true

request = Net::HTTP::Get.new(url)
request["Authorization"] = "{your_auth_token}"

response = https.request(request)
puts response.read_body
import http.client

conn = http.client.HTTPSConnection("api.radar360.sportradar.com")
payload = ''
headers = {
  'Authorization': '{your_auth_token}'
}
conn.request("GET", "/insights/v1/nfl?types=highs&index=50", payload, headers)
res = conn.getresponse()
data = res.read()
print(data.decode("utf-8"))
curl --location --request GET 'https://api.radar360.sportradar.com/insights/v1/nfl?types=highs&index=50' \
--header 'Authorization: {your_auth_token}'
In addition to the URL parameters listed above, you can filter the insights with one or more of the following optional query string parameters. By default, the insights endpoint displays 50 results. To see more results use the index parameter.
Note: Optional query string parameters must be added after the URL with a question mark (?) and must be separated with an ampersand (&).
Replace placeholders with the following query parameters: | Parameter | Description | | --------- | ----------- | | `index` | Number to start the list of results from.
Example: index=50 | | `pageSize` | Number to limit the number of results. Minimum value is 1, maximum value is 50.
Example: pageSize=10 | | `custom` | Filters to display a subset of the results payload.
Example: custom=content,event | | `types` | Insight types (expert_picks, game_notes, highs, leaderboards, lineup_changes, milestones, predictions, player_betting_trends, scoring, team_betting_trends) | | `typeIds` | Insight type ids | | `sources` | Source keys (advanced_insights, mocap, research) | | `sourceIds` | Source ids | | `categories` | Source keys (media, betting) | | `categoryIds` | Source ids | | `lifecycles` | Source keys (pre_game, in_game, post_game) | | `lifecycleIds` | Source ids | | `playerIds` | Player ids | | `playerSrIds` | Player sr ids | | `playerUsIds` | Player us ids | | `teamIds` | Team ids | | `teamSrIds` | Team sr ids | | `teamUsIds` | Team us ids | | `gameIds` | Game ids | | `gameSrIds` | Game sr ids | | `gameUsIds` | Game us ids | | `packagesIds` | Package ids | ## Milestone Thresholds ```ruby require "uri" require "net/http" url = URI("https://api.radar360.sportradar.com/insights/thresholds/v1/nfl") https = Net::HTTP.new(url.host, url.port) https.use_ssl = true request = Net::HTTP::Get.new(url) request["Authorization"] = "{your_auth_token}" response = https.request(request) puts response.read_body ``` ```python import http.client conn = http.client.HTTPSConnection("api.radar360.sportradar.com") payload = '' headers = { 'Authorization': '{your_auth_token}' } conn.request("GET", "/insights/thresholds/v1/nfl", payload, headers) res = conn.getresponse() data = res.read() print(data.decode("utf-8")) ``` ```shell curl --location --request GET 'https://api.radar360.sportradar.com/insights/thresholds/v1/nfl' \ --header 'Authorization: {your_auth_token}' ``` > The above command returns json structured like this. This endpoint retrieves Milestone Thresholds. https://api.radar360.sportradar.com/insights/thresholds/`{version}`/nfl Replace placeholders with the following query parameters: | Parameter | Description | | --------- | ----------- | | `version` | Version number of the API you are accessing (Current Version: v1). | ## Frequently Asked Questions

Q: What is the Date format?

A: When we present date only values we present these in the ISO 8601 standard format.
ex: 2013-04-03
We use these for attributes that have date and no time (such as birthdate). For more information: https://en.wikipedia.org/wiki/ISO_8601

Q: What time zone are the date time fields presented in?

A: All of our Date/Time attributes are in UTC, presented in the ISO 8601 standard format.
ex: 2013-04-03T18:15:00+00:00
For more information: https://en.wikipedia.org/wiki/ISO_8601

Q: What is the benefit of using this API?

A: The Insights API allows you to access a variety of different Insight types all under one call, versus having to integrate with all the various individual Insight APIs.

Q: When should I expect to see Insights come through?

A: There are a number of Insights that populate each morning. Then, when games begin, Insights are generated in real-time.

Q: What career milestone thresholds are available?

A: We support the following career thresholds:

  • career_player_passing_attempts
  • career_player_passing_completions
  • career_player_passing_yards
  • career_player_passing_touchdowns
  • career_player_passing_interceptions
  • career_player_receptions
  • career_player_targets
  • career_player_receiving_yards
  • career_player_receiving_touchdowns
  • career_player_rushing_attempts
  • career_player_rushing_yards
  • career_player_rushing_touchdown
  • career_player_defensive_sacks
  • career_player_interceptions
  • career_player_defensive_touchdowns
  • career_player_total_tackles
  • career_player_solo_tackles
  • career_player_tackles_for_loss
  • career_player_fumbles_forced
  • career_player_defensive_hurries
  • career_player_extra_points_made
  • career_player_field_goals_made

Q: What season milestone thresholds are available?

A: We support the following season thresholds:

  • season_player_passing_attempts
  • season_player_passing_completions
  • season_player_passing_yards
  • season_player_passing_touchdowns
  • season_player_passing_interceptions
  • season_player_receptions
  • season_player_targets
  • season_player_receiving_yards
  • season_player_receiving_touchdowns
  • season_player_rushing_attempts
  • season_player_rushing_yards
  • season_player_rushing_touchdown
  • season_player_defensive_sacks
  • season_player_interceptions
  • season_player_defensive_touchdowns
  • season_player_total_tackles
  • season_player_solo_tackles
  • season_player_tackles_for_loss
  • season_player_fumbles_forced
  • season_player_defensive_hurries
  • season_player_extra_points_made
  • season_player_field_goals_made
Return to top

Docs Navigation