Stay organized with collectionsSave and categorize content based on your preferences.
Authorize Requests
When your application requests private data, the request must be authorized by an authenticated user who has access to that data.
Every request your application sends to the Indexing API must include an authorization token. The token also identifies your application to Google.
About authorization protocols
Your application must useOAuth 2.0to authorize requests. No other authorization protocols are supported. If your application usesSign In With Google, some aspects of authorization are handled for you.
Authorizing requests with OAuth 2.0
All requests to the Indexing API must be authorized by an authenticated user.
The details of the authorization process, or "flow," for OAuth 2.0 vary somewhat depending on what kind of application you're writing. The following general process applies to all application types:
When you create your application, you register it using theGoogle API Console. Google then provides information you'll need later, such as a client ID and a
client secret.
Activate the Indexing API in the Google API Console. (If the API isn't listed in the API Console, then skip this step.)
When your application needs access to user data, it asks Google for a particularscopeof access.
Google displays aconsent screento the user, asking them to authorize your application to request some of their data.
If the user approves, then Google gives your application a short-livedaccess token.
Your application requests user data, attaching the access token to the request.
If Google determines that your request and the token are valid, it returns the requested data.
Some flows include additional steps, such as usingrefresh tokensto acquire new access tokens. For detailed information about flows for various types of applications, see Google'sOAuth 2.0 documentation.
Here's the OAuth 2.0 scope information for the Indexing API:
Scope
Meaning
https://www.googleapis.com/auth/indexing
Read/write access.
To request access using OAuth 2.0, your application needs the scope information, as well as
information that Google supplies when you register your application (such as the client ID and the
client secret).
Tip:The Google APIs client libraries can handle some of the authorization process for you. They are available for a variety of programming languages; check thepage with libraries and samplesfor more details.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eThe Indexing API requires authorization for all requests using OAuth 2.0 for accessing private user data.\u003c/p\u003e\n"],["\u003cp\u003eApplications need to be registered with Google API Console and the Indexing API activated to initiate the authorization process.\u003c/p\u003e\n"],["\u003cp\u003eUsers are presented with a consent screen to grant access, and upon approval, the application receives a short-lived access token to make authorized requests.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's client libraries offer built-in support for handling parts of the authorization, simplifying the process for developers.\u003c/p\u003e\n"]]],["Applications must use OAuth 2.0 to authorize requests for private data from the Indexing API. This requires registering the application with the Google API Console to obtain a client ID and secret. The application requests a specific access scope from Google, which then prompts the user for consent. Upon approval, Google issues a short-lived access token. This token is attached to data requests, and Google validates it before providing the requested data. The scope for the Indexing API is `https://www.googleapis.com/auth/indexing` for read/write access.\n"],null,["# Authorize Requests | Indexing API Documentation | Google Search Central\n\nAuthorize Requests\n==================\n\nWhen your application requests private data, the request must be authorized by an authenticated user who has access to that data.\n\nEvery request your application sends to the Indexing API must include an authorization token. The token also identifies your application to Google.\n\nAbout authorization protocols\n-----------------------------\n\nYour application must use [OAuth 2.0](https://developers.google.com/identity/protocols/OAuth2) to authorize requests. No other authorization protocols are supported. If your application uses [Sign In With Google](https://developers.google.com/identity/gsi/web), some aspects of authorization are handled for you.\n\nAuthorizing requests with OAuth 2.0\n-----------------------------------\n\nAll requests to the Indexing API must be authorized by an authenticated user.\n\nThe details of the authorization process, or \"flow,\" for OAuth 2.0 vary somewhat depending on what kind of application you're writing. The following general process applies to all application types:\n\n1. When you create your application, you register it using the [Google API Console](https://console.cloud.google.com/). Google then provides information you'll need later, such as a client ID and a client secret.\n2. Activate the Indexing API in the Google API Console. (If the API isn't listed in the API Console, then skip this step.)\n3. When your application needs access to user data, it asks Google for a particular **scope** of access.\n4. Google displays a **consent screen** to the user, asking them to authorize your application to request some of their data.\n5. If the user approves, then Google gives your application a short-lived **access token**.\n6. Your application requests user data, attaching the access token to the request.\n7. If Google determines that your request and the token are valid, it returns the requested data.\n\nSome flows include additional steps, such as using **refresh tokens** to acquire new access tokens. For detailed information about flows for various types of applications, see Google's [OAuth 2.0 documentation](https://developers.google.com/identity/protocols/OAuth2).\n\nHere's the OAuth 2.0 scope information for the Indexing API:\n\n| Scope | Meaning |\n|--------------------------------------------|--------------------|\n| `https://www.googleapis.com/auth/indexing` | Read/write access. |\n\nTo request access using OAuth 2.0, your application needs the scope information, as well as\ninformation that Google supplies when you register your application (such as the client ID and the\nclient secret).\n\n**Tip:** The Google APIs client libraries can handle some of the authorization process for you. They are available for a variety of programming languages; check the [page with libraries and samples](/search/apis/indexing-api/v3/libraries) for more details."]]
