Match Odds
Match Odds
Request structure
Here is what you need to successfully make a Match Odds Query
v5.core.graphql.matchodds.oddsandresultprediction
In case, if the probability of winning among the teams is required to be known, the query explaining the possible percentage of teams winning in the match, can look like in the below query request.
query {
match(key: "auseng_2021_test_02") {
odds {
match {
meta {
key
status
format
startAt
}
teams {
key
name
code
}
resultPrediction {
automatic {
percentage {
team {
key
name
code
}
value
}
}
}
}
}
}
}HTTP Status
Possible status code you may receive in response to your request.
Cache
A cache object accompanies every API response. It comes with a set of recommended values to help you properly cache the data and handle the cache internally.
When you try to cache the responses on say MemCached, Redis or any other cache server, you will usually require a Key and an expire time.
Our recommendations on what Key or ID you should use while you cache a response of this API.
Our recommendations on how long you can cache a particular response.
An interesting thing to note here is that the recommended expire time is not going to be the same under all situations. Our intelligent caching mechanism dynamically decides the best expire time analysing various parameters.
The cache object also provides you with a max_age and the ETag values, which lets you implement the ETag HTTP caching mechanism. To implement HTTP Caching with this API, refer here.
Our recommended period of time up to which you can consider the data to be fresh. It gives you a heads up on when you should be checking for updates in the data.
Etag is an identifier for a specific version of a response. To know more, refer here.
The time period specified in max_age will be lesser than that in the expires object. To sum it up, the cache.expires object tells you how long you can cache the data while the cache.max_age object tells you when you should check for updates.
