4 ms·

Thanks! Unfortunately, I haven't had time to write an API yet. I'm the only developer, so I focused on the features that needed to be there right away for users

by podman 16y ago

Thanks! Unfortunately, I haven't had time to write an API yet. I'm the only developer, so I focused on the features that needed to be there right away for users to be able to use our service. I had just about 2 weeks to pull this together and still have a fulltime job. Almost none of them needed an API. Building an API, however, is very high up on my list of things to do though. What kind of things would you like to see in an API? I think we have another, very large, customer who needs an API too so I'll try to get something set up ASAP.

karanbhangui 16y ago
I guess for now: - a way to directly upload a video from a file select field (http://code.google.com/apis/youtube/2.0/developers_guide_protocol.html#Browser_based_uploading http://code.google.com/apis/youtube/2.0/developers_guide_pro...) - a unique identifier for the video I can then store in my database with other metadata (which user uploaded it, when, etc). If you want to expose other metadata on the video like compressed size, number of views, etc that'd be great but not yet necessary - a standardized way to embed the videos based on the unique id (above)