We have encountered a potential issue regarding playlist IDs returned by the YouTube Data API and their usage in YouTube Aspera uploads.

Background

We create playlists programmatically using the YouTube Data API v3 (playlists.insert) through the official PHP SDK.

Example code:

$playlist = new Google_Service_YouTube_Playlist();
$playlist->setSnippet($snippet);
$playlist->setStatus($status);

$result = $service->playlists->insert(
    ['snippet', 'status'],
    $playlist
);

Some newly created playlists return IDs similar to:

PLZfNoYeTnhXIed5zGmaF3taBjHXIFPw2x

These playlist IDs work correctly with YouTube Aspera uploads.

However, some playlists created through the same API return shorter IDs, for example:

PLQTt1f_6YJAI

Verification

We have verified that the shorter playlist ID is valid:

1. The playlist can be successfully retrieved using playlists.list.

2. The playlist can be opened normally on YouTube using:

https://www.youtube.com/playlist?list=PLQTt1f_6YJAI

3. The API recognizes the playlist without any errors.

Problem

When using the same playlist ID in a YouTube Aspera CSV upload file:

playlist_id
PLQTt1f_6YJAI

the upload fails with the following error:

PLAYLIST_ID_WRONG_FORMAT

Questions

1. Are shorter playlist IDs such as PLQTt1f_6YJAI officially supported playlist IDs generated by the YouTube Data API?

2. Does YouTube Aspera currently support all valid playlist IDs returned by the YouTube Data API?

3. Is there a known limitation or validation rule in Aspera that rejects certain playlist ID formats?

4. If this is a bug, is there a recommended workaround?

Since the playlist is valid according to the YouTube Data API but is rejected by Aspera, it appears there may be an inconsistency between the API and Aspera playlist ID validation.

We would appreciate any clarification or guidance.

Thank you for your assistance.