Site Home / Forum / 3rd Party Projects / livescore regression
livescore regression
Posted: 09 Aug 2024 15:25
smathers
Posts: 42 Joined: 2023
My app was working fine all of last season accessing livescores of the Scottish Leagues via the following endpoint example for the Scottish Premiership:
Even after I was recently given another API Key, the above call no longer works i.e. even with the free key "3" it returns:
{"error":"Invalid ID Passed"}
I see that the following DOES appear to work:
https://www.thesportsdb.com/api/v2/json/3/livescore/4330
Can you please reinstate the original livescore endpoint operation, so that my users can get live scores again. I luckily use AWS code to handle all android phone app accesses to thesportsdb APi so have been able to disable it for now.
Cheers,
Stewart
Update 17th August 2024
"Scottish Football League Info" Android App now successfully using the v2 livescores with header based API-KEY.
Posted: 10 Aug 2024 12:48
smathers
Posts: 42 Joined: 2023
After further investigation, I have confirmed that:
Says:
"Larger API Limits (Patreon only)
Livescores V1 (Patreon only) V2 is now recommended for livescores"
Then gives a sample:
https://www.thesportsdb.com/api/v2/json/APIKEY/livescore.php?l=4399
I thus successfully used the V2 sample based calls, as above, for all of last season for the four Scottish Leagues. It was only when the new Scottish Football season opened two Saturdays ago, that I noticed that it no longer worked, causing strange behaviour with my app until I initially disabled it on AWS code, then hack got it working last weekend, with the following endpoint sample:
Sounds like my hack for the above will break this weekend unless I move the api-key to the header - correct?
Update
----------
I trialled the v2 API with the api-key in the header and confirmed it is working with the updated API-Key you gave me and not with the original which does however continue to work with v1 . I also noted a subtle change in behaviour from that of: