cancel
Showing results for 
Search instead for 
Did you mean: 

API documentation bugs

paleloser
Shkhara

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.
1 REPLY 1

Elliott
Community Manager Community Manager
Community Manager

Hi there, 

Thanks for flagging this.

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