Crunch Time: Embrace the Cookie Monster Within!

We use cookies to enhance your browsing experience and analyse our traffic. Nothing beyond essential cookies runs until you choose. You can change your mind any time in our Cookie Policy.

  • Unified API
  • Mobile SDK
  • Connection Widget
  • Streaming
  • Lab Reports API
  • Graph API
  • Health Scores
  • Health Rewards
  • Workouts & Routes
  • Predictions
  • Lab Testing
  • DNA Testing
  • AI Interface
  • Enterprise
  • Insurance
  • Integrations
  • Research
  • Podcast
  • Blog
  • Reports
  • Events
  • Documentation
  • Community
  • Example apps
  • Wearable Data
  • About
  • Customers
  • Partners
  • Startup Accelerator
  • Careers
  • Support
  • Pricing
Terra
Pricing
Become an integrationGet started
zap

Latest

zap

Popular

API

Unified API

SDK

Phone SDK

Authentication

Widget

Streaming

Streaming

Graph API

Graph API

in supabase files are not storing as mentioned in document

All

ChristianDolphin19 months ago

In subapase files are not stored with user-Id-starttime.json format.

It is taking payload_id.json.

Also, all request data is not saved in terra_data_payloads.

Can someone tell me how it works and why it is not as per documentation?

terra

Elliottadmin17 months ago

Hey,

Apologies for the confusions here! This was an old structure that we went with, however with feedback we realised this was not the best way to utilise Supabase's capabilities.

Hence, now all data (daily, sleep, activity, etc.) payloads are stored in terra_data_payloads with a payload_id.json format. This payload_id is inserted into the database table terra_data_payloads. User auth's are directly written into the terra_users table allowing you to easily query and check what users are connected.

Hope this clears it up!