Docs
Coverage MatrixDocumentationRelease LogLog In

Frequently asked questions for Tennis v3

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

Categories

.


Coverage


What leagues or tournaments do you cover, and at what level?

You can find all the leagues we cover, as well as a breakdown of data offered, via our Coverage Matrix.


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

Find the node called: coveragetype which denotes if the match is covered at the sport_event or competition level.

  • When type="sport_event" you will only get sport_event_properties.
  • When type="competition" you will get sport_event_properties and competition_properties.

Within coverage, scores states if the match is scored live or post. Extended stats show if we have enhanced stats for the sport event.


How are “live” feeds 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.


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.



Integration


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:
https://api.sportradar.com/tennis/trial/v3/openapi/swagger/index.html


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_statusstatus values?

  • not_started – The match is scheduled to be played
  • started – The match has begun
  • postponed – The match has been postponed to a later time
  • match_about_to_start – The match time has expired, awaiting play
  • live – The match is currently in progress
  • ended – The match is over
  • closed – The match results have been confirmed.
  • 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
  • suspended – The match began, but has been suspended to a later time
  • cancelled – The match has been cancelled and will not be played
  • delayed – The match has been temporarily delayed and will be continued

What are the valid sport_event_statusmatch_status values?

  • not_started – The match is scheduled to be played
  • match_about_to_start – The match time has expired, awaiting play
  • start_delayed – The match has been temporarily delayed and will be continued. Matches are manually moved to this status 15 minutes after the scheduled start time.
  • 1st_set – First set
  • 2nd_set – Second set
  • 3rd_set – Third set
  • 4th_set – Fourth set
  • 5th_set – Fifth set
  • ended – The match is over
  • walkover - The match ended in a walkover
  • interrupted – The match began, but is stopped for a short time
  • suspended – The match began, but has been suspended to a later time
  • cancelled – The match has been cancelled and will not be played
  • postponed – The match has been postponed to a future date
  • retired – The match is incomplete as the result of one player
  • defaulted - The match has ended as a result of one player being disqualified

How does sport event type work in the feeds?

The sport_event_type explicitly denotes the match type.

Where there are competitions which have "parent matches" and "child matches" where country_format='true', such as Davis Cup and ATP Cup, this attribute will only appear on the "child match" node.

The "parent match" sport_event node will have a type='parent' attribute and the competition node will have a type='mixed' attribute. Otherwise, for competitions where country_format is not present, the competition will have a type either singles or doubles.



Statistics


Is the statistical data provided in the Tennis API official data?

Sportradar collects sports data independently. For some sports Sportradar is the official data provider. In the case of Tennis, we provide official data for ITF tournaments only.


What are the definitions for the various statistics?

General Definitions:

  • Racket arm: The arm with which the player serves and holds the racket. It is used to define if a player is right-handed or left-handed.
  • Stroke/Shot: The act of striking the ball with the racket.
  • Serve: Short for Service.
  • Server: The player who serves.
  • Returner/Receiver: The player who receives the serve.
  • Return: A shot used to hit back the serve.
  • Forehand: A shot hit from the racket-arm side of the body. The stroke used to return balls hit to the right side of a right-handed player and to the left side of a left-handed player. Forehands are commonly hit one-handed.
  • Backhand: A stroke in which the ball is struck on the opposite side of the body to the racket arm. The stroke is used to return balls hit to the left side of a right-handed player and to the right side of a left-handed player. Backhands are hit either one-handed or two-handed.
  • Groundstroke: A stroke made after the ball has bounced. The standard shot in tennis. Can be either forehand or backhand.
  • Volley: During play, a shot where the ball is hit before it bounces. Can be either forehand or backhand.
  • Overhead: During play, a stroke made with the racket above the head in a motion similar to that of an overhand serve.
  • Drop Shot: A softly hit ball (usually with backspin) that drops near the net after crossing it. Is hit either as a groundstroke or a volley and can be either forehand or backhand.
  • Lob: A stroke that lifts the ball high in the air, usually over the head of the opponent at the net. Is hit either as a groundstroke or a volley and can be either forehand or backhand.

Sportradar Definition – Winners

  • Winner: A winner is any shot that is hit successfully into the opposite side of the court that the opponent can’t manage to get a shot at. It can either be a clean hit without any racket touch or where the opponent only manages to slightly touch the ball (racket clip). Important is that the opponent cannot manage to hit a proper shot. All the below specifications count as Winners in Statistics.
  • Ace: A ball that is served without an opponent (receiver) touching the ball with the racket (usually due to well executed serve)
  • Return winner: A direct winner hit when returning serve. Can be either forehand or backhand.
  • Groundstroke winner: A winner hit as a groundstroke. Can be either forehand or backhand.
  • Volley winner: A winner hit as a volley. Can be either forehand or backhand.
  • Overhead winner: A winner hit as an overhead shot.
  • Drop shot winner: A winner hit as a drop shot. Has to be either groundstroke or volley and can be either forehand or backhand.
  • Lob winner: A winner hit as a lob. Has to be either groundstroke or volley and can be either forehand or backhand.

Sportradar Definition – Forced errors

  • Forced error: An unsuccessful shot caused by an opponent's good play. Primarily defined when the player who made the error is under time pressure or is on the move/on the defense during the shot execution. If one of those factors is true, then the player was forced into a difficult situation by a good shot and thus made a forced error. All the below specifications count as Forced Errors in Statistics.
  • Return forced error: A forced error caused by an opponent`s serve, player gets racket to the ball but is unable to put it in play (incl. Racket Clip).
  • Groundstroke forced error: A forced error while trying to hit a groundstroke. Can be either forehand or backhand.
  • Volley forced error: A forced error while trying to hit a volley. Can be either forehand or backhand.
  • Overhead forced error: A forced error while trying to hit an overhead shot.

Sportradar Definition – Unforced errors

  • Unforced error: An unsuccessful shot due to an error without being forced under pressure by the opponent. All the below specifications count as Unforced Errors in Statistics.
  • Double fault: Two faults served in a row. On a double fault, the server loses the point.
  • Return unforced error: An unforced error while trying to hit a return of serve. Can be either forehand or backhand.
  • Groundstroke unforced error: An unforced error while trying to hit a groundstroke. Can be either forehand or backhand.
  • Volley unforced error: An unforced error while trying to hit a volley. Can be either forehand or backhand.
  • Overhead unforced error: An unforced error while trying to hit an overhead shot.
  • Drop shot unforced error An unforced error while trying to hit a drop shot. Has to be either groundstroke or volley and can be either forehand or backhand.
  • Lob unforced error: An unforced error while trying to hit a lob. Has to be either groundstroke or volley and can be either forehand or backhand.

When are standard match stats available?

Standard match stats are available whenever live point-by-point coverage is true.


What are the standard match statistics?

  • aces
  • double_faults
  • games_won
  • max_games_in_a_row
  • max_points_in_a_row
  • points_won
  • breakpoints_won
  • total_breakpoints
  • first_serve_points_won
  • first_serve_successful
  • second_serve_points_won
  • second_serve_successful
  • aces
  • double_faults
  • second_serve_successful
  • second_serve_points_won

Which statistics are considered extended match stats and which are standard stats?

  • backhand_errors
  • backhand_unforced_errors
  • backhand_winners
  • volley_errors
  • volley_unforced_errors
  • volley_winners
  • forehand_errors
  • forehand_unforced_errors
  • forehand_winners
  • groundstroke_errors
  • groundstroke_unforced_errors
  • groundstroke_winners
  • lob_unforced_errors
  • lob_winners
  • overhead_errors
  • overhead_stroke_errors
  • overhead_winners
  • return_errors
  • return_unforced_errors
  • return_winners
  • service_unforced_errors
  • service_games_won
  • service_points_lost
  • service_points_won
  • tiebreaks_won
  • drop_shot_unforced_errors
  • drop_shot_winners


Match Updates


How long are matches stored in the deleted/updated matches endpoints?

The deleted/updated matches endpoints will show sport events removed or updated in the last 2 weeks.


When are placeholder competitors used?

We will create fixtures in advance when details are confirmed (fixed draw competitions only). For competitors that have placeholder names, we will display virtual=”true” until the competitor qualifies for the match and replaces the placeholder. Placeholders are not used for qualifiers.


What prompts a match to appear in Sport Events Updated?

Changes to score, match status, or schedule in last 24 hours would cause a match to display in this endpoint.