Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
YouTube Reporting API y YouTube Analytics API admiten el protocolo OAuth 2.0 para autorizar el acceso a los datos privados del usuario.
En la siguiente lista, se explican algunos conceptos básicos de OAuth 2.0:
Cuando un usuario intenta usar por primera vez funciones de tu aplicación que requieren que acceda a un Google Account or YouTube account, tu aplicación inicia el proceso de autorización de OAuth 2.0.
La aplicación dirige al usuario al servidor de autorización de Google. El vínculo a esa página especifica el scope de acceso que tu aplicación solicita para la cuenta del usuario. El objeto scope especifica los recursos que tu aplicación puede recuperar, insertar, actualizar o borrar cuando actúa como el usuario autenticado.
Si el usuario da su consentimiento y autoriza a la aplicación a acceder a esos recursos, Google genera un token para la aplicación. Dependiendo del tipo de aplicación, puede validar el token o cambiarlo por uno de otro tipo.
Por ejemplo, una aplicación web del servidor cambia el token que se generó por un token de acceso y otro de actualización. El token de acceso permite a la aplicación autorizar solicitudes en nombre del usuario, mientras que el token de actualización permite a la aplicación obtener un nuevo token de acceso cuando el original expire.
El flujo de OAuth 2.0 para TVs y dispositivos de entrada limitada admite dispositivos con capacidades de entrada limitada, como consolas de juegos y cámaras de video.
The YouTube Reporting and YouTube Analytics APIs do not currently support the OAuth 2.0 flow for devices.
El flujo de OAuth 2.0 para cuentas de servicio admite interacciones de servidor a servidor que no acceden a la información del usuario.
Sin embargo, YouTube Reporting API y YouTube Analytics API no admiten este flujo.
Since there is no way to link a Service Account to a YouTube account, attempts to authorize requests with this flow will generate an error.
Identifica los permisos de acceso
Los permisos permiten que tu aplicación solo solicite acceso a los recursos que necesita, al tiempo que permiten a los usuarios controlar el nivel de acceso que otorgan a tu aplicación. Por lo tanto, puede haber una relación inversa entre la cantidad de permisos solicitados y la probabilidad de obtener el consentimiento del usuario.
Antes de que comiences a implementar la autorización de OAuth 2.0, te recomendamos identificar los permisos
a los que tu app necesitará acceder.
La API de YouTube Analytics usa los siguientes alcances:
Alcance
Descripción
https://www.googleapis.com/auth/youtube
Administrar tu cuenta de YouTube
https://www.googleapis.com/auth/youtube.readonly
Permite ver tu cuenta de YouTube.
https://www.googleapis.com/auth/youtubepartner
Ver y administrar sus elementos y el contenido asociado en YouTube
[null,null,["Última actualización: 2025-08-21 (UTC)"],[[["\u003cp\u003eThe YouTube Reporting API and YouTube Analytics API utilize OAuth 2.0 for authorizing access to private user data.\u003c/p\u003e\n"],["\u003cp\u003eOAuth 2.0 requires user consent, and the scope requested determines the resources the application can access, with a possible inverse relationship between the number of scopes and the likelihood of consent.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's OAuth 2.0 supports various flows including server-side web apps, JavaScript web apps, and mobile/desktop apps, but it doesn't support the device flow for YouTube Reporting and Analytics APIs, or the service account flow.\u003c/p\u003e\n"],["\u003cp\u003eBefore implementing OAuth 2.0, it's recommended to identify the necessary scopes, with specific scopes for the YouTube Analytics API and YouTube Reporting API being detailed, as well as a document containing a full list of possible scopes for Google APIs.\u003c/p\u003e\n"],["\u003cp\u003eIf your application uses scopes that permit access to certain user data, you might need to complete a verification process, especially if you encounter an "unverified app" warning.\u003c/p\u003e\n"]]],["OAuth 2.0 authorizes access to private YouTube user data. Applications initiate authorization, directing users to Google's server to specify access scopes. User consent grants a token, which can be exchanged for access and refresh tokens. Credentials must be obtained via the Google API Console. Supported flows include server-side, JavaScript, and mobile/desktop apps, but not limited-input devices or service accounts. Scopes, defined for YouTube Analytics and Reporting APIs, dictate resource access and influence user consent. Public apps accessing user data must undergo verification.\n"],null,["# Implement OAuth 2.0 Authorization\n\nThe YouTube Reporting API and YouTube Analytics API support the [OAuth 2.0 protocol](http://oauth.net/2/) for authorizing access to private user data.\n\nThe following list explains some core OAuth 2.0 concepts:\n\n- 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.\n\n- 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.\n\n- 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.\n\n 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.\n\n**Important:** To use the OAuth 2.0 Authorization, you need to [obtain authorization credentials in the Google API Console](/youtube/reporting/guides/registering_an_application).\n\nFor more details, see the [OAuth 2.0 Authorization Guide](https://developers.google.com/identity/protocols/oauth2).\n\nOAuth 2.0 flows\n---------------\n\nGoogle APIs support several OAuth 2.0 use cases:\n\n- The [server-side web apps](/youtube/reporting/guides/authorization/server-side-web-apps) flow supports web applications that can securely store persistent information.\n- The [JavaScript web apps](/youtube/reporting/guides/authorization/client-side-web-apps) flow supports JavaScript applications running in a browser.\n- The [mobile and desktop apps](/youtube/reporting/guides/authorization/installed-apps) flow supports applications installed on a device, such as a phone or computer.\n- The OAuth 2.0 flow for TVs and limited-input devices supports devices with limited input capabilities, such as game consoles and video cameras. The YouTube Reporting and YouTube Analytics APIs do not currently support the OAuth 2.0 flow for devices.\n- The OAuth 2.0 flow for service account flow supports server-to-server interactions that do not access user information. However, the YouTube Reporting API and YouTube Analytics API do not support this flow. Since there is no way to link a Service Account to a YouTube account, attempts to authorize requests with this flow will generate an error.\n\n### Identify access scopes\n\nScopes enable your application to only request access to the resources that it needs while also\nenabling users to control the amount of access that they grant to your application. Thus, there\nmay be an inverse relationship between the number of scopes requested and the likelihood of\nobtaining user consent.\n\nBefore you start implementing OAuth 2.0 authorization, we recommend that you identify the scopes\nthat your app will need permission to access.\n\nThe YouTube Analytics API uses the following scopes:\n\nThe YouTube Reporting API uses the following scopes:\n\nThe [OAuth 2.0 API Scopes](/identity/protocols/oauth2/scopes) document contains a full\nlist of scopes that you might use to access Google APIs.\n| If your public application uses scopes that permit access to certain user data, it must complete a verification process. If you see **unverified\n| app** on the screen when testing your application, you must submit a verification request to remove it. Find out more about [unverified apps](https://support.google.com/cloud/answer/7454865) and get answers to [frequently asked questions about app verification](https://support.google.com/cloud/answer/9110914) in the Help Center."]]
