![youtube future never end video youtube future never end video](http://www.overlyanimated.com/wp-content/uploads/2018/11/ladybug-mayura_recap.jpg)
YouTube videoId and channelId identifiers are single integer values represented in a slightly modified version of Base64 encoding. There are some edge casesįor newly uploaded videos or private videos, but for most purposes I'd Non-200 response, you have an invalid id. If you get a 200 response, then VIDEO_ID is valid. Video id, I'd recommend doing an empirical test. If you need to validate that random user input corresponds to a valid The Youtube team seems to prefer to directly ask Youtube server if the Video_ID is correct or not (refer to an existing video) : Into your application (unless you have an easy way of changing it in Numbers and some punctuation, I wouldn't recommend hardcoding that While they're currently 11 character strings that contain letters,
![youtube future never end video youtube future never end video](https://i.ytimg.com/vi/P1c-DWFM0-w/hqdefault.jpg)
We don't make any public guarantees about the format for video ids. But we're not offering any officialĬommitment to that, so proceed at your own risk.Īnd last but not least, another post clarify (or not) the format : Of those things where we have a current implementation, and it may To a standard length of 11 characters for YouTube video ids. I don't see anywhere in the documentation where we officially commit According to the Youtube 2.0 API documentation and 3.0 API documentation, the videoId is a string, nothing is specified about the current set of characters used.Ībout the 11 characters length, a post from a Youtube API Team say :