All Toolkits

YouTube

Latest version

YouTube is a video-sharing platform with user-generated content, live streaming, and monetization opportunities, widely used for marketing, education, and entertainment

Authentication DetailsComposio-managed OAuth available

Frequently Asked Questions

How do I set up custom Google OAuth credentials for YouTube?

Use your own Google OAuth app when you want your app name on the consent screen, full control over the requested scopes, or your own YouTube API quota (see the quota question below).

Create the Google OAuth app

  1. In Google Cloud Console, select the project that will own the OAuth client, or create one.

    Google Cloud console project picker

  2. Open APIs & Services → Library, search for YouTube Data API v3, and select Enable. If the page shows Manage, the API is already enabled. See Google's server-side web app guide.

    YouTube Data API v3 page in the API Library with the Enable button

  3. Open Google Auth Platform → Branding. If Google shows Get started, enter the app name, user support email, and developer contact email, then save.

    Google Auth Platform Branding page with app name and user support email

  4. Open Audience. Choose Internal to limit the app to users in your Google Workspace organization, or External for consumer accounts and users outside it. While an external app's publishing status is Testing, only accounts listed under Test users can connect, so add every account you'll test with.

    Google Auth Platform Audience page with Testing status, External user type, and Test users

  5. Open Data Access → Add or remove scopes and add the scopes listed under Scopes below. If a scope isn't in the list, paste its full URL under Manually add scopes and select Add to table. Select Update, then Save.

    Data Access scope picker with the youtube.readonly scope selected

  6. Open Clients → Create client, choose Web application, and give it a name.

    Create OAuth client ID form with Web application selected and a client name

  7. Under Authorized redirect URIs, add https://backend.composio.dev/api/v1/auth-apps/add. It must exactly match the oauth_redirect_uri field on your Composio auth config.

    OAuth client form with the Composio redirect URI under Authorized redirect URIs

  8. Select Create. Copy the Client ID and Client secret. Google shows the full secret only once, so save it before you close the dialog.

    OAuth client created dialog with the Client ID and Client secret

Create the auth config in Composio

  1. In the Composio dashboard, open Auth Configs → Create and select YouTube.

    Composio Auth Configs page with the Create button

    Create Auth Config dialog with YouTube in the search results

  2. Choose OAuth 2.0 and Your Own Credentials, then paste your Client ID and Client secret. Leave Redirect URI unchanged, keep the scopes in line with what you added in Google, and select Create Auth Config.

    YouTube auth config form with Client ID, Client secret, Redirect URI, and the youtube.readonly scope

  3. Open the auth config, select Connect Account, and sign in. If Google asks, pick the YouTube channel or Brand Account you want to connect.

    Google consent screen asking to view your YouTube account

  4. Open Accounts on the auth config and confirm the connected account shows Active. The auth config's own Enabled label doesn't confirm a connection.

    Composio auth config panel with the YouTube connected account shown as Active

For the general flow, see Custom auth configs.

Scopes

The default auth config requests these scopes under https://www.googleapis.com/auth/: youtube, youtube.readonly, youtube.force-ssl, youtube.upload, youtube.channel-memberships.creator, youtubepartner, and youtubepartner-channel-audit. To only read channel data, youtube.readonly is enough. Uploads, content management, memberships, and partner operations need their own scopes and, for some, YouTube eligibility. See Google's YouTube authentication guide.

Short scope names on this page leave out the https://www.googleapis.com/auth/ prefix. When you paste a scope under Manually add scopes, use the full URL, for example https://www.googleapis.com/auth/userinfo.email. Scopes already written as a full URL, such as https://mail.google.com/, go in as shown.

Publish and verify the app

While an external app is in Testing, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select Publish app on the Audience page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from Verification Center. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's verification requirements.

Google hasn't verified this app notice for an app in Testing

If you change the requested scopes later, reconnect the account so the user grants the new access.

Why am I getting quota errors on YouTube?

YouTube enforces strict API quotas. If you use the managed/default OAuth app, that quota can be shared across users, so production workloads can hit provider quota limits faster than expected.

For production, create your own Google Cloud OAuth app and use those credentials in the YouTube auth config. That gives your project its own YouTube API quota and lets you control scopes, branding, and quota increase requests in Google Cloud.