Guides · social · Verification-gated

YouTube Data API v3 (keys, quota and compliance audit)

Enable the YouTube Data API in a Google Cloud project and create an API key or OAuth client. The default quota is small (10,000 units a day plus 100 search and 100 upload calls); more quota, and public uploads from new projects, require passing a YouTube API Services compliance audit.

Researched · not yet run liveLast researched 25 October 2026 · Google · 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.

Who owns what

Everything lives in one Google Cloud project owned by your Google Account or organisation. YouTube's policies require exactly one Cloud project per API client (your app), and quota, audits and the API key or OAuth client all belong to that project. End users' YouTube channels are reached through OAuth, not through your own account.

  • Google Account or Google Workspace/Cloud organisation organisation owned by the company or the person
  • Google Cloud project (one per API client) project owned by the company or the person · under Google Account or Google Workspace/Cloud organisationUsing several projects for one app to get more quota breaks the policies.

Public data reads can use an API key; anything on a user's channel (uploads, edits, private data) needs OAuth 2.0 user authorisation.

Have ready

  • google/cloud-project-run: Any Google Cloud project works; Cloud Run, Firestore and the domain parts are not needed.
  • google/oauth-verification: Only if you use OAuth with YouTube scopes for public users; whether each YouTube scope counts as sensitive [to verify].
  • Public privacy policy that users must accept before using the API features, linking to Google's privacy policy · Required by the YouTube Developer Policies and checked in audits. [5]Needed for: Pass the compliance audit (for more quota or public uploads)
  • Live app or website showing how YouTube data is used and displayed (with YouTube branding) [5]Needed for: Pass the compliance audit (for more quota or public uploads)
  • Screencast or test account showing the API client in use [to verify which the audit asks for] · Policies require you to provide test accounts when audited. [5]Needed for: Pass the compliance audit (for more quota or public uploads)
  • Quota estimate by endpoint (calls per day multiplied by unit cost) and a clear use case · Extra quota is granted for a specific use case only. [5]Needed for: Pass the compliance audit (for more quota or public uploads)

Steps

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

  1. Choose the one Cloud project for this app

    Create or pick a Google Cloud project dedicated to this API client.

    • Guided by hand
    • Human step: You press submit

    Where: https://console.cloud.google.com/projectcreate

  2. Enable YouTube Data API v3

    In the API Library, enable "YouTube Data API v3" for the project.

    • Guided by hand
    • Human step: You press submit
    • After: Choose the one Cloud project for this app

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

  3. Create an API key for public data

    In Credentials, create an API key and restrict it to YouTube Data API v3 (and to your app's referrers, IPs or package) so it cannot be abused [to verify restriction options for your platform].

    • Guided by hand
    • Human step: You press submit
    • After: Enable YouTube Data API v3

    verapli captures YOUTUBE_API_KEY here by plain code: encrypted in your browser, never shown to AI.

    Where: https://console.cloud.google.com/apis/credentials

  4. Create an OAuth client for channel actionsoptional

    For uploads, edits or private data, configure the OAuth consent screen and create an OAuth client ID. Apps for the public need Google OAuth verification (see google/oauth-verification).

    • Guided by hand
    • Human step: You press submit
    • After: Enable YouTube Data API v3

    Where: https://console.cloud.google.com/apis/credentials

  5. Check quota and estimate usage

    Open the Quotas page. Default is 10,000 units a day for most endpoints plus 100 search.list and 100 videos.insert calls. Reads usually cost 1 unit, writes 50. Work out whether you need more.

    • Guided by hand
    • After: Enable YouTube Data API v3

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

  6. Pass the compliance audit (for more quota or public uploads)optional

    Make sure the app complies with the YouTube API Services Terms and Developer Policies, then submit the Audit and Quota Extension Form. A YouTube API Services team member contacts you. New projects (after 28 July 2020) need this before uploads can be anything but private.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Check quota and estimate usage
    The provider says
    No timeframe given; YouTube says the team will contact you as soon as possible. [2]
    People report
    People report several weeks to several months, often with follow-up questions (vendor blog). [7]
    If something goes wrong (3)
    • Uploaded videos are stuck as private: The project is unverified and was created after 28 July 2020; pass the audit to lift the restriction. Staying under quota does not help. [6]
    • 403 quotaExceeded: Reduce calls (cache, avoid search.list, batch ids into list calls) or apply for more quota through the audit form; do not create extra projects. [5]
    • Audit failed or quota denied: Fix the compliance issues named, then appeal with the Appeals Form. [4]

    Where: https://support.google.com/youtube/contact/yt_api_form

Terms and gotchas

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

Can get you bannedThe rules say

One project per app

You must create exactly one API project for each API client. Spreading one app across several projects to get more quota breaks the Developer Policies and can lead to suspension. [5]

Can get you bannedThe rules say

Quota is tied to your approved use case

Extra quota may only be used for the use case that was approved; a new use case needs a new audit. [5]

Can cost moneyThe rules say

Data retention limits

Non-authorised statistics may be stored for at most 30 days, and user data must be deleted within 7 calendar days of a deletion request. [5]

Can cost moneyThe rules say

YouTube can audit you at any time

YouTube may monitor and audit your use at any time; you must not interfere and must provide test accounts when asked. [5]

Worth knowingThe rules say

Tell YouTube about a change of control

After a merger, acquisition or similar change of control, submit the Change of Control Form. [2]

What you end up with

Env varSecretFormatWhat it is
YOUTUBE_API_KEYsecretAIza…API key for public YouTube Data API calls
YOUTUBE_OAUTH_CLIENT_IDnot secret1234567890-abc123.apps.googleusercontent.comOAuth 2.0 client id for user-authorised calls
YOUTUBE_OAUTH_CLIENT_SECRETsecretGOCSPX-…OAuth 2.0 client secret (web server apps only)

Renewals

  • Re-audit when you need more quota again (an audit within the last 12 months can be reused via the same form) or when contacted for a periodic audit: every when requested (periodic audits) [to verify any fixed cycle] [2]

Pricing

  • Free tier: Default 10,000 units/day plus 100 search.list and 100 videos.insert calls per project.
  • The official docs describe quota, not charges; extra quota is obtained by audit, not purchase [to verify].

Source [1]

For agents

The same entry as JSON: /api/v1/entries/google/youtube-data-api · requirements /api/v1/requirements/google/youtube-data-api · terms /api/v1/terms/google/youtube-data-api.

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

> "What do I need for YouTube Data API v3 (keys, quota and compliance audit), and how long will it take?"
  → tools/call requirements { "provider_id": "google/youtube-data-api" }

Sources

  1. YouTube Data API – Getting started Need a Google Account, a Cloud project, enable the API, API key or OAuth credentials; writes need user authorisation; default 100 search.list, 100 videos.insert and 10,000 units/day for other endpoints; reads usually 1 unit, writes usually 50 units; every request costs at least 1 unit · accessed 25 October 2026 · official
  2. YouTube Data API – Quota and compliance audits More quota requires an audit via the Audit and Quota Extension Form; team contacts you as soon as possible (no timeframe); periodic audits use the Periodic Audit Form; appeals form; change of control form for mergers and acquisitions · accessed 25 October 2026 · official
  3. YouTube API Services – Audit and Quota Extension Form Form used to request an audit and quota extension; denials can be appealed · accessed 25 October 2026 · official
  4. YouTube API Services – Appeals Form Appeal a failed audit or denied quota extension · accessed 25 October 2026 · official
  5. YouTube API Services – Developer Policies Exactly one API project per API client; no extra projects for quota; privacy policy required before use; show YouTube as source with brand features; delete user data within 7 days of request; non-authorised statistics stored at most 30 days; YouTube may audit any time; extra quota only for the approved use case; suspension for non-compliance · accessed 25 October 2026 · official
  6. YouTube Data API – Videos insert Videos uploaded from unverified API projects created after 28 July 2020 are restricted to private viewing until the project passes an audit · accessed 25 October 2026 · official
  7. Phyllo – Is the YouTube API free in 2026? (vendor blog) People report quota extension reviews take weeks to months, with follow-up questions; vendor with an alternative product · accessed 25 October 2026 · community

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