Docs
Coverage MatrixDocumentationRelease LogLog InContact Us
Coverage MatrixDocumentationRelease LogLog InContact Us

FAQs

Frequently asked questions for Field Hockey v2

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

Categories

.

Coverage


What leagues do you cover, and at what level?

Coverage information can be found via our Coverage Matrix.


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 coverage - live reports if Sportradar has live coverage of the match or not.


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.


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 Field Hockey, there will be no difference between competition coverage between conferences.


Integration


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: https://en.wikipedia.org/wiki/ISO_8601


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: https://en.wikipedia.org/wiki/ISO_8601


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?

  • not_started – The match is scheduled to be played
  • live – The match is currently in progress
  • postponed – The match has been postponed to a future date
  • delayed – The match has been temporarily delayed and will be continued
  • 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
  • cancelled – The match has been cancelled and will not be played
  • ended – The match is over
  • closed – The match results have been confirmed

Event Types


What are the point event possible values?

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

Probabilities


What are markets and what are the different markets?

Markets is something you can bet on that we provide probabilities for. Over time we intend to provide more and more markets in the API. Currently the only market we provide is 3-way (will the home team win? Or the away team? Or will it be a draw?).


What are the valid outcomes for probabilities?

  • home_team_winner
  • away_team_winner

Past Season Data


How do I access past seasons results and stats?

Use the Competition Seasons endpoint to locate the season_id for the season you want to access. Use that season_id to interrogate the various seasons endpoints.


Standings / Tournaments


What are the possible standings types in the Standings endpoint?

  • total
  • home
  • away
  • first_half_total
  • first_half_home
  • first_half_away
  • second_half_total
  • second_half_home
  • second_half_away

What are the possible values for cup_round – state in the Season Links endpoint?

Listed below are the values and definitions for cup_round - state. These can be leveraged to determine the status of a cup round.

  • empty - A matchup has been created but neither the match details nor the competitors are known.
  • unseeded_fixture - Match details are known but competitors are unknown.
  • partial_seeded - One competitor is known.
  • partial_seeded_fixture - Match details and one competitor are known.
  • seeded - Both competitors are known.
  • seeded_fixture - Match details and both competitors are known.
  • unstarted - Match(es) have been added.
  • on_going - The first match has started.
  • decided - The last match has ended.
  • winner - The winner is known.
  • cancelled – The matchup has been cancelled.

How are group IDs delivered in the stage array with the various types?

With the type of "league" they will have a sr:league prefix.
With the type of "cup" they will have a sr:cup prefix.



🙋

More questions?

Reach out to [email protected] for further assistance.


© Sportradar AG, St. Gallen, Switzerland