Developer Checklist

This checklist provides an overview of the steps recommended to launch your application with Google Health API integration.

1. Before you begin

Review developer documentation: Understand data types, scopes, and API endpoints to determine which are needed for your integration.

Review Google Health API Policies: Make sure your use case is compliant with Google Health API Developer Terms and Conditions and Google Health API Developer and User Data Policy.

Plan your user experience: If you are migrating users from Fitbit Web API, review best practices in the Migration guide for handling user re-authentication.

2. Set up your integration

Set up Google Cloud: Follow Set up Google Cloud and OAuth to create a Google Cloud project, enable Google Health API, and configure OAuth 2.0 credentials.

Configure OAuth consent screen: In Google Cloud console, configure the OAuth consent screen with your app information, branding, and links to your app's privacy policy and terms of service.

Add scopes: In Google Cloud console, add the scopes required for the data types your app needs to access.

3. Develop and test

Make your first API call: If you are new to Google Health API, follow the Codelab to make your first API call in minutes.

Migrate from Fitbit Web API: If you are migrating from Fitbit Web API, review the Migration Guide and use the Parity Tool to compare APIs.

Implement OAuth 2.0: Implement OAuth 2.0 authorization to obtain user consent and API tokens. Use Client Libraries to simplify your implementation.

Add test users: While your app is in "Testing" mode in Google Cloud, add test users to test your integration with allowlisted accounts.

Fetch data: Use appropriate data type endpoints to fetch user data.

Handle errors: Review the Troubleshooting Guide for common errors and how to handle them.

4. Prepare for launch

OAuth verification: If your app needs to support more than 100 users, or you are ready to launch publicly, submit your app for OAuth verification. This process can take several days and includes a third-party security review and verification of your app's privacy policy and terms of service.

Fitbit Web API migration: If migrating, ensure your re-authentication flow for migrating users is smooth, following recommendations in Migration Guide.

5. Launch and maintain

Publish your app: Once OAuth verification is complete, publish your app to "In production" in Google Cloud console to remove the 100-user limit.

Monitor: Monitor API usage and error rates in Google Cloud console.

Stay informed: Keep up with Release Notes for API updates and deprecations.