Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

AI agents cannot invite reviewers to private YouTube videos via YouTube Data API

Aperta
  • Qualcosa non va?
#3,932 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
32/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
node.js, typescript
Ambito
api

Direzione di ricerca

Inizia dal repository di riproduzione collegato, esegui index.ts con le variabili d’ambiente documentate e ispeziona la sua richiesta diretta videos.update usando part=recipients. Confronta quella richiesta con la documentazione dell’API YouTube videos e con l’issue correlata #3626; il lavoro sarà considerato completato quando sarà confermata una superficie API/client supportata per aggiungere, elencare e rimuovere gli spettatori invitati, oppure quando sarà documentato chiaramente che non ne esiste alcuna.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Please make sure you have searched for information in the following guides.
A screenshot that you have tested with "Try this API".
Image

Errors from the screenshot:

Property "recipients" does not exist in object specification.

You have invalid or missing required parameter values above. If you execute anyway, the response will likely be an error.

API response from the screenshot:

{
  "error": {
    "code": 400,
    "message": "'recipients'",
    "errors": [
      {
        "message": "'recipients'",
        "domain": "youtube.part",
        "reason": "unknownPart",
        "location": "part",
        "locationType": "parameter"
      }
    ]
  }
}
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.

https://github.com/karlhorky/repro-youtube-api-private-video-recipients

A step-by-step description of how to reproduce the issue, based on the linked reproduction.
  1. Clone the linked reproduction repository.
  2. Set YOUTUBE_ACCESS_TOKEN to an OAuth access token for the Google account that owns the test video.
  3. Set YOUTUBE_VIDEO_ID to the ID of a video owned by that account.
  4. From the repository root, run:
    YOUTUBE_ACCESS_TOKEN='...' YOUTUBE_VIDEO_ID='...' node index.ts
  5. The script calls the YouTube Data API videos.update endpoint directly with fetch, using part=recipients.
  6. The request body includes the video ID and an attempted invited-viewer list.
  7. The API rejects the request because recipients is not a supported part.

Expected: the API supports adding invited viewers to a private YouTube video, or documents the supported equivalent.

Actual: the API rejects the request before any invited-viewer validation can happen, because there does not appear to be a supported API surface for private-video invited viewers.

A clear and concise description of what the bug is, and what you expected to happen.

AI-agent workflow blocked: AI agents can upload or update private YouTube videos through the API, but cannot invite specific human reviewers to those private videos.

(also applies to regular scripts and other automation)

YouTube Studio supports account-based access control for private videos: a creator can invite specific Google accounts by email address to view a private video.

The YouTube Data API and generated Node.js client do not appear to expose this same capability.

I expected the API to allow automation of the same private-sharing workflow available in YouTube Studio:

  • Set a video to Private
  • Add invited viewers by email address / Google account
  • List invited viewers
  • Remove invited viewers

Instead, the API rejects the recipients part as unsupported.

This blocks AI agents (for example with Antigravity CLI or Codex CLI or Claude Code, etc). A common agentic workflow is:

  1. Upload or generate a draft video
  2. Keep it private
  3. Invite a specific reviewer, client, student or teammate
  4. Wait for human review
  5. Update the video, publish it later or revoke access

Because the API cannot manage invited viewers, AI agents and other automation systems using private videos are pushed toward:

  1. brittle browser automation against YouTube Studio using Playwright MCP or similar
  2. unofficial client libraries that depend on undocumented YouTube Studio internals, such as https://github.com/adasq/youtube-studio
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **

I expect this behavior because YouTube Studio already supports this private-video sharing workflow in the UI:

Video:

https://github.com/user-attachments/assets/4dbacac6-28bb-462c-898f-6ae0a672de67

Screenshots:

Image Image Image

The YouTube Data API currently documents status.privacyStatus for videos, including private, but there does not appear to be a documented way to manage the invited users for a private video:

https://developers.google.com/youtube/v3/docs/videos

This means there is a mismatch between YouTube Studio functionality and the public API/client surface.

A related earlier report also ran into the same missing API surface when trying to use a recipients part:

Expected behavior:

The API should expose a documented way to manage private-video invited viewers, for example:

  • Adding invited viewers: support a privateSharing / recipients part on videos.update, a videos.permissions.insert method or another documented endpoint for adding account-based private video access
  • Listing invited viewers: support a privateSharing / recipients part on videos.list, a videos.permissions.list method or another documented endpoint for reading the current invited-viewer list
  • Removing invited viewers: support a privateSharing / recipients part on videos.update, a videos.permissions.delete method or another documented endpoint for revoking account-based private video access
  • Validating invited viewers: return clear errors for invalid emails, non-Google accounts, quota issues and permission issues

At minimum, the API should support:

  • Adding invited viewers
  • Listing invited viewers
  • Removing invited viewers
  • Returning clear validation errors for invalid emails, non-Google accounts, quota issues and permission issues
Lingua principale
TypeScript
Stelle
12.3k
Fork
2k
Merge medio
1g 19h
PR unite (30g)
21

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di googleapis/google-api-nodejs-client

Tutte le issue di googleapis/google-api-nodejs-client

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.