Hi everyone,

We've just released support for YouTube (as well as DocList and Picasa) in our PHP Client Library!

New sample applications have been released along with the extensions. See the video below for demos (look for our very own Ryan Boyd) ...Read More

Hi everyone,

We've just released support for YouTube (as well as DocList and Picasa) in our PHP Client Library!

New sample applications have been released along with the extensions. See the video below for demos (look for our very own Ryan Boyd):



YouTube's sample app also comes with a Developer's Guide that walks through the code and highlights important operations.

Check out the full blog post over at the Google Data blog for more details.

Cheers,

Steph

Hi everyone,

We recently pushed out a few notable changes -- take a look! If you notice anything weird, please bring it up in our discussion forum.

Projections. You can now use the /api projection to get a feed without all the HTML markup, making it faster and lighter weight for you to use. A more feed-reader friendly version can be accessed with the /base projection. Read about it more here ...Read More

Hi everyone,

We recently pushed out a few notable changes -- take a look! If you notice anything weird, please bring it up in our discussion forum.

Projections. You can now use the /api projection to get a feed without all the HTML markup, making it faster and lighter weight for you to use. A more feed-reader friendly version can be accessed with the /base projection. Read about it more here: http://code.google.com/apis/youtube/reference.html#Projection

Spelling Suggestions. If we have a better suggestion for your 'vq' query, it will appear like this: (Link to feature request.)

http://gdata.youtube.com/feeds/videos?vq=flowar

<feed>
  <link 
    rel="http://schemas.google.com/g/2006#spellcorrection" 
    type="application/atom+xml" 
    href="http://gdata.youtube.com/feeds/videos?start-index=1&max-results=25&vq=flower&oi=spell&spell=1"/>
...

geoRSS information. You'll now notice geoRSS information returned in video feeds if it's available. Format is the same as other GData APIs with lat/long information like Picasa. (Link to feature request.)

<georss:where>
  <gml:Point>
    <gml:pos>28.61345863342285 -82.6171875</gml:pos>
  </gml:Point>
</georss:where>

Searching within a specific area and filtering by videos with geoRSS information is not available yet. This functionality is planned -- you can follow it in our issue tracker. Star the issue to receive updates.

Notable bug fixes:

• &format=5 restrict now works. This is useful for only returning embeddable videos; format 5 being the embed SWF. (Link to issue.)


• The user subscription feed now pages past 20. (Link to issue.)

Cheers,

Steph

Hi everyone,

The new GData YouTube API is here! If you remember my previous post, we've been working on rewriting the API using the Google data protocol to be more scalable and reliable. We're now ready to release the read-only feeds for you to play with.Read More

Hi everyone,

The new GData YouTube API is here! If you remember my previous post, we've been working on rewriting the API using the Google data protocol to be more scalable and reliable. We're now ready to release the read-only feeds for you to play with.

You'll be able to do all the things you could with the old API (search through videos, get user information, and list playlists). On top of that, we've added more flexibility with filtering, querying, and alternative outputs (e.g. if you want output in JSON). Brand new feeds include video responses, full comments list, and related videos.

Additionally, the Google data client libraries are now at your disposal. The Java client library even has YouTube-specific extensions, and you can check out the Java developer guide for sample code and explanations. More documentation in different languages is on the way

This new API also fulfills many of the feature requests you've been asking for,
e.g. you can now filter search results by upload date, view count, and rating as well as relevance. Visit the wiki for a full list of completed requests.

To get a full picture of what's new, read up on the docs at our new home on
code.google.com. The reference guide, developers guide, and migration guide are great reads. (Not as engaging as Harry Potter 7, but really, what is?)

What will happen to the Legacy API?

The old REST/XML-RPC API will continue to work for at least a year - through
August 30th, 2008. After that, its existence is not guaranteed. If your website or app is using the Legacy API, we recommend switching sooner rather than later. The migration guide will help you through the process.

What's next?

We hear you - we know that upload and other write capabilities are wanted by the community. These features are what we're focusing on next.

We've also tried to anticipate other common questions in our new Knowledge Base.

As always, join the discussion forum to give feedback and ask questions I haven't addressed here. We're excited to see what you can build!

Cheers,

Steph

Hi everyone!

Last Thursday at the Google Developer Day, we announced that the next iteration of the API will be based on the Google data ("GData") standard! We hope to release read feeds later this summer. As the date gets closer, we'll be posting announcements and documentation here, on the ...Read More

Hi everyone!

Last Thursday at the Google Developer Day, we announced that the next iteration of the API will be based on the Google data ("GData") standard! We hope to release read feeds later this summer. As the date gets closer, we'll be posting announcements and documentation here, on the developer homepage, and the forums. Check out our presentation on, of course, YouTube: http://www.youtube.com/watch?v=zEUDvEd31F8

Why GData?

- Better scalability/stability/flexibility
- Standardizing on an existing framework - easier to mash up with other GData APIs
- Setting us up for write feeds later in the year by using the authentication models
- Developers can leverage GData resources, such as client libraries and developer guides

What will happen to the old API?

The existing API will continue to be available for the foreseeable future, but all new features will be built into the GData API. Plenty of notice will be given before the current API goes anywhere.

What do I do now?

Give us feedback! This is your chance to let us know what you want in a YouTube API. The team goes through the API Feature Request wiki regularly, so sign up for our forum (if you haven't already), and get involved!


We hope that the new API will improve the developer experience, and make it even easier to add YouTube content into your project.

Cheers,

Steph

Hi everyone!

Welcome to the official blog for the YouTube API. All important announcements regarding the API will be posted here, so please subscribe to our RSS feed to stay in the loop.Read More

Hi everyone!

Welcome to the official blog for the YouTube API. All important announcements regarding the API will be posted here, so please subscribe to our RSS feed to stay in the loop.

For any developers new to the API, I encourage you to visit the YouTube developer homepage. There, you'll be able to sign up and gain access to YouTube's search results, video details, user details and more for your application or website. We hope the developer community will help us bring YouTube videos to even more people on the web!

To join this growing community, check out our developer forum where you can post questions, answer questions, share your projects, and give feedback. We've been busy working on enhancements to the API, and appreciate all the feedback we've gotten from the folks speaking up there.

Happy coding,

Stephanie