Get your Google API client ID
Stay organized with collections
Save and categorize content based on your preferences.
Google Sign-In manages the OAuth 2.0 flow and token lifecycle, simplifying your
integration with Google APIs. A user always has the option to revoke access
to an application at any time.
Before you can integrate Google 3P Authorization library into your website, you
must create a client ID, which you need to call the 3P Authorization API.
To create a Google Cloud console Project and Client ID, follow the
instructions to get your Google API client ID.
When you configure the project, select the Web browser client type and specify
the origin URI of your app. When you perform tests, both http://localhost and
http://localhost:<port_number> must be added to the Authorized JavaScript
origins field.
After configuration is complete, take note of the client ID that was created.
You will need the client ID to complete the next steps. (A client secret is also
created, but you need it only for server-side operations.)
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-05 UTC.
[null,null,["Last updated 2025-08-05 UTC."],[[["\u003cp\u003eGoogle Sign-In streamlines the use of Google APIs by managing the OAuth 2.0 flow and token lifecycle, allowing users to revoke access at any time.\u003c/p\u003e\n"],["\u003cp\u003eBefore integrating Google 3P Authorization, you need to create a client ID within a Google API Console project, specifying the Web browser client type and authorized origins including localhost for testing.\u003c/p\u003e\n"],["\u003cp\u003eAfter project configuration, note the generated client ID, which is essential for subsequent integration steps.\u003c/p\u003e\n"]]],[],null,["# Get your Google API client ID\n\nGoogle Sign-In manages the OAuth 2.0 flow and token lifecycle, simplifying your\nintegration with Google APIs. A user always has the option to [revoke access](https://myaccount.google.com/permissions)\nto an application at any time.\n\nBefore you can integrate Google 3P Authorization library into your website, you\nmust create a client ID, which you need to call the 3P Authorization API.\n\nTo create a Google Cloud console Project and Client ID, follow the\n[instructions to get your Google API client ID](https://developers.google.com/identity/gsi/web/guides/get-google-api-clientid#get_your_google_api_client_id).\n\nWhen you configure the project, select the Web browser client type and specify\nthe origin URI of your app. When you perform tests, both `http://localhost` and\n`http://localhost:\u003cport_number\u003e` must be added to the Authorized JavaScript\norigins field.\n\nAfter configuration is complete, take note of the client ID that was created.\nYou will need the client ID to complete the next steps. (A client secret is also\ncreated, but you need it only for server-side operations.)"]]