08-15-2024 12:36 AM
I see on strava status there are problems. We are facing problems submitting activities via API. Normally this is very stable for years for us so we are pretty sure strava API has errors. Anyone else seeing this?
Solved! Go to Solution.
08-15-2024 06:42 AM
@jaimegil please don't apologize for mentioning me directly!
There were residual issues from the incident yesterday but traffic should be restored for all apps. Sincerest apologies to anyone who experienced this issue and for our API status page not reflecting the behavior some of you were experiencing.
If anyone is still experiencing issues please let me know.
08-15-2024 06:44 AM
Yes
08-15-2024 06:44 AM
I see that it started working again for us.
08-15-2024 06:05 AM - edited 08-15-2024 06:05 AM
We have the same problem, is there a way to report this to Strava? - since according to the status page https://status.strava.com/ the API is working fine 😕
08-15-2024 06:09 AM
i opend a ticket via email at developer support and wait now for the aswer
08-15-2024 06:31 AM
I think the API is working, but not the authorization (token and refresh token requests), although I didn't test it. I also opened a ticket a few hours ago, but I don't expect any reply. I think there is a serious issue because this is already taking more than 12 hours.
08-16-2024 12:43 PM
Having the same issue with the authorization code exchange interface. i.e.
08-15-2024 06:44 AM
Come on, an API without access is for me a not working API and has not earned a green tick on the status dashboard 😄
Without a key you couldn't use the care. The care is working yes, but useless 😄
08-15-2024 05:59 AM
Yes, same problem here.
ERROR: The request could not be satisfied
403 ERROR
08-15-2024 05:42 AM
I am also seeing the same problem. If I had to guess, its most likely a AWS security rule that has been applied that blocks requests from certain types of servers (like ones in data centers). I manually updated the access token on my server to see if is just a problem with refreshing it, but it still fails to fetch activities returning a status code of 403.
08-15-2024 04:33 AM
Came here for the same reason. My server is getting a 403 (Forbidden) response when trying to do the token exchange; though it works fine for me locally. I was afraid my server got blacklisted, but it sounds like there's a bigger problem going on.
Welcome to the Community - here is your guide to help you get started!