How to use the endpoints effectively for Live Scores & Match Center in API?

As you know, our endpoints work by date, tournamentId and matchId. Date friendly endpoints which are “Match Lists” and also “Missing Players” help you to use your call limits very economically. Because they always request the data daily and get all data of tournaments at that moment. So, one shot call updates all your data once. If you want the fastest score updates for your application, you should always call “Match List All” endpoint to update the all score and status related areas in your application for live scores. And also, if you have the push mechanism for live scores in your web or mobile application you should definitely use the “Match List All”.

On the other hand, the tournament and match based endpoints run out of your limit very quickly due to working via tournamentId & matchId, when the match counts are at a high level in the prime time. At this point, creating a-sync’ed structures and consecutive updating mechanisms will update your side quickly and also economically. For example, if you are planning to create “Match Center or Match Detail Page” with “Match Summary”, “Match Lineup”, “Match Commentary” & “Match Statistics” endpoints. You should not choose to update your all components or widgets at the same time. Because “sync’ed structures” will burn up your calls rapidly. So, you should try to call the endpoints via consecutive values. You can see these values in the “Working Process” column in the table below.

HINT: For Match Center, sometimes there can be 80-120 matches at the same time. But, all matches will not start at the same time although kick-off times are the same. Some start at the exact time, some start 1-2 mins later. If you put a timestamp for matches(matchIds) in your database, you can update your data consecutive and a-sync’ed intervals according to matches’ timestamps.