Authentication Types
Stay organized with collections
Save and categorize content based on your preferences.
This page provides a brief overview of authentication for YouTube APIs.
OAuth 2.0 (User Accounts)
OAuth 2.0 allows your application to act on behalf of a human user.
| Details |
| Concept |
"Act on behalf of a User"
Requires a human to sign in and grant permission ("handshake"). The app relies on that specific user's access level (e.g., "Show me the analytics for the channels this user manages").
|
| Best For |
CMS & Channel Management
When accessing sensitive financial data, managing rights, or uploading video content where permission is tied to a specific Google Account.
|
| Required By |
- Data API (Uploads/Playlists)
- Analytics API (Insights)
- Reporting API (Financials)
- Content ID API (Rights Management)
|
| Why? |
These APIs require YouTube to verify who is asking. For example, the Reporting API needs to confirm that the logged-in user actually has admin rights to the Content Owner ID they are requesting reports for. |
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-05-15 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 2026-05-15 UTC."],[],[]]
