Connect with Zepp

Terra's Zepp API integration will allow your app to collect data from the Zepp platform, and gain insights into the number of calories burned for a user, the steps they generate in a day, and more. Through the Zepp API integration, your app can use these data keep users active, and pull detailed workout metrics for analysis.

Start Receiving Data From Zepp In 5 Minutes

Zepp

Enable Zepp through your Terra dashboard

Select a Wearable

Zepp

Connect

Connect users to your app

0. "active_durations_data":{...}
1. "calories_data": {...}
2. "device_data": {...}
3. "distance_data": {...}
4. "heart_rate_data": {...}
5. "movement_data": {...}
6. "position_data": {...}

Start receiving data from Zepp on your app or website

You Can Receive...

Recent Data with Webhooks

Historical Data with HTTP Requests

When data is available from a Zepp device, it will be streamed to you via our webhooks. During your Terra account setup, you'll be prompted to provide a callback URL, allowing Terra to PUSH data using POST requests.

You may also use HTTP requests with your Zepp integration in case you wish to request historical data or data over extended periods of time.

Our Zepp integration with Terra offers instant data delivery, eliminating the need for periodic requests. Zepp notifies Terra whenever new data is available, and we then POST the normalized data to your webhook.

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.

Zepp's
Activity

Payload Preview

Zepp's
Daily

Payload Preview

Zepp's
Sleep

Payload Preview

Terra API preserves the raw data from the wearable, it just standardizes the units and the json format. It doesn’t augment or change the raw data in any way.

Data is organized into one of 6 data types.

Learn More

Zepp's Avaliable Data Types

Activity Payload (JSON)

{

active_durations_data: { ... }

calories_data: { ... }

metadata: { ... }

heart_rate_data: { ... }

movement_data: { ... }

position_data: { ... }

distance_data: { ... }

device_data: { ... }

}