All data is sent to your webhook in JSON format in the form of 5 different types of payloads: Activity. Depending on your needs, you may select a subset of the aforementioned, and request less data from your users.
Examples of data payloads can be found here. If you would only like to receive specific fields out of the ones available, you may also select only the ones relevant to your needs and omit the rest. The following is an example of the data payload you may expect from an activity coming from Terra.
Whenever data become available from a Zwift device, they will be streamed to you, via our webhooks. When setting up your Terra account, you will be prompted to provide a callback URL, to which Terra may send PUSH data using POST requests.
Your Zwift integration with Terra supports instant delivery of data without needing to periodically request it yourself. Zwift notifies Terra whenever new data is available, following which we POST the normalized data to your webhook.
You may also use HTTP requests with your Zwift integration in case you wish to request historical data or data over extended periods of time.
Most HTTP endpoints can take additional parameters start_date and end_date which allow you to request data over a specific period for the given user.
