Page Summary
-
This API reference organizes information by resource type, with each type having data representations and methods.
-
The API covers resource types including Users.dataSources, Users.dataSources.dataPointChanges, Users.dataSources.datasets, Users.dataset, and Users.sessions.
-
You can perform operations like creating, deleting, getting, listing, and updating data sources.
-
The API allows for querying data point changes for a specific data source.
-
Datasets within data sources can be deleted, retrieved, or patched (data points added).
-
Data can be aggregated across multiple data types and sources into buckets.
-
Sessions can be deleted, listed, updated, or inserted.
This API reference is organized by resource type. Each resource type has one or more data representations and one or more methods.
Resource types
- Users.dataSources
- Users.dataSources.dataPointChanges
- Users.dataSources.datasets
- Users.dataset
- Users.sessions
Users.dataSources
For Users.dataSources Resource details, see the resource representation page.
POST / userId
/dataSources
A data source is a unique source of sensor data. Data sources can expose raw data coming from hardware sensors on local or companion devices. They can also expose derived data, created by transforming or merging other data sources. Multiple data sources can exist for the same data type. Every data point in every dataset inserted into or read from the Fitness API has an associated data source.
Each data source produces a unique stream of dataset updates, with a unique data source identifier. Not all changes to data source affect the data stream ID, so that data collected by updated versions of the same application/device can still be considered to belong to the same data source.
Data sources are identified using a string generated by the server, based on the contents of the source being created. The
dataStreamId
field should not be set when invoking this method. It
will be automatically generated by the server with the correct format. If
a dataStreamId
is set, it must match the format that the
server would generate. This format is a combination of some fields from the
data source, and has a specific order. If it doesn't match, the request
will fail with an error.Specifying a DataType which is not a known type (beginning with "com.google.") will create a DataSource with a custom data type . Custom data types are only readable by the application that created them. Custom data types are deprecated; use standard data types instead.
In addition to the data source fields included in the data source ID, the developer project number that is authenticated when creating the data source is included. This developer project number is obfuscated when read by any other developer reading public data types.
DELETE / userId
/dataSources/ dataSourceId
GET / userId
/dataSources
PUT / userId
/dataSources/ dataSourceId
dataStreamId
, dataType
, type
, dataStreamName
, and device
properties with the exception of version
,
cannot be modified.Data sources are identified by their
dataStreamId
.Users.dataSources.dataPointChanges
For Users.dataSources.dataPointChanges Resource details, see the resource representation page.
GET / userId
/dataSources/ dataSourceId
/dataPointChanges
Users.dataSources.datasets
For Users.dataSources.datasets Resource details, see the resource representation page.
DELETE / userId
/dataSources/ dataSourceId
/datasets/ datasetId
com.google.activity.segment
), and a data point straddles
either end point of the dataset, only the overlapping portion of the data
point will be deleted.GET / userId
/dataSources/ dataSourceId
/datasets/ datasetId
PATCH / userId
/dataSources/ dataSourceId
/datasets/ datasetId
This method does not use patch semantics: the data points provided are merely inserted, with no existing data replaced.
Users.dataset
For Users.dataset Resource details, see the resource representation page.
POST / userId
/dataset:aggregate
Users.sessions
For Users.sessions Resource details, see the resource representation page.


