Each entry in the adaptiveFormats field of /api/v1/videos/:id has different available fields. For example, audio streams are missing resolution and qualityLabel. This is currently not mentioned anywhere in the documentation, so it would be better to have these missing fields to return null instead, or at least mention it in the API docs.
Steps to Reproduce
have and API request on video page, e.g. /api/v1/videos/xuCn8ux2gbs
I found 3 types of entry:
Video streams (except AV1) : all fields available
This is because the data we return is directly what youtube provides, hence the API instability.
The API needs a proper lifting, and that's why I'm marking this as an enhancement.
Describe the bug
Each entry in the
adaptiveFormats
field of/api/v1/videos/:id
has different available fields. For example, audio streams are missingresolution
andqualityLabel
. This is currently not mentioned anywhere in the documentation, so it would be better to have these missing fields to returnnull
instead, or at least mention it in the API docs.Steps to Reproduce
have and API request on video page, e.g.
/api/v1/videos/xuCn8ux2gbs
I found 3 types of entry: Video streams (except AV1) : all fields availableAudio streams (missing
resolution
andqualityLabel
):AV1 video stream (missing
fps
,container
,encoding
,resolution
andqualityLabel
):Logs
Screenshots
Additional context