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](https://developers.google.com/health/data-types.md.txt), [scopes](https://developers.google.com/health/scopes.md.txt), and API [endpoints](https://developers.google.com/health/endpoints.md.txt) 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](https://developers.google.com/health/policies/health-api-developer-terms-and-conditions.md.txt) and [Google Health API Developer and User Data Policy](https://developers.google.com/health/policies/health-api-developer-user-data-policy.md.txt). **Plan your user experience** : If you are migrating users from Fitbit Web API, review best practices in the [Migration guide](https://developers.google.com/health/migration.md.txt) for handling user re-authentication.

## 2. Set up your integration

**Set up Google Cloud** : Follow [Set up Google Cloud and
OAuth](https://developers.google.com/health/setup) to create a Google Cloud project, enable Google Health API, and configure OAuth 2.0 credentials. Use [separate projects for staging
and production](https://developers.google.com/health/setup#separate-environments) so testing does not affect your live app. **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](https://developers.google.com/health/scopes.md.txt) required for the data types your app needs to access. Review [scope implementation](https://developers.google.com/health/scopes.md.txt#implementation), such as requesting only needed scopes, only configuring write access when sending data, and handling partial consent gracefully.

## 3. Develop and test

**Make your first API call** : If you are new to Google Health API, follow the [Codelab](https://developers.google.com/health/codelabs/make-your-first-api-call) 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](https://developers.google.com/health/migration.md.txt) and use the [Parity
Tool](https://developers.google.com/health/migration/parity-tool) to compare APIs. **Implement OAuth 2.0** : Implement OAuth 2.0 authorization to obtain user consent and API tokens. Use [Client Libraries](https://developers.google.com/health/libraries.md.txt) to simplify your implementation. **Add test users** : While your app is in "Testing" mode in Google Cloud, [add test users](https://developers.google.com/health/setup.md.txt#test-users) to test your integration with accounts on the allowlist. **Fetch data** : Use the appropriate [data type endpoints](https://developers.google.com/health/data-types.md.txt) to fetch user data. Follow best practices for [retrieving historical
data](https://developers.google.com/health/rate-limits) by separating it from onboarding, as rate limits are fixed across all data periods. **Handle errors** : Review the [Troubleshooting Guide](https://developers.google.com/health/troubleshooting.md.txt) for common errors and how to handle them. **Use webhooks for subscriptions** : Use the subscription API to receive notifications rather than polling. Put incoming notifications into a queue and process them separately. See [webhooks best
practices](https://developers.google.com/health/webhooks#best-practices).

## 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](https://support.google.com/cloud/answer/13463073). 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](https://developers.google.com/health/migration). **OAuth token grant rate limits** : Google Cloud enforces a rate limit on OAuth token grants to control how quickly your app can onboard or re-authenticate users. If you expect to exceed 10,000 user sign-ups or re-authentications within a 24-hour sliding window, request a higher quota in advance. For more information, see [OAuth application rate limits](https://support.google.com/cloud/answer/9028764).

## 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, error rates, and OAuth token grant usage in Google Cloud console. **Stay informed** : Keep up with [Release Notes](https://developers.google.com/health/release-notes.md.txt) for API updates and deprecations.