Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Os YouTube Reporting API e YouTube Analytics API são compatíveis com o protocolo OAuth 2.0 para autorizar o acesso a dados particulares do usuário.
A lista a seguir explica alguns conceitos básicos do OAuth 2.0:
Quando um usuário tenta usar recursos no seu aplicativo que exigem login em um Google Account or YouTube account, o aplicativo inicia o processo de autorização do OAuth 2.0.
Seu aplicativo redireciona o usuário ao servidor de autorização do Google. O link para essa página especifica o scope de acesso que seu aplicativo está solicitando para a conta do usuário. O scope especifica os recursos que seu aplicativo pode recuperar, inserir, atualizar ou excluir ao agir como o usuário autenticado.
Se o usuário consentir em autorizar seu aplicativo para acessar os recursos, o Google retorna um token a seu aplicativo. Dependendo do tipo do aplicativo, ele valida ou token ou troca-o por um tipo de token diferente.
Por exemplo, um aplicativoda Web do lado do servidor troca o token retornado por um token de acesso e um token de atualização. Com o token de acesso, o aplicativo pode autorizar solicitações em nome do usuário. Já o token de atualização permite que o aplicativo recupere um novo token de acesso quando o token de acesso original expirar.
O fluxo do OAuth 2.0 para TVs e dispositivos de entrada limitada é compatível com dispositivos com recursos de entrada limitados, como consoles de jogos e câmeras de vídeo.
The YouTube Reporting and YouTube Analytics APIs do not currently support the OAuth 2.0 flow for devices.
O fluxo do OAuth 2.0 para contas de serviço aceita interações de servidor para servidor que não acessam informações do usuário.
No entanto, os YouTube Reporting API e YouTube Analytics API não são compatíveis com esse fluxo.
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.
Identificar escopos de acesso
Os escopos permitem que seu aplicativo solicite acesso apenas aos recursos necessários, além de permitir que os usuários controlem o nível de acesso que concedem ao seu aplicativo. Assim, pode haver uma relação inversa entre o número de escopos solicitados e a probabilidade de obter o consentimento do usuário.
Antes de começar a implementar a autorização do OAuth 2.0, recomendamos que você identifique os escopos
que seu app precisará de permissão para acessar.
A API YouTube Analytics usa os seguintes escopos:
Escopo
Descrição
https://www.googleapis.com/auth/youtube
Gerenciar sua conta do YouTube
https://www.googleapis.com/auth/youtube.readonly
Visualize sua conta do YouTube
https://www.googleapis.com/auth/youtubepartner
Ver e gerenciar seus ativos e conteúdos associados no YouTube
[null,null,["Última atualização 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."]]
