How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Google Fit REST Users API

The Users API from Google Fit REST — 6 operation(s) for users.

Google Fit REST Users API is published by Google Fit REST on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

This API exposes 9 operations across 6 paths, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://www.googleapis.com/fitness/v1.

9 operations 6 paths 6 schemas 1 DELETE4 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://www.googleapis.com/fitness/v1
Authentication
OAuth 2.0
Contact
Resource Areas
1

Authentication & Security 1

Google Fit REST Users API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 6 scopes. By default, every request must be authenticated.

Paths & Operations 9

Across 6 paths, the API surfaces 9 operations — 1 DELETE, 4 GET, 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Users 9
GET
/users/{userId}/dataSources
List data sources
listDataSources 1 param → 200
POST
/users/{userId}/dataSources
Create a data source
createDataSource 1 param body → 200
GET
/users/{userId}/dataSources/{dataSourceId}
Get a data source
getDataSource 2 params → 200
GET
/users/{userId}/dataSources/{dataSourceId}/datasets/{datasetId}
Get a dataset
getDataset 5 params → 200
PATCH
/users/{userId}/dataSources/{dataSourceId}/datasets/{datasetId}
Add data points to a dataset
patchDataset 3 params body → 200
POST
/users/{userId}/dataset:aggregate
Aggregate data
aggregateDataset 1 param body → 200
GET
/users/{userId}/sessions
List sessions
listSessions 4 params → 200
PUT
/users/{userId}/sessions/{sessionId}
Update or insert a session
updateSession 2 params body → 200
DELETE
/users/{userId}/sessions/{sessionId}
Delete a session
deleteSession 2 params → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Session (9 properties), DataSource (7 properties), Dataset (5 properties), DataPoint (4 properties). Each schema is shown below with its type and property counts.

ListSessionsResponse
object
2 properties
DataPoint
object
4 properties
DataSource
object
7 properties
Dataset
object
5 properties
ListDataSourcesResponse
object
1 property
Session
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

google-fitness-users-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Google Fit REST Users API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.