Obtaining authorization credentials
Stay organized with collections
Save and categorize content based on your preferences.
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.
Your application must have authorization credentials to be able to use the YouTube Content ID API.
This document describes the different types of authorization credentials that the Google API Console
supports. It also explains how to find or create authorization credentials for your project.
Create your project and select API services
- Open the Credentials page
in the API Console.
- The page allows you to create two different types of credentials.
However, all of the methods for the YouTube Content ID API require OAuth 2.0
authorization.
Follow the instructions below to generate OAuth 2.0 credentials.
-
OAuth 2.0:
Whenever your application requests private user
data, it must send an OAuth 2.0 token along with the request. Your
application first sends a client ID and, possibly, a client secret to
obtain a token. You can generate OAuth 2.0 credentials for web
applications, service accounts, or installed applications.
For more information, see the OAuth 2.0 documentation
.
-
API keys:
You have the option of including an API key with a request.
The key identifies your project and provides API access, quota, and
reports.
Note that all of the methods for the YouTube Content ID API require
OAuth 2.0 authorization.
For that reason, you need to follow the instructions above for
generating OAuth 2.0 credentials. If you want, you can also send an
API key, but that's not necessary.
The API supports several types of restrictions on API keys. If the API key that you
need doesn't already exist, then create an API key in the Console by
clicking Create credentials
> API key
. You can restrict the key before using it
in production by clicking Restrict key
and selecting one of the Restrictions
.
To keep your API keys secure, follow the best practices for
securely using API keys
.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-28 UTC.
[[["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 YouTube Content ID API is exclusively for YouTube content partners and requires authorization credentials for use.\u003c/p\u003e\n"],["\u003cp\u003eAccess to the YouTube Content ID API requires OAuth 2.0 authorization, which involves sending a client ID and possibly a client secret to obtain a token.\u003c/p\u003e\n"],["\u003cp\u003eWhile API keys can be optionally included with requests, they are not required for the YouTube Content ID API, and OAuth 2.0 authorization is mandatory.\u003c/p\u003e\n"],["\u003cp\u003eYou can create OAuth 2.0 credentials or optional API keys through the Google API Console's Credentials page, located at console.cloud.google.com/apis/credentials.\u003c/p\u003e\n"]]],["The YouTube Content ID API, exclusive to YouTube content partners, requires OAuth 2.0 authorization for all methods. To use it, access the Credentials page in the Google API Console, and generate OAuth 2.0 credentials for your project. While API keys can be created for project identification and access, they are not sufficient for this API, and are optional. To create an API key you have to select the \"Create credentials\" option in the console. API keys can be restricted and must be securely managed.\n"],null,["**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](https://console.cloud.google.com/), see the [YouTube Help Center](https://support.google.com/youtube/answer/72851) to learn more about the YouTube Partner Program.\n\n\nYour application must have authorization credentials to be able to use the YouTube Content ID API.\n\nThis document describes the different types of authorization credentials that the [Google API Console](https://console.cloud.google.com/) supports. It also explains how to find or create authorization credentials for your project.\n\nCreate your project and select API services\n\n1. Open the [Credentials page](https://console.cloud.google.com/apis/credentials) in the API Console.\n2. The page allows you to create two different types of credentials. However, all of the methods for the YouTube Content ID API require OAuth 2.0 authorization. Follow the instructions below to generate OAuth 2.0 credentials.\n - **OAuth 2.0:** Whenever your application requests private user\n data, it must send an OAuth 2.0 token along with the request. Your\n application first sends a client ID and, possibly, a client secret to\n obtain a token. You can generate OAuth 2.0 credentials for web\n applications, service accounts, or installed applications.\n\n For more information, see the [OAuth 2.0 documentation](https://developers.google.com/identity/protocols/OAuth2).\n - **API keys:**\n\n You have the option of including an API key with a request.\n\n The key identifies your project and provides API access, quota, and\n reports.\n\n\n Note that all of the methods for the YouTube Content ID API require\n OAuth 2.0 authorization.\n\n\n For that reason, you need to follow the instructions above for\n generating OAuth 2.0 credentials. If you want, you can also send an\n API key, but that's not necessary.\n\n The API supports several types of restrictions on API keys. If the API key that you\n need doesn't already exist, then create an API key in the Console by\n clicking **[Create credentials](https://console.cloud.google.com/apis/credentials) \\\u003e API key** . You can restrict the key before using it\n in production by clicking **Restrict key** and selecting one of the\n **Restrictions**.\n\nTo keep your API keys secure, follow the [best practices for\nsecurely using API keys](//cloud.google.com/docs/authentication/api-keys)."]]
