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

Google fit no datasource payloads

All

DreadfulGecko25 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

Danieladmin25 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.

DreadfulGecko25 months ago

Thank you for your answer, we will try that