Terra

Integration

API
Unified API
SDK
SDK
Authentication
Authentication
Streaming
Streaming
Blood
Blood Report API
Planned Workout
Planned Workout
AI Interface
AI Interface

User engagement

Graph API
Graph API
Scores
Health Scores
Rewards
Health Rewards

Use cases

Enterprise
Enterprise
Insurance
Insurance

Developers

Wearable Data
Wearable Data
Community
Community
Documentation
Documentation

Learn

Blog
Blog
Podcast
Podcast
Events
Events
Reports
Reports

Company

Customers
Customers
Careers
Careers
Partners
Partners
Support
Support
Become an integration
Become an integration

Cookie Preferences

Essential CookiesAlways On
Advertisement Cookies
Analytics Cookies

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.

zap

Latest

zap

Popular

API

Unified API

SDK

Phone SDK

Authentication

Widget

Streaming

Streaming

Graph API

Graph API

Sample Definitions for Development

All

SuccessfulLemming8 months ago

I'm trying to understand what the S3 bucket will look like if we utilise your solution for sourcing health data for our use cases... Ideally I need to source some indicative definitions so I can look at a small scale POC to remove our legacy integration solutions. Is it possible to provide this without me having to subscribe?

terra

Vanessaadmin8 months ago

Hi!

When you use an S3 bucket as a data destination with Terra, the structure is as follows:

  • Data is organized by event type (for example, activity, sleep, authentication) as the parent folder.
  • For versioned data events, the objects will be placed under a folder named for the API version (such as 2022-03-16).
  • Each event will be saved with a unique name:

For data events: the file name is a combination of the user ID and the start time of the period the event refers to. For other event types: the file name is a combination of the user ID and the timestamp when the event was generated.

This means your S3 bucket will have folders for each event type, with files named according to these conventions. The files themselves contain the payloads (such as health, activity, or authentication data) in standard formats.

You do not need to subscribe just to see the structure! :) This information is available in the documentation and you can design your POC folder structure accordingly.

See here for the S3 Cloud storage data structure: https://docs.tryterra.co/health-and-fitness-api/integration-setup/setting-up-data-destinations/cloud-storage-s3-gcp

Hope this helps!

SuccessfulLemming8 months ago

Okay thats fine but I am trying to understand what the JSON will look like for each event etc... I couldn't spot the definition so to speak in the documentation can you give me a pointer? My ask is because I want to mock some data before paying for the service so I can have some of the downstream platform activities started etc...

My hope is to be able to decouple the development but I can't see any sample data available which is a bit disapointing.