Authorizing requests

Note: The YouTube Content ID API is intended for use by YouTube content partners and is not accessible to all developers or to all YouTube users. If you do not see the YouTube Content ID API as one of the services listed in the Google API Console, see the YouTube Help Center to learn more about the YouTube Partner Program.

The YouTube Content ID API supports the OAuth 2.0 protocol for authorizing access to private user data. The following list explains some core OAuth 2.0 concepts:

  • When a user first attempts to use features in your application that requires the user to be logged in to a Google Account or YouTube account, your application initiates the OAuth 2.0 authorization process.

  • Your application directs the user to Google's authorization server. The link to that page specifies the scope of access that your application is requesting for the user's account. The scope specifies the resources that your application can retrieve, insert, update, or delete when acting as the authenticated user.

  • If the user consents to authorize your application to access those resources, Google returns a token to your application. Depending on your application's type, it either validates the token or exchanges it for a different type of token.

    For example, a server-side web application exchanges the returned token for an access token and a refresh token. The access token lets the application authorize requests on the user's behalf, and the refresh token lets the application retrieve a new access token when the original access token expires.

Important: To use the OAuth 2.0 Authorization, you need to obtain authorization credentials in the Google API Console.

For more details, see the OAuth 2.0 Authorization Guide.

OAuth 2.0 flows

Google APIs support several OAuth 2.0 use cases: