Start Receiving Data From Flo In 5 Minutes
Flo
Enable Flo through your Terra dashboard
Select a Wearable
Flo
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 Flo on your app or website
How the Flo API integration works
- Data delivery
- Terra polls Flo
- Expected latency
- Up to 5–10 minutes after the provider syncs
- Data types
- Menstruation
- Credentials
- No provider credentials required
Two ways to receive Flo data
When data is available from a Flo 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.
Flo does not notify Terra when data changes, so Terra polls it every 5–10 minutes for each connected user and POSTs the normalized payload to your webhook.
Flo's Menstruation
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
Menstruation Payload (JSON)
{
menstruation_data: { ... }
metadata: { ... }
}
Data can also be sent as a FIT File or with the FHIR Format.
Send Flo 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 Blob
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.