Skip to main content
Solved

API documentation bugs


paleloser
Forum|alt.badge.img+12

Been using the API for a while now, and trying to mock it using the examples provided in the specification ran into some failures:

  • At /athlete/activities the returned upload_id through SummaryActivity has type long. Yet, the response example uses a 987654321234567891234 value, which is higher than the max int64.
  • There are some fields such as resource_state, max_heartrate or location_city that don't comply with the SummaryActivity definition.
  • The components aren't sorted alphabetically, which makes navigating through the documentation site a bit difficult.

Best answer by Elliott11

Hi there, 

Thanks for flagging this.

Our team is investigating and making sure our documentation is up to date. 

View original
Did this topic help you find an answer to your question?

Forum|alt.badge.img+20
  • Community Manager
  • April 3, 2023

Hi there, 

Thanks for flagging this.

Our team is investigating and making sure our documentation is up to date. 


Forum|alt.badge.img+1
  • Hub Starter
  • June 2, 2024

Chiming back here - I came across this issue on my own and saw this post. The documentation Sample API Response for List Athlete Activities (getLoggedInAthleteActivities) includes a sample "id" : 154504250376823, however that number is higher than the max int64 and causes Xcode to crash.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept, you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings