- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Examples
- Try it!
Exports exercise data in TCX format.
IMPORTANT: HTTP clients must append ?alt=media to the request URL to download the raw TCX file.
Example: https://health.googleapis.com/v4/users/me/dataTypes/exercise/dataPoints/EXERCISE_ID:exportExerciseTcx?alt=media
Without alt=media, the server returns a JSON response (ExportExerciseTcxResponse) which is intended primarily for gRPC clients.
Note: While the Authorization section below states that any one of the listed scopes is accepted, this specific method requires the user to provide both one of the activity_and_fitness scopes (normal or readonly) AND one of the location scopes (normal or readonly) in their access token to succeed.
HTTP request
GET https://health.googleapis.com/v4/{name=users/*/dataTypes/*/dataPoints/*}:exportExerciseTcx
The URL uses gRPC Transcoding syntax. To know more about valid error responses that can be thrown by this HTTP request, please refer to the service error catalog
Path parameters
| Parameters | |
|---|---|
name |
Required. The resource name of the exercise data point to export. Format: The |
Query parameters
| Parameters | |
|---|---|
partialData |
Optional. Indicates whether to include the TCX data points when the GPS data is not available. If not specified, defaults to |
Request body
The request body must be empty.
Response body
Represents a Response for exporting exercise data in TCX format.
If successful, the response body contains data with the following structure:
| JSON representation |
|---|
{ "tcxData": string } |
| Fields | |
|---|---|
tcxData |
Contains the exported TCX data. This field is intended for gRPC clients, as media download integration is not supported for gRPC. HTTP clients should instead use the |
Authorization scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/googlehealth.activity_and_fitness.readonlyhttps://www.googleapis.com/auth/googlehealth.location.readonly
For more information, see the OAuth 2.0 Overview.