Google Fitness

Connector for the google-fitness API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://fitness.googleapis.com/fitness/v1/users
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• fitness_users_datasources_list — GET /{userId}/dataSources — Lists all data sources that are visible to the developer, using the OAuth scopes
• fitness_users_datasources_get — GET /{userId}/dataSources/{dataSourceId} — Returns the specified data source.
• fitness_users_datasources_datapointchanges_list — GET /{userId}/dataSources/{dataSourceId}/dataPointChanges — Queries for user's data point changes for a particular data source.
• fitness_users_datasources_datasets_get — GET /{userId}/dataSources/{dataSourceId}/datasets/{datasetId} — Returns a dataset containing all data points whose start and end times overlap w
• fitness_users_sessions_list — GET /{userId}/sessions — Lists sessions previously created.
• fitness_users_datasources_create — POST /{userId}/dataSources — Creates a new data source that is unique across all data sources belonging to th

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: fitness_users_datasources_list
# (attach an 'oauth' credential to the task — no inline secrets)