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

Google fit no datasource payloads

All

DreadfulGecko31 months ago

When I authenticate a new user with the /authenticateUser endpoint, we receive an auth_success payload followed by google_no_datasource. How can I handle this?

terra

Danieladmin31 months ago

The google_no_data_source payload is sent when a user connects a Google account which has no devices or sources of health data attached to it. This usually means the user connected the wrong account or does not have the Google Fit app installed and connected with their gmail/google account.

When you receive this payload, deauthenticate the user using the /deauthenticateUser endpoint, then ask the user to connect a valid account in your application front-end. You can use the reference_id sent in the payload to identify which user provided the invalid account.

DreadfulGecko31 months ago

Thank you for your answer, we will try that