Start Receiving Data From PÜL In 5 Minutes
PÜL
Enable PÜL through your Terra dashboard
Select a Wearable
PÜL
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 PÜL on your app or website
How the PÜL API integration works
- Data delivery
- PÜL pushes to Terra on change
- Expected latency
- Seconds after the provider syncs
- Data types
- Nutrition
- Credentials
- Terra manages the PÜL API credentials, so there is nothing to register
Two ways to receive PÜL data
When data is available from a PÜL device, Terra sends it straight to your webhook. During your Terra account setup you'll be prompted for a callback URL, and that is where Terra POSTs each payload.
PÜL notifies Terra as soon as new data is available, and we POST the normalized payload straight to your webhook. No polling needed.
PÜL's Nutrition
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
Nutrition Payload (JSON)
{
drink_samples: [ ... ]
metadata: { ... }
summary: { ... }
}
Data can also be sent as a FIT File or with the FHIR Format.
Send PÜL data to your backend
Terra forwards every normalized payload to the destination you already use.
Webhook
Firestore
SQL
Mongo DB
Google Cloud Storage Bucket
AWS S3 Bucket
AWS Simple Queue Service
Kafka
Supabase
Azure BlobPeople Often Ask Us...
Can't Find Your Question?
PÜL API alternatives
These integrations also offer Nutrition data.
Cookie Preferences
Crunch Time: Embrace the Cookie Monster Within!
We use cookies to enhance your browsing experience and analyse our traffic. By clicking “Accept All”, you consent to our use of cookies according to our Cookie Policy. You can change your mind any time by visiting out cookie policy.