YouTube Aspera rejects a legitimate playlist ID returned by YouTube Information API with PLAYLIST_ID_WRONG_FORMAT

YouTube Aspera rejects a legitimate playlist ID returned by YouTube Information API with PLAYLIST_ID_WRONG_FORMAT

Asked today · Stack Overflow
YouTube Aspera rejects a legitimate playlist ID returned by YouTube Information API with PLAYLIST_ID_WRONG_FORMAT

We make playlists programmatically utilizing the YouTube Information API v3 (playlists.insert) with the authoritative PHP SDK.

Illustration:

$playlist = new Google_Service_YouTube_Playlist();$playlist->setSnippet($snippet);$playlist->setStatus($status);$result = $service->playlists->insert( ['snippet', 'status'], $playlist);$playlistId = $result['id'];

1 playlist created done the API returned the pursuing playlist ID:

PLQTt1f_6YJAI

The playlist seems to beryllium legitimate:

  1. playlists.database efficiently returns the playlist.
  2. The playlist tin beryllium opened successful a browser:https://www.youtube.com/playlist?database=PLQTt1f_6YJAINevertheless, once this playlist ID is included successful an Aspera CSV:
playlist_idPLQTt1f_6YJAI

the add fails with:PLAYLIST_ID_WRONG_FORMAT

For examination, different playlist created done the aforesaid API call returns a longer ID specified arsenic:

PLZfNoYeTnhXIed5zGmaF3taBjHXIFPw2x

and that playlist ID is accepted by Aspera.

Is location immoderate documented playlist ID format demand for YouTube Aspera that differs from the playlist IDs accepted by the YouTube Information API?

My anticipation is that immoderate playlist ID returned by playlists.insert ought to besides beryllium accepted by Aspera.

PhpYoutube

Answers

plus metadata). Three. Separate modular YouTube Information API IDs from YouTube Contented Director (CMS) IDs. Four. Codification snippet / XML illustration displaying appropriate metadata construction. Decision: Last wrapping ideas connected standardizing media ingest pipelines
Previous Post Next Post

Formulario de contacto