Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
We recommend the following frequency for your REST requests to ensure that you have the most up-to-date information at all times:
REST Endpoint
Frequency
/tournaments/liveevents
Every 10 seconds
/tournaments/{id}/draws
Every minute
/tournaments/{id}/events
Every minute
/tournaments
Every 12 hours
/players
Every week
IMG suggests the above recommendations because of the order in which we value these updates.
Polling the /liveevents endpoint is essential when attempting to connect to an event at the earliest possible convenience. If this was polled any less then every 10 seconds, then you may not connect to a game as quickly as you may like.
Polling the /draws and /events endpoints is only needed every minute because it is not as vital to know draw or Order of Play (OOP) updates as it is to know that a match is live. These updates include draw updates like player changes or OOP updates such as court changes.
The /tournaments endpoint should be polled every 12 hours because IMG generally only receive information on new tournaments two to three times a week, for events months in advance.
Lastly, polling the /players endpoint anymore than once a week does not offer a value as IMG only receives player updates once per week. This is due to player information (e.g. ranking) only changing post-tournament and not mid-tournament.
All REST endpoints have a dedicated page and contain our recommended frequency of rest requests
This endpoint lists the currently live booked events for which you are licenced. This allows you to determine which events have live streams available.
URL: https://dde-api.data.imgarena.com/tournaments/liveevents
We recommend that you request this REST endpoint every 10 seconds so that you have the most up-to-date information on the events that are currently live on the DDE.
You will use the response from this end point to decide which live streams that you should connect to. As soon as you see a live stream available on this end point you should commence connecting to the websocket for that individual live stream event.
This endpoint currently takes no request parameters, we aim to add them, and once we have they will be detailed here.
An example from the Tournaments Live Events end point in December 2024
New URL: https://dde-api.data.imgarena.com/tournaments/liveevents
This section contains details on the following RESTful endpoints:
Field Name
Type
Description
tournamentName
string
Name of the tournament
eventId
string
Unique identifier for this event
startTime
object
StartTime object indicating when the match was scheduled to start
teamA
object
A team status object describing the first team taking part
teamB
object
A team object describing the second team taking part
This endpoint lists all tournaments for which you are licensed, and you have booked at least one event. With unlimited licences, you will see all tournaments and events as they are automatically booked for you
The /tournaments endpoint will display the following types of information on each tournament:
City (LA)
Location (California)
Country (USA)
Surface
Year
Environment (Indoors or outdoors)
Name
Number of matches
Match Schedule Plan info (expected matches each day)
Draw Sizes
Start/End Date
Competition IDs (2024-0540)
Organisation (ATP/AELTC/USTA/FFT)
We recommend that you request the https://dde-api.data.imgarena.com/tournaments REST endpoint every 12 hours so that you have the most up-to-date information on the tournaments that we offer at all times.
Example requests of this end point:
https://dde-api.data.imgarena.com/tournaments?includeUnbooked=true (includes all matches, booked and unbooked, that you may have for this tournament)
https://dde-api.data.imgarena.com/tournaments?dateFrom=2024-02-28&dateTo=2024-03-01 (All matches between 28 Feb and 1 March)
This endpoint takes the following parameters:
Parameter
Type
Purpose
includeUnbooked
boolean
When set to true we will return a list of all tournaments for which you are licensed irrespective of whether you have booked events in them. If not specified then only booked tournaments are returned
dateFrom
date
Filter the tournaments by date. Only tournaments which have events on or after the specified date will be included.
E.g. dateFrom=2024-06-01
dateTo
date
Filter the tournaments by date. Only tournaments which have events on or before the specified date will be included.
E.g. dateTo=2024-06-30
: Note: api will return a list of LiveEvent when hitting LiveEvents endpoint.
This endpoint returns details for a specific tournament if the id is valid and you are licenced for it
This endpoint should be requested if you want to understand details on a specific tournament. It will display the same types of information as the https://dde-api.data.imgarena.com/tournaments/ endpoint.
We recommend you request this end point on an ad hoc basis whenever you want this information on a specific tournament.
Example requests of this end point:
https://dde-api.data.imgarena.com/tournaments/11904
This endpoint currently takes no request parameters, we aim to add them, and once we have they will be detailed here.
Field Name
Type
Description
sport
string
The sport of the tournament
tournamentName
string
The name of the tournament
city
string
The city where the tournament is being held
status
string
The status of the tournament - Cancelled, Confirmed or Unconfirmed. Note that occasionally scheduled tournaments will not take place (e.g. a sponsor pulls out) in which case the status will be set to Cancelled
location
string
The country or state (US only) and country where the tournament is being held. Note that when a tournament is cancelled, the location will be set to CANCELLED as well. See countryCode for a fixed format location field
countryCode
string
ISO-3166-1 alpha-3 country code of the country where the tournament is taking place. If the country is currently unknown, the code “ZZZ” will be returned.
startDate
date
The date the tournament starts
endDate
date
The date the tournament starts
surface
string
The surface the tournament is being played on. Can be one of Hard, Clay, Grass or Carpet
year
int
The year of the tournament
identifier
int
Identifier for the tournament
environment
string
Whether the tournament is held Indoor or Outdoor
numberOfMatches
int
The number of matches to be played in this tournament. Note that for Tennis and Badminton this number is initially an estimate and will become more accurate as the order of play is released
utcOffset
double
The number of hours difference between the tournament location’s timezone and UTC. Note that this offset does not account for Daylight Saving Time (DST) rules, so at the time of the tournament the actual offset may be slightly different
eventsSummary
object
The number of matches to be played on each day, if known. This data is only available once the order of play for the tournament is released. See object definition below
competitions
array [object]
The competitions which are played as part of the tournament. Generally there is a single tournament but some events have both ATP and WTA competitions. See object definition below
eventsResource
url
Location of details of the tournament events
bookingStatus
string
Indicates if this tournament is booked. One of: “Booked”, “Autobooked”, “NotBooked” or “PartiallyBooked”. PartiallyBooked indicates that some of the events have been booked
venueNames
array [object]
Venue name of where the tournament is hosted. Note if available
Field Name
Type
Description
numberOfMatchesBookedToday
int
Optional field indicating the number of events booked from the tournament if the bookingStatus was “PartiallyBooked”
Field Name
Type
Description
{date}
object
Object containing the number of events on the specified date. There are codes for the types of events: MS - Mens Singles, LS - Ladies Singles, MD/MX - Mens Doubles, LD - Ladies Doubles, XD - Mixed Doubles. The above codes can be prefixed with ‘Q’ to indicate they are part of qualifying for the competition
Field Name
Type
Description
organisation
string
Name of the organisation running the competition (ATP, FFT, AELTC, USTA)
externalId
string
Identifier for the competition. Note that the tournament year and this id uniquely identify a competition e.g. 2024-9028
competitionId
string
Identifier for the competition - this is the year and the externalId
competitionType
string
The competition type - possible values are: Challenger, 250, 500, 1000, GrandSlam, WorldChampionships, Premier, Premier5, Qualifying, Internationals, PremierMandatory, ITF
singlesDrawSize
int
Draw size for the singles competition
singlesQualifyingDrawSize
int
Draw size for the singles qualifying competition
doublesDrawSize
int
Draw size for the doubles competition
doublesQualifyingDrawSize
int
Draw size for the doubles qualifying competition
startDate
date
Start date of the competition
endDate
date
End date of the competition
licensingProperty
string
The license covering the event
drawPoolSize (Round Robin only)
int
The number of teams within each group in the **round robin tournament**
drawNumPools (Round Robin only)
int
The number of groups within the **round robin tournament**
Tournament: Note - Multiple tournaments can be returned after a call in an array.
An example of a request for the tournament end point for the BNP Paribas Open, Indian Wells
https://dde-api.data.imgarena.com/tournaments/10840
This endpoint lists the draws for a tournament. This includes the placeholders for matches in each round of the competition.
A typical Tennis draw is an expected set of matchups within a tennis tournament which is a knockout competition. Every match a player wins, they are entered into the next round of the draw
A Tennis draw on the DDE is first of all defined by the draw type, with each competition in a tennis tournament having its own draw.
For example, the majority of tennis tournaments require one or more qualifying rounds, which typically take place over the weekend before the tournament week starting. On the DDE, a qualifying round can be identified by each match's specific event ID. Event IDs are explained in detail on page.
We recommend that you request the https://dde-api.data.imgarena.com/tournaments/{id}/draws REST endpoint every minute so that you have the most up-to-date information on the draws from live/upcoming tournaments.
This endpoint currently takes no request parameters, we aim to add them, and once we have they will be detailed here.
Filed Name
Type
Description
competitionId
string
Unique identifier for this competition
competitionType
string
Identifies the competition type e.g MD - Mens Doubles, LS - Ladies singles. There will be a draw object for each singles competition in the tournament and each doubles competition. Therefore, for a tournament with both ATP & WTA events there may be 4 or 5 draws
drawSize
int
Number of positions in the draw
entrySize
int
Number of teams in the draw (if not equal to drawSize then some teams will be given byes)
numberOfPools
int
(Round robin tournament only) The number of pools in the round robin
matches
array[object]
Array of Match objects describing the matches that are to be played
Field Name
Type
Description
eventId
string
Unique identifier for this match within the competition - to match this with the eventID returned in the /[id]/events end point you just need to concatenate it with the competitionID
round
int
(Knockout tournament only) Which round of the draw this match is in. The rounds work backwards, with 1 being the final, 2 being the semi finals, 3 the quarters etc
stageType
string
(Round robin only) Indicates if this match is in the group stage or the knockout stage. Values are Group or Knockout
groupId
int
(Round robin only) If a group stage match then this shows the id of the group the match is in
teamA
object
A team status object describing the first team taking part (if known)
teamB
object
A team status object describing the second team taking part (if known)
estimatedDate
date
Indicates the date when the match is likely to be played
estimatesTime
timestamp
Please be advised that this is merely a placeholder until the official Order of Play has been released and will be defaulted to 10am local time
Field Name
Type
Description
status
string
Indicates if the player detail is known for this team. Values are KnownTennisTeam, UnknownTennisTeam or Bye. For UnknownTennisTeam or Bye, no other fields will be present
team
object
A tennis Team Object
Field Name
Type
Description
Player1
object
Player object containing details for the first player in the team
Player2
object
Player object containing details for the second player in the team. Only present if a doubles team
seed
int
This team’s seeding for the competition
entryType
string
This team’s entry type for the competition. Possible values are: Wildcard, Qualifier, LuckyLoser, ProtectedRank, Alternate, SpecialExempt or Standard
An example JSON response of a draws endpoint for the ATP Hamburg European Open in Hamburg, Germany 2022.
Endpoint URL: https://dde-api.data.imgarena.com/tournaments/11904/draws
/tournaments endpoint, but a single Tournament Object.Field Name
Type
Description
sport
string
The sport of the tournament
tournamentName
string
The name of the tournament
city
string
The city where the tournament is being held
status
string
The status of the tournament - Cancelled, Confirmed or Unconfirmed. Note that occasionally scheduled tournaments will not take place (e.g. a sponsor pulls out) in which case the status will be set to Cancelled
location
string
The country or state (US only) and country where the tournament is being held. Note that when a tournament is cancelled, the location will be set to CANCELLED as well. See countryCode for a fixed format location field
countryCode
string
ISO-3166-1 alpha-3 country code of the country where the tournament is taking place. If the country is currently unknown, the code “ZZZ” will be returned.
startDate
date
The date the tournament starts
endDate
date
The date the tournament starts
surface
string
The surface the tournament is being played on. Can be one of Hard, Clay, Grass or Carpet
year
int
The year of the tournament
identifier
int
Identifier for the tournament
environment
string
Whether the tournament is held Indoor or Outdoor
numberOfMatches
int
The number of matches to be played in this tournament. Note that this number is initially an estimate and will become more accurate as the order of play is released
utcOffset
double
The number of hours difference between the tournament location’s timezone and UTC. Note that this offset does not account for Daylight Saving Time (DST) rules, so at the time of the tournament the actual offset may be slightly different
eventsSummary
object
The number of matches to be played on each day, if known. This data is only available once the order of play for the tournament is released. See object definition below
competitions
array [object]
The competitions which are played as part of the tournament. Generally there is a single tournament but some events have both ATP and WTA competitions. See object definition below
eventsResource
url
Location of details of the tournament events
bookingStatus
string
Indicates if this tournament is booked. One of: “Booked”, “Autobooked”, “NotBooked” or “PartiallyBooked”. PartiallyBooked indicates that some of the events have been booked
Field Name
Type
Description
booked
int
Optional field indicating the number of events booked from the tournament if the bookingStatus was “PartiallyBooked”
Field Name
Type
Description
{date}
object
Object containing the number of events on the specified date. There are codes for the types of events: MS - Mens Singles, LS - Ladies Singles, MD/MX - Mens Doubles, LD - Ladies Doubles, XD - Mixed Doubles. The above codes can be prefixed with ‘Q’ to indicate they are part of qualifying for the competition
Field Name
Type
Description
organisation
string
Name of the organisation running the competition (ATP, WTA, FFT, AELTC, USTA, TA or ITF)
externalId
string
Identifier for the competition. Note that the tournament year and this id uniquely identify a competition e.g. 2015-9028
competitionId
string
Identifier for the competition - this is the year and the externalId
competitionType
string
The competition type - possible values are: Challenger, 250, 500, 1000, GrandSlam, WorldChampionships, Premier, Premier5, Qualifying, Internationals, PremierMandatory, ITF
singlesDrawSize
int
Draw size for the singles competition
singlesQualifyingDrawSize
int
Draw size for the singles qualifying competition
doublesDrawSize
int
Draw size for the doubles competition
doublesQualifyingDrawSize
int
Draw size for the doubles qualifying competition
startDate
date
Start date of the competition
endDate
date
End date of the competition
licensingProperty
string
The license covering the event
drawPoolSize (Round Robin only)
int
The number of teams within each group in the **round robin tournament**
drawNumPools (Round Robin only)
int
The number of groups within the **round robin tournament**
This endpoint lists the booked events for a tournament for which you are licenced. Note that the list of events is incomplete and will only show previous events and events for today and tomorrow. As a tournament progresses, matches will be added to the list.
This endpoint will include the order of play (OOP) updates. These include updates to events such as:
A change of court
A change of court sequence (An event is moved from 5th to 1st on a certain court)
A change of scheduled start time
We recommend that you request the https://dde-api.data.imgarena.com/tournaments/{id}/events REST endpoint every minute so that you have the most up-to-date information on the events from live/upcoming tournaments.
This endpoint currently takes no request parameters, we aim to add them, and once we have they will be detailed here.
This endpoint lists the draws for a competition. This includes the placeholders for matches in each round of the competition.
This end point will show the same information as the /tournaments/{id}/draws end point, but for a competition.
The difference between competitions and tournaments is explained here.
We recommend that you request the https://dde-api.data.imgarena.com/competitions/{id}/draws REST end point every minute so that you have the most up-to-date information on the draws from live/upcoming competitions.
Note to pass the competitionId as the {ID} when hitting the /competition endpoint.
CompetitionId for competition type qualifying men's singles for Roland Garross 2024 M"2024-0520". i.e: https://dde-api.data.imgarena.com/competitions/2024-0520/draws
This endpoint currently takes no request parameters, we aim to add them, and once we have they will be detailed here.
An array of Event objects.
Field Name
Type
Description
eventId
string
Unique identifier for this event
date
date
Date the match was played or is scheduled to be played
matchType
string
Code indicating the type of match: MS - Mens Singles, LS - Ladies Singles, MD/MX - Mens Doubles, LD - Ladies Doubles, XD - Mixed Doubles. The above codes can be prefixed with ‘Q’ to indicate they are part of qualifying for the competition
status
string
The current status of the match, one of: NotStarted, InProgress, Suspended, Finished
courtId
string
The identifier for the court the match is on. Note that this value is assigned by the ATP’s software - it will likely not correlate with the actual court name
courtName
string
The name of the court the match is on
courtSeq
int
Defines the ordinal position of the match on this court. First match will have a value of 1, the second 2 etc.
teamA
object
Team Status object for the first team in the match
teamB
object
Team Status object for the second team in the match
startTime
object
startTime object indicating when the match is scheduled to start
startTimeText
string
Text description of the start time. Note that the start time object contains detailed information about the start and is likely to be more useful than this field
additionalText
string
Additional information about the match
bookingStatus
structure
Indicates if this event is booked. One of: “Booked”, “Autobooked” or ”NotBooked”
competitionId
string
Identifier for the competition - this is the year and the externalId
round
string
The round this event is being played in. In case of a qualifier event the round number is prepended with a ‘Q’, like “Q3”. Otherwise it’s simply a number, e.g. “3”. The rounds work backwards, with 1 being the final, 2 being the semi-finals, 3 the quarters etc
globalCourtId
string
Unique global court ID for the court. UTR events only
venueId
string
Unique Venue court ID for the venue. UTR events only
Field Name
Type
Description
status
string
Indicates if the player detail is known for this team. Values are KnownTennisTeam or UnknownTennisTeam. For UnknownTennisTeam, no other fields will be present
team
object
A tennis team object
Field Name
Type
Description
id
string
Unique identifier for this player as defined by the ATP/UTR
firstName
string
First name of the player
lastName
string
Last name of the player
country
string
IOC (Olympic) country code for the player
Field Name
Type
Description
status
string
Indicates the type of information held for the start time.
StartsAt: The time in which the match is expected to start.
NotBefore: The time in which the match will not start before.
EstimatedStart: The time in which the match is estimated to start.
FollowsPrevious: The match will follow the previous match on the same court, therefore the time attributed with a 'Follows Previous' state is a rough estimate of the start time of that match.
NoInformation: No information available.
time
offset time
Contains either the start time for the match (generally if it’s the first match of the day on a court) or the earliest time it could start (e.g. if there is a rain delay and they know play will not start until midday) or an estimate of the start time based on the start time of the previous match
An example from the tournament events endpoint JSON response from Roland Garros 2024
https://dde-api.data.imgarena.com/tournaments/11904/events
This endpoint lists the events for a competition for which you are licensed. Please note that the list of events is incomplete and will generally only show previous events and events for today and tom
This end point will show the same information as the /tournaments/{id}/events end point, but for a competition.
The difference between competitions and tournaments is explained here.
We recommend that you request the https://dde-api.data.imgarena.com/competitions/{id}/events REST end point every minute so that you have the most up-to-date information on the events from live/upcoming competitions.
This endpoint currently takes no request parameters, we aim to add them, and once we have they will be detailed here.
An example Competition Draw from the Roland Garros 2024.
https://dde-api.data.imgarena.com/competitions/2024-0520/draws
N.B: If a request was made mid-way through the tournament, unknowns players will be returned as draws have not been released.
A map of competitionType -> Draw objects, populated with players where they are known.
The response format is the same as the one for the /tournaments/{id}/events endpoint - see here - except that the start time may not be available if we have not received that information.
Field Name
Type
Description
eventId
string
Unique identifier for this event
date
date
Date the match was played or is scheduled to be played
matchType
string
string Code indicating the type of match: MS - Mens Singles, LS - Ladies Singles, MD/MX - Mens Doubles, LD - Ladies Doubles, XD - Mixed Doubles. The above codes can be prefixed with ‘Q’ to indicate they are part of qualifying for the competition
status
string
The current status of the match, one of: NotStarted, InProgress, Suspended, Finished
courtId
string
The identifier for the court the match is on. Note that this value is assigned by the ATP’s software - it will likely not correlate with the actual court name
courtName
string
The name of the court the match is on
courtSeq
int
Defines the ordinal position of the match on this court. First match will have a value of 1, the second 2 etc.
teamA
object
Team Status object for the first team in the match
teamB
object
Team Status object for the second team in the match
startTime
object
startTime object indicating when the match is scheduled to start
startTimeText
string
Text description of the start time. Note that the start time object contains detailed information about the start and is likely to be more useful than this field
additionalText
string
Additional information about the match
bookingStatus
structure
Indicates if this event is booked. One of: “Booked”, “Autobooked” or ”NotBooked”
competitonId
string
Identifier for the competition - this is the year and the externalId
round
string
The round this event is being played in. In case of a qualifier event the round number is prepended with a ‘Q’, like “Q3”. Otherwise it’s simply a number, e.g. “3”. The rounds work backwards, with 1 being the final, 2 being the semi-finals, 3 the quarters etc
Field Name
Type
Description
status
string
Indicates if the player detail is known for this team. Values are KnownTennisTeam or UnknownTennisTeam. For UnknownTennisTeam, no other fields will be present
team
object
A tennis team object
Field Name
Type
Description
id
string
Unique identifier for this player as defined by the ATP
firstName
string
First name of the player
lastName
string
Last name of the player
country
string
IOC (Olympic) country code for the player
Field Name
Type
Description
status
string
Indicates the type of information held for the start time.
StartsAt: The time in which the match is expected to start.
NotBefore: The time in which the match will not start before.
EstimatedStart: The time in which the match is estimated to start.
FollowsPrevious: The match will follow the previous match on the same court, therefore the time attributed with a 'Follows Previous' state is a rough estimate of the start time of that match.
NoInformation: No information available.
time
offset time
Contains either the start time for the match (generally if it’s the first match of the day on a court) or the earliest time it could start (e.g. if there is a rain delay and they know play will not start until midday) or an estimate of the start time based on the start time of the previous match
This endpoint lists the results from a specific tournament, as a list of final match scores.
This endpoint lists information on results for a specific tournament, namely:
The match winner
The set scores
The time/date of match completion
As soon as a match is finished in the tournament, it will appear in this endpoint https://dde-api.data.imgarena.com/tournaments/{id}/results.
This endpoint currently takes no request parameters, we aim to add them, and once we have they will be detailed here.
An example Competition Events from the Roland Garros 2024.
https://dde-api.data.imgarena.com/competitions/2024-0520/events
A snippet of an example of the Tournaments Results end point from Roland Garros 2024.
https://dde-api.data.imgarena.com/tournaments/11904/results
: Note: A map of competitionType -> Draw objects, populated with players where they are known.
: Note: It is possible that we may not have been informed of the start time, in which case that information will not be available.
:
Field Name
Type
Description
teamA
object
Team object containing details for the first team
teamB
object
Team object containing details for the second team
winner
string
The team ID of the winner - TeamA or TeamB
matchScore
object
The final match score object
matchExternalId
string
The external match ID for the event
finishReason
string
The reason of winning - one of “Normal”, “Retirement”, “SuddenDeath”, “Default” or “Unknown”
matchId
string
IMG match ID
eventId
string
The event ID of the match
Field Name
Type
Description
status
string
Indicates if the player detail is known for this team. Values are KnownTennisTeam, UnknownTennisTeam or Bye. For UnknownTennisTeam or Bye, no other fields will be present
team
object
A tennis team object
Field Name
Type
Description
player1
object
Player object containing details for the first player in the team
player2
object
Player object containing details for the second player in the team. Only present if a doubles team
seed
int
This team's seeding for the competition
entryType
string
This team’s entry type for the competition. Possible values are: Wildcard, Qualifier, LuckyLoser, ProtectedRank, Alternate, SpecialExempt or Standard
Field Name
Type
Description
id
string
Unique identifier for this player as defined by the ATP
firstName
string
First name of the player
lastName
string
Last name of the player
country
string
IOC (Olympic) country code for the player
Field Name
Type
Description
setScores
object
The scores in the completed match sets
Field Name
Type
Description
gamesA
int
Number of games won by TeamA
gamesB
int
Number of games won by TeamB
tieBreakPointsA
int
Tie-break score for the Set if it went to a tie break for TeamA
tieBreakPointsB
int
Tie-break score for the Set if it went to a tie break for TeamB
Field Name
Type
Description
competitionId
string
Unique identifier for this competition
competitionType
string
Identifies the competition type e.g MD/MX - Mens Doubles, LS - Ladies singles. There will be a draw object for each singles competition in the tournament and each doubles competition. Therefore, for a tournament with both ATP & WTA events there may be 4 or 5 draws
drawSize
int
Number of positions in the draw
entrySize
int
Number of teams in the draw (if not equal to drawSize then some teams will be given byes)
numberOfPools
int
(Round robin tournament only) The number of pools in the round robin
matches
array[object]
Array of Match objects describing the matches that are to be played
Field Name
Type
Description
eventId
string
Unique identifier for this match within the competition - to match this with the eventID returned in the /[id]/events end point you just need to concatenate it with the competitionID
round
int
(Knockout tournament only) Which round of the draw this match is in. The rounds work backwards, with 1 being the final, 2 being the semi finals, 3 the quarters etc
stageType
string
(Round robin only) Indicates if this match is in the group stage or the knockout stage. Values are Group or Knockout
groupId
int
(Round robin only) If a group stage match then this shows the id of the group the match is in
teamA
object
A team status object describing the first team taking part (if known)
teamB
object
A team status object describing the second team taking part (if known)
estimatedDate
date
Indicates the date when the match is likely to be played
estimatedTime
timestamp
Please be advised that this is merely a placeholder until the official Order of Play has been released and will be defaulted to 10am local time
Field Name
Type
Description
status
string
Indicates if the player detail is known for this team. Values are KnownTennisTeam, UnknownTennisTeam or Bye. For UnknownTennisTeam or Bye, no other fields will be present
team
object
A tennis team object
Field Name
Type
Description
Player1
object
Player object containing details for the first player in the team
Player2
object
Player object containing details for the second player in the team. Only present if a doubles team
seed
int
This team’s seeding for the competition
entryType
string
This team’s entry type for the competition. Possible values are: Wildcard, Qualifier, LuckyLoser, ProtectedRank, Alternate, SpecialExempt or Standard
The /players endpoint contains over 60,000 players, both active and inactive - this changes infrequently. It will generally be updated once a week when new ranking information comes in, following the end of a tournament.
We recommend that you request the https://dde-api.data.imgarena.com/players REST end point once a week, for this reason, so that you have the most up-to-date information on the players in the ATP
Due to the large response message size for requests made using the "activity=inactive" and "activity=all" parameters, the responses, although successful, will not return any information. We therefore recommend that any requests made to the /players REST endpoint are no larger than "results=10000"
This endpoint lists all the players registered with the ATP & UTR
*Please note that the optional fields are dependent on data being known and available in our database.
This endpoint takes the following parameters:
Parameter
Type
Purpose
activity
string
This is an optional field. Possible values are "active" "inactive" and "all". They are not case sensitive. active returns just active players, inactive returns only the inactive players and all, returns all. If not specified, only the active players are returned. E.g. activity=all
gender
string
This is an optional field. Possible values are "male" and "female"
results
string
This is an optional field, and should be used in conjunction with the offset parameter. Possible values are numbers: "1", "2" etc, but will only return information on the first X players in the response. E.g. "activity=active&results=3" will return information for the first three active players in the response, and nothing else
offset
string
This is an optional field, and should be used in conjunction with the results parameter. Possible values are numbers: "1", "2" etc, but will only return information on players who are after X players in the response. E.g. "activity=active&offset=3" will ignore the first 3 players in the active list, and return everything from player four onwards
showRanking
boolean
By default, if no value passed or set as true, we will return ranking for players. Passing False will not return rankings.
gender
boolean
By default, feed will return both men and women. Possible values: "men" "female"
Best practice (using the results and offset parameters):
When results and offset are used together, you can specify how many players are 'ignored' and not included in the response, as well as the number of players who are included in the response. E.g. "results=10&offset=10" will bring back the first 10 players after the first 10 are ignored (Players 11 through 20)
If you would like to obtain the full list of inactive players (over 50,000 players), you can do so in increments of 5000, increasing the 'offset' value, whilst keeping 'results' the same. Examples below:
"results=5000" - this will bring back information for the first 5000 players. "results=5000&offset=5000" - this will bring back information for players 5001 through 10000. "results=5000&offset=10000" - this will bring back information for players 10001 through 15000. "results=5000&offset=15000" - this will bring back information for players 15001 through 20000. etc.
An array of player details objects.
Field Name
Type
Description
playerSummary
object
Player Object containing basic information about the player
active
boolean
indicating whether the player is active or inactive
gender
string
Possibles values are “Male” and “Female”
rankDate
string
The most recent rankdate
*Please note that the optional fields are dependent on data being known and available in our database.
Field Name
Type
Description
currentSinglesRank
int
Current singles rank
currentSinglesRankTied
boolean
True if tied for current singles rank
currentDoublesRank
int
Current doubles rank
currentDoublesRankTied
boolean
True if tied for current doubles rank
currentYTDRank
int
Current YTD rank
currentYTDRankTied
boolean
True if tied for current YTD rank
singlesRollingPoints
int
Singles rolling points. Points earned by a player in the last 52 weeks
doublesRollingPoints
int
Doubles Rolling Points. Points earned by a player in the last 52 weeks
singlesRacePoints
int
Singles Race Points. Points earned by a player in the calendar year
A snippet of the /players endpoint, with rankings from December 2024
https://dde-api.data.imgarena.com/players
i.e return first 100 results: https://dde-api.data.imgarena.com/players?results=100