Coverage MatrixDocumentationRelease LogLog In

Global Football FAQs

Frequently asked questions for Global American Football v2

Click on the categories below or browse questions on the right panel.




What leagues do you cover, and at what level?

Coverage information can be found via our Coverage Matrix

Please note that sr:competition:27653 (NCAA, Regular Season) includes DI, DII, and DIII games.

How do I find out the coverage for a particular match?

Find the node called coverage in any of the Summary, Lineups, or Timeline feeds. The attribute reports if Sportradar has live coverage of the match or not.

Why do different groups have coverage information for a competition?

The notion of “groups” is versatile and is used to distinguish between playoffs, and our competition structures and is therefore necessary to describe coverage at a group level for consistency. Generally, however, within a competition in Football, there will be no difference between competition coverage.

How are “live” endpoints handled in the API?

Sport Events appear in the feed 10 minutes before the scheduled start time and are removed 10 minutes after the Sport Event is ended. Live endpoints include: Live Summaries, Live Timelines, and Live Timelines Delta.

How will a sport event behave when it is not covered with live scores?

When a sport_event is not covered live, the status and match_status will remain as not_started until results are entered post-match.

<sport_event_status status="not_started" match_status="not_started"/>


How can I find the values for various enum data points within the API?

Many enum values are listed in the FAQ below. For the most up-to-date values, please see the Schema section of the OpenAPI specification here.

What format are date fields presented in?

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:

What format are the date/time fields presented in?

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:

How do I locate the TTL (Time to Live)/cache on an API endpoint?

The cache (in seconds) can be accessed in the returned header information on each RESTful API call, under cache-control.

ex. cache-control: max-age=1, public, s-maxage=1 or
cache-control: public, must-revalidate, max-age=120

Sport Event Statuses

What are the valid sport_event_status - status values?

Here are the valid sport_event_status values and their definitions:

  • not_started – The match is scheduled to be played
  • started – The match has begun
  • live – The match is currently in progress
  • postponed – The match has been postponed to a future date
  • `suspended - The match began, but has been suspended to a later time
  • delayed – The match has been temporarily delayed and will be continued
  • cancelled – The match has been cancelled and will not be played
  • match_about_to_start – The match is about to begin
  • interrupted - The match began, but coverage has stopped for a short time. Note that match scores may not be updated during this period, the last recorded match score will be displayed instead
  • ended – The match is over
  • closed – The match results have been confirmed

What are the valid sport_event_statusmatch_status values?

Here are the valid match_status values:

  • not_started
  • ended
  • postponed
  • cancelled
  • interrupted
  • overtime
  • abandoned
  • 1st_quarter
  • 2nd_quarter
  • 3rd_quarter
  • 4th_quarter
  • pause
  • awaiting_extra_time
  • aet
  • start_delayed

Event Types

What are the possible event types logged?

Here are the valid event type:

  • match_started
  • period_start
  • score_change
  • period_score
  • break_start
  • match_ended