Lists sessions previously created in Google Fitness
A documented Google Fitness operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Lists sessions previously created.
- GETReads data · users
fitness.googleapis.com/{userId}/sessions
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Google Fitness operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Google Fitness operations
- Creates a new data sourcePOST · changes data
- Aggregates data of a certain typePOST · changes data
- Deletes a session specified by the given session IDDELETE · changes data
- Updates or insert a given sessionPUT · changes data
- Deletes the specified data sourceDELETE · changes data
- Updates the specified data sourcePUT · changes data
- Adds data points to a datasetPATCH · changes data
- Performs an inclusive delete of all data points whose startDELETE · changes data
Questions
- Can HumDay lists sessions previously created in Google Fitness?
- Yes. This operation is published in Google Fitness's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Google Fitness account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google Fitness.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Fitness account.
Where this came from
Read from a published API description for Google Fitness at fitness.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.