--- title: "Google Health: Getting credentials from Google Console" canonical: "https://help.validic.com/space/VCS/5581111299/Google%20Health%3A%20Getting%20credentials%20from%20Google%20Console" format: markdown --- > Macro (children) > Macro (anchor) **Contents:** > Macro (toc) --- In order to have credentials for Validic to enable Google Health, the client must go through the steps in the Google Cloud Console. The instructions below aim to make this process clear and easy for Validic clients to accomplish. If you encounter any questions or concerns while going through the process, please [open a ticket with Validic technical support](https://help.validic.com/space/VCS/1725693964/Opening+a+Validic+Support+Portal+case) so we can assist with this process. > ℹ️ ### Important Note: > ℹ️ > ℹ️ If your organization already has a Google Cloud Console project in Production mode used for other Google services (Google Fit, Google Maps, YouTube, or an Android application), do not add Google Health credentials to that project. > ℹ️ > ℹ️ Adding the Google Health API and its scopes to an existing Production-mode app can affect that app's OAuth verification status and could trigger a CASA security assessment for your existing production project. The recommended path is to create a new, separate Google Cloud project dedicated to Google Health. This isolates the Google Health credential lifecycle from your existing production infrastructure and lets you test in Testing mode without any impact on your current users. If you have already added the Google Health API to an existing Production-mode project and need to remove it before creating a separate project: 1. Go to APIs and Services, then Enabled APIs and Services. Locate "Google Health API" in the table, click it, and click Disable API. 2. Go to APIs and Services, then OAuth consent screen, then Data Access. Remove all Google Health scopes. 3. Check the Verification Center. If it shows that verification is not required, the removal was completed before OAuth verification or CASA was triggered, and you can proceed with creating a new, dedicated project. If the Verification Center shows verification is required after completing the steps above, contact Validic support before proceeding. --- ### Access the Google Cloud Console 1. Go to Google Cloud Platform (aka Google Cloud Console): [https://console.cloud.google.com/welcome](https://console.cloud.google.com/welcome) 1. If you are not signed into the Google Cloud Console, you will receive this auth page: If you use a Google Workspace for your company’s email addresses, then you can use that to access. If you don’t use a Google Workspace, then Google does give instructions for how to create Google Auth with an existing non-Gmail email address: [https://support.google.com/accounts/answer/27441?hl=en&sjid=10117345795956719693-NA#existingemail](https://support.google.com/accounts/answer/27441?hl=en&sjid=10117345795956719693-NA#existingemail) 2. Log in with Google Auth to access the Google Cloud Console 1. If you first log in to Google Cloud Console, you will have to agree to the Terms of Service Click in the Terms of Service box, select the right country for your organization, and then click Agree and Continue [[ Back to top ]](#top) --- ### Create a project, or pick a project if you’re going to use an existing one 1. Now that you are logged into Google Cloud Console click the Select a project button in the top left of the screen: 2. From the module window that opens, you can select an existing project or create a new project. 1. If creating a new project, then see the New Project option in the top right of the module window. Click that. 2. You will be greeted by this page. Give your project a name that you will recognize later. This name is not shown to users anywhere. After creating the naming convention in the Project name section, press the Create button. 1. Parent Resource isn’t required if you are only creating this to get Google Health credentials. If you have existing Google projects that are related to the application, the Validic Google Health integration will be used, and then consult people within your organization familiar with your other Google projects to determine if a Parent resource is needed. 3. You will be taken back to the landing page. Click the Select a Project button in the top left and select the project you created to ensure it shows in place of the Select a Project button. 3. As you move through further steps, make sure you stay in the project you created or the existing project you selected. If you see Select a Project in the top left beside Google Cloud, then click it and select the appropriate project. [[ Back to top ]](#top) --- ### Enable Google Health API 1. Once on the landing page, you should see the naming convention of your project in the location where the “ Select a project " button was displayed in step 1 of the previous section. You will also see the randomized project name Google gave your project in the URL. Verify that you have selected the correct project before moving to the next step. 2. There is a search bar at the top middle of the page. Type “Google Health API” and then click on it when it shows 3. After clicking on the Google Health API, click the Enable button 4. You will resolve on the page below. Click the Create credentials button on the left side of the screen 5. Credential Type: 1. Verify that the API selected is Google Health API and that you have selected User Data. After doing that, click the Next button. **Don’t click the Done button yet. ** ![image-20260520-175717.png](media://89d9dab2-6940-4216-8da3-ffb3cd7e8695) 6. OAuth Consent Screen: 1. App Name: Make this exactly what you want displayed to end users in the Google Health OAuth portion of the Google Health flow with the Validic Marketplace. 2. User support email: You will only be able to select an email address from your Google Workspace or your email if your organization doesn’t use Google Workspace 1. This won’t actually appear on the Oauth screen, but you have to enter an email 3. Logo: Upload your company or app logo 4. Developer Contact Info: Add a developer contact email address. 5. Click Save and Continue after entering the information 7. Scopes 1. These are noted as optional. Validic suggests that you add them now and only select the scopes you currently plan on using to ingest data from Validic. You can identify what metrics are available per endpoint on [this page](https://help.validic.com/space/VCS/1681129566/Standard+Metrics+Used+per+App) by going to the Google Health entry. 1. `settings.readonly` (required) - For user local UTC offset 2. `activity_and_fitness.readonly` (optional) - Validic Summary and Workout endpoints 3. `health_metrics_and_measurements.readonly`(optional) - Validic Measurement endpoint 4. `sleep.readonly`(optional) - Validic Sleep endpoint 5. `nutrition.readonly`(optional) - Validic Nutrition endpoint - No scheduled job for this endpoint. This requires [webhook configuration ](https://help.validic.com/space/VCS/5754421279/Google+Health:+Enable+webhooks+for+near+real+time+data+delivery)to receive data from this endpoint. - This endpoint was added in late July 2026. For those that have created their GCP project with the other endpoints and worry about adding this causing a retriggering of CASA if they have completed 2. Click the "Add or Remove Scopes” button 3. Expand the rows on the page to 100, then copy the scopes above you want to use and use Command + F to use browser search to find the scope you want to enable. Check the ones you want to enable. 4. After selecting the scopes you want, make sure to click the Update button at the bottom of the module window before navigating away. 5. After clicking the update button, you will see your selected scopes displayed as below. 1. Please take a screenshot of this page. Validic support will need it to configure your Google Health integration when you deliver your credentials. 2. If you have all the scopes you need and have a screenshot of this page, then click Save and Continue 8. OAuth Client ID 1. Select Web Application from the drop-down 2. Name: Enter an internal name for identifying the integration 3. Do nothing with Authorized JavaScript origins 4. For Authorized redirect URIs, click the Add URI button and put in this URL: [https://syncmydevice.com/auth/google_health/callback](https://syncmydevice.com/auth/google_health/callback) 5. Click Create after filling that all out 9. Your Credentials 1. Click the Download button before clicking Done. The downloaded file, along with the screenshot of your scopes as they appear in Google Cloud Console, will be what Validic support needs to set up your Google Health integration. [[ Back to top ]](#top) --- ### Add Testers 1. Your project is automatically created in the Google Cloud Platform in “[Testing Status](https://support.google.com/cloud/answer/15549945#publishing-status-testing&zippy=%2Ctesting)”. While publishing status is set to "Testing", **only test users are able to access your app**. Allowed user cap before app verification is 100, and is counted over the entire lifetime of your app. 2. Navigate to [https://console.cloud.google.com/auth/audience](https://console.cloud.google.com/auth/audience) 1. Verify you are still connected to the project you created credentials for in the URL, and the Select a Project button shows the naming convention you gave your project 3. Do not publish the app yet!!! You still have to test in a lower environment!!! 4. Under Test Users, click the Add Users button 1. This won’t have to be done after you publish the app. It is a step required by Google for the testing period 2. Enter each user’s Google email that is connected to a Fitbit/Google Health login. To be clear, this wouldn’t be their work email. It would be the Google Auth email they use to log in to the Fitbit/Google Health app. 3. After you enter the email and save it, you will see the email addresses configured under User Information on that page. [[ Back to top ]](#top) --- ### Send Google Health credentials to Validic Support This was a journey, and the last thing you need to do is to ensure you have replied to your existing ticket with Validic technical support about Google Health, or create a new ticket with Validic technical support if you don’t have an existing one. What will Validic technical support need? 1. Org ID for the sandbox that the credentials will be added to. 2. The downloaded file with your credentials 3. Screenshot of the scopes you enabled. (If you forgot to take a screenshot, then just include the scopes you selected in the ticket) With that information, Google Health can be enabled in your sandbox environment for testing! ### Enable webhooks for Google Health GCP project You probably want near real time data from your end users through Google Health. Use the instructions here to enable webhooks in your GCP project so you can pass the needed information to Validic Support to get that enabled in your organization as well: [https://help.validic.com/space/VCS/5754421279/Google+Health:+Enable+webhooks+for+near+real+time+data+delivery](https://help.validic.com/space/VCS/5754421279/Google+Health:+Enable+webhooks+for+near+real+time+data+delivery) [[ Back to top ]](#top) --- ### What your testers should be aware of after Google Health is enabled in your org 1. While your app is in Testing mode, they will see below after clicking connect in the marketplace for Google Health and using their Google Auth Just click Continue to test 2. What a user will see while you are in Testing status and someone that hasn’t been added as a tester in the Google Cloud Platform location noted above: 3. Instructions for adding [webhooks](https://help.validic.com/space/VCS/5754421279/Google+Health:+Enable+webhooks+for+near+real+time+data+delivery) are available. Webhooks are required for production configuration. If you don’t have webhooks configured in your sandbox, then scheduled jobs are syncing data. See expected return time frames below: 1. Hourly jobs for summary and workout endpoints 2. Twice a day for sleep and measurement endpoints 3. Nutrition endpoint doesn’t have a scheduled job and requires [webhooks to be configured](https://help.validic.com/space/VCS/5754421279/Google+Health:+Enable+webhooks+for+near+real+time+data+delivery) for data to flow 4. While your credentials are in the testing status in Google Cloud console, there is only about 7 days of refresh token expected. We have seen a test user make it two weeks connected before being disconnected due to an invalid refresh token. If this happens to your user, you would need to reconnect your test user. This isn’t going to be a worry when credentials are in production status in Google Cloud Console, but while testing the integration in your sandbox, you may encounter this. You can see connection events org wide with this endpoint: [https://developer.validic.com/reference/get-connection-events-by-orgid](https://developer.validic.com/reference/get-connection-events-by-orgid) [[ Back to top ]](#top)