Create TeamAdd Your APIDocs
Log In
Sign Up
Rapid account: API-SPORTS

API-SPORTS / api-sports

Sports API supplier. Football, Basketball, Baseball, Handball, Hockey, NBA, NFL, Formula-1, Rugby, Volleyball

    Discussions

    4332
    Title
    		Created at (Click to sort ascending)
    A
    1
    		 Hi, Unfortunately we cannot act on our side on the Rapidapi proxy, the best would be to contact them at support@rapidapi.com. Regarding your errors, they may be linked to the latency of Rapidapi's proxy, which don't respond quickly enough to cut the connection (you can normally change this timeout on your side too). Note that there is a per-minute ratelimit (also managed by Rapidapi) that slows you down and blocks your requests when you exceed the per-minute limit. Best Tue 4:17 14/5/24
    A
    2
    		 Hi, On our side, latencies are normal on all our services. Average response times are between 200ms and 300ms. Nothing has changed on our side either concerning servers or latencies. Some time ago we had a Rapidapi user who had a similar problem. He was based in Europe (like our servers) but Rapidapi's proxies made him pass through the United States, which greatly increased latency on his side. It would be a good idea for you to check this out. All you have to do is look at the history of your requests on the Rapidapi dashboard. In the history of each request you'll find the "headers" section, which tells you which Rapidapi proxy the request went through. For example : { "access-control-allow-credentials": "true", "access-control-allow-headers": "x-rapidapi-key, x-apisports-key, x-rapidapi-host", "access-control-allow-methods": "GET, OPTIONS", "access-control-allow-origin": "*", "content-length": "8456", "content-type": "application/json", "date": "Tue, 14 May 2024 07:28:10 GMT", "server": "RapidAPI-1.2.8", "vary": "accept-encoding", "x-rapidapi-region": "AWS - eu-central-1", "x-rapidapi-version": "1.2.8", "x-request-id": "cf7fa9a7-5c60-491c-a59a-bbb0a2e9fd53" } My request went through proxies in Europe "AWS - eu-central-1" Regarding the error you reported, it looks like a connection error (according to the message) which could also be linked to what I've just described, but which would be on the Rapidapi side. What you can do is also try calling without going through Rapidapi to see the difference (without their proxy the response will be much faster). You can do this on our dashboard with a free plan here : https://dashboard.api-football.com/ Best Tue 7:32 14/5/24
    A
    1
    		 Hi, There was a disruption at our server provider today and we had to migrate the APis to another one. This may be due to that. Everything has now been resolved, so I invite you to try again to see if everything is OK on your side. Best Mon 3:55 13/5/24
    A
    2
    		 Hi, I have forwarded this to the tech team for check, but could be a cache issue. Best Mon 3:54 13/5/24
    A
    1
    		 Hi, Thanks for pointing this, fixture id : 1200150 Best Mon 12:14 13/5/24
    A
    1
    		 Hi, In Custom plan it's 1200 requests per minute. You have a tutorial about ratelimit here : https://www.api-football.com/news/post/how-ratelimit-works Best Thu 6:49 9/5/24