YouTube Data API videos.insert returns hidden “Video Uploads per day” 429 despite quota headroom
まだ誰も着手していません。
評価
調査の方向性
最小限の youtube.videos().insert(...).next_chunk() アップロードフローから始め、その 429 レスポンスを、文書化されているクォータの情報源および issue に記載されている Cloud Quotas コマンドと比較します。完了の条件は、サービス側のクォータの挙動を確認し、クライアント、ドキュメント、またはクォータの可視性に対する実行可能な変更を特定することです。リポジトリ内のファイルやテストは指定されていません。
索引モデルが issue の本文から書いたものです。
説明
Summary
Starting around May 24-25, 2026, uploads through the YouTube Data API videos.insert endpoint began failing after a small number of uploads per day with HTTP 429:
{
"error": {
"code": 429,
"message": "Quota exceeded for quota metric 'Video Uploads' and limit 'Video Uploads per day' of service 'youtube.googleapis.com' for consumer 'project_number:REDACTED'.",
"errors": [
{
"message": "Quota exceeded for quota metric 'Video Uploads' and limit 'Video Uploads per day' of service 'youtube.googleapis.com' for consumer 'project_number:REDACTED'.",
"domain": "global",
"reason": "rateLimitExceeded"
}
]
}
}
This appears to be a hidden or newly enforced quota separate from the documented YouTube Data API quota-unit system.
Expected behavior
According to the YouTube Data API quota documentation:
- Default project quota is 10,000 units/day
videos.insertcosts 100 units- Quota resets at midnight Pacific Time
A default project should therefore support roughly 100 uploads/day, assuming no other significant quota usage.
If there is a separate Video Uploads per day quota, it should be documented and visible in Cloud Console / Cloud Quotas API so developers can monitor it and request increases.
Actual behavior
Uploads fail after roughly 7 uploads/day with:
Quota exceeded for quota metric 'Video Uploads' and limit 'Video Uploads per day'
However:
- Cloud Console shows YouTube Data API quota usage well below 100%
gcloud beta quotas info list --service=youtube.googleapis.comdoes not expose aVideo Uploads per daymetric- Cloud Quotas API also does not appear to expose this metric
- Manual uploads through YouTube Studio to the same channel still work
Environment
- API: YouTube Data API v3
- Method:
videos.insert - Library:
google-api-python-client - Version tested:
2.196.0 - Upload type: resumable upload
- Auth scope:
https://www.googleapis.com/auth/youtube.upload - Project has YouTube Data API enabled
- OAuth app, project, and channel are unchanged from before the regression
Minimal code shape
media = MediaFileUpload(path, chunksize=-1, resumable=True)
request = youtube.videos().insert(
part="snippet,status",
body={
"snippet": {
"title": title,
"description": description,
},
"status": {
"privacyStatus": "private",
},
},
media_body=media,
)
response = None
while response is None:
status, response = request.next_chunk()
Additional evidence
Multiple developers appear to be reporting the same behavior in the same timeframe: API uploads fail after a small number of videos, while Cloud Console still shows quota headroom and manual YouTube Studio uploads still work.
Related Reddit discussion:
https://old.reddit.com/r/googlecloud/comments/1tm1scx/429_quota_exceeded/
Request
Could you please confirm:
- whether
Video Uploads per dayis a new or newly enforced quota; - where this quota can be viewed, monitored, and increased;
- whether the current behavior is intentional;
- if intentional, whether the public YouTube Data API quota docs and Cloud Console / Cloud Quotas API can be updated to expose this metric?
I understand this may be a service-side quota issue rather than a google-api-python-client bug, but the client is currently surfacing an undocumented quota error that developers cannot inspect or manage through the usual quota tools.
Sources checked
- YouTube quota docs: https://developers.google.com/youtube/v3/determine_quota_cost
videos.insertreference: https://developers.google.com/youtube/v3/docs/videos/insert- YouTube upload guide: https://developers.google.com/youtube/v3/guides/uploading_a_video
- Related Reddit thread: https://old.reddit.com/r/googlecloud/comments/1tm1scx/429_quota_exceeded/
- 主要言語
- Python
- スター
- 8.9k
- フォーク
- 2.6k
- 平均マージ
- 2日 2時間
- マージ済み PR(30日)
- 15
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
googleapis/google-api-python-client のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 92/100
-
難易度 4/5 3〜5日 初心者へのやさしさ 52/100
-
samples type: docs
難易度 3/5 1〜2日 初心者へのやさしさ 52/100
googleapis/google-api-python-client の issue をすべて見る
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
xinnan-tech/xiaozhi-fde-talk#263 ·
-
rules
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
huggingface/Repo2RLEnv#163 · コメント 1 件 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 95/100
huggingface/sentence-transformers#4074 ·
-
comp/dashboard invalid P3
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
NousResearch/hermes-agent#121143 ·