YouTube Data API

Working in dev?How we estimated thisTime to register an app and complete one sign-in with your own account. It covers console setup, not building your integration.Evidence: InferredCreate a Cloud project, enable YouTube Data API v3, set up the consent screen in Testing with test users, and create a web OAuth client. No review needed.

30–90 min

Signing in with your own account

Any user can connect?How we estimated thisAn agent that reads channel/video data for many users and needs more than the default quota, so it needs both sensitive-scope verification and a quota audit. Google estimates 3-5 to 10 business days for sensitive verification; YouTube publishes no audit timeline, and audits can run months or end in a lower quota or rejection. If 10,000 units/day is enough, only OAuth verification applies (about 1–2 weeks). Includes waiting on: Google Trust & Safety sensitive-scope verification, then the YouTube API Services compliance audit and quota extension review.. Provider review times vary, so this is a range, not a promise.Evidence: InferredEstimate. Google's FAQ says sensitive verification takes '10 Business days' (developer docs: 'typically takes 3-5 business days'), 'not guaranteed'. YouTube's audit page gives no timeline, only that the team will contact you 'as soon as possible', so we allow a few weeks for the audit on top; month-plus audits reported by third parties are tail risk, not typical.

3–8 weeks

An agent that reads channel/video data for many users and needs more than the default quota, so it needs both sensitive-scope verification and a quota audit. Google estimates 3-5 to 10 business days for sensitive verification; YouTube publishes no audit timeline, and audits can run months or end in a lower quota or rejection. If 10,000 units/day is enough, only OAuth verification applies (about 1–2 weeks).