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. |