verapli
Sign inJoin free
Menu

Guides · social · Popular APIs

YouTube Data API OAuth scopes, verification and quota audit

YouTube Data API apps that act on a user's channel use sensitive OAuth scopes and need Google OAuth verification for a public launch; going beyond the default daily quota needs a YouTube API Services compliance audit.

Researched · not yet run liveLast researched 25 October 2026 · Google (YouTube) · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

A Google Cloud project holds the OAuth client and the YouTube Data API quota; users authorise access to their own channels.

  • Google Cloud project project

Have ready

  • A Google Cloud project with the YouTube Data API v3 enabled and an OAuth client
  • google/oauth-verification: Public External apps requesting YouTube scopes go through Google OAuth verification.
  • Home page on a domain verified in Search Console [3]Needed for: Submit Google OAuth verification
  • Privacy policy on the same domain [3]Needed for: Submit Google OAuth verification
  • Unlisted YouTube demo of the consent flow and of each scope in use [3]Needed for: Submit Google OAuth verification

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Pick the narrowest YouTube scope

    Prefer youtube.readonly for read-only, youtube.upload for uploads only; youtube and youtube.force-ssl give full or delete-level access. Declare them under Google Auth platform > Data Access.

    • verapli co-pilot
    • Human step: You press submit

    Where: https://console.cloud.google.com/auth/scopes

  2. Submit Google OAuth verification

    Publish the app to production and submit data-access verification with per-scope justifications and a demo video.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Pick the narrowest YouTube scope
    The provider says
    Sensitive scope verification typically takes 3-5 business days. [3]
    If something goes wrong (1)
    • Users see "Google hasn't verified this app"; sign-ups stop at 100 users: Complete verification. [4]

    Where: https://console.cloud.google.com/auth/verification

  3. Check your daily quota use

    Watch usage on the Quotas page; the default is 10,000 units/day plus 100 search.list and 100 videos.insert calls.

    • verapli co-pilot
    • After: Pick the narrowest YouTube scope

    Where: https://console.cloud.google.com/apis/api/youtube.googleapis.com/quotas

  4. Request more quota via the compliance auditoptional

    Submit the YouTube API Services Audit and Quota Extension Form describing your use case; YouTube audits compliance with the YouTube API Services Terms before granting more quota.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Check your daily quota use
    The provider says
    No fixed timeline; a member of the YouTube API Services team contacts you "as soon as possible". [2]
    If something goes wrong (1)
    • Audit failed: Use the appeal form linked from the audits page. [2]

    Where: https://developers.google.com/youtube/v3/guides/quota_and_compliance_audits

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can cost moneyThe rules say

Quota beyond the default needs a compliance audit against the YouTube API Services Terms; YouTube may also run periodic audits when it contacts you. [2]

Can cost moneyThe rules say

Ownership changes affecting an API project need the Change of Control form. [2]

Pricing

  • Free tier: Default 10,000 units/day (plus 100 search.list and 100 videos.insert calls).
  • Extra quota is granted after audit, not purchased [to verify].

Source [2]

For agents

The same entry as JSON: /api/v1/entries/youtube/oauth-verification-scopes · requirements /api/v1/requirements/youtube/oauth-verification-scopes · terms /api/v1/terms/youtube/oauth-verification-scopes.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for YouTube Data API OAuth scopes, verification and quota audit, and how long will it take?"
  → tools/call requirements { "provider_id": "youtube/oauth-verification-scopes" }

Sources

  1. Using OAuth 2.0 for Mobile & Desktop Apps (YouTube Data API) YouTube scopes youtube, youtube.readonly, youtube.upload, youtube.force-ssl, youtubepartner, youtubepartner-channel-audit, youtube.channel-memberships.creator. · accessed 25 October 2026 · official
  2. Quota and Compliance Audits Default allocation 100 search.list calls, 100 videos.insert calls and 10,000 units/day for other endpoints; more quota requires a compliance audit against the YouTube API Services Terms; Audit and Quota Extension Form; YouTube contacts you "as soon as possible"; periodic audits when contacted; appeal and Change of Control forms. · accessed 25 October 2026 · official
  3. Sensitive scope verification "Deleting a YouTube video" cited as a sensitive-scope example; requirements (verified domain, home page and privacy policy, per-scope justification, unlisted YouTube demo video); typically 3-5 business days. · accessed 25 October 2026 · official
  4. Unverified apps Unverified apps show a warning screen and are limited to 100 new users. · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Google (YouTube) is not affiliated with verapli.