You’ve already been able to simply include a photo in a Google Buzz post using the Buzz API. Today we’re making it much easier to add photos to Buzz posts. Additionally, using Picasa as the photo repository, you’ll now be able to wield the Buzz API to take all sorts of other actions on behalf of the user:
Accessing a photo entry through the Buzz API is just as easy as getting an activity. The form for retrieving an activity is:
https://www.googleapis.com/buzz/v1/activities/{userId}/@self/{activityId}
With just a few alterations, we get the form for retrieving a photo:
https://www.googleapis.com/buzz/v1/photos/{userId}/@self/{albumId}/@photos/{photoId}
With live data, it would look like the following URL:
https://www.googleapis.com/buzz/v1/photos/farago/@self/5251364904403459921/@photos/5251366163678993586?alt=json&prettyprint;=true
Browse to that address and you’ll get data that will point to this Picasa photo:
The read-only endpoints will return public data without authentication. For authenticated access to the photos endpoints, you must be granted an OAuth token for the user with both the Buzz and Photos API scopes. For existing users, you will need to discard the OAuth tokens scoped to the Buzz API and request authorization to both scopes. More details can be found on the Google Buzz API documentation site.
Photos are an essential part of social applications. We expect these new capabilities will allow you to enrich your user’s experience with a minimum of fuss. As always, please swing by the Developer Forum to let us know what you think. And if you haven’t already, start using the APIs console to track your API usage and other coolness.
https://www.googleapis.com/buzz/v1/activities/track?q=coffee+OR+tea
<errors xmlns="http://schemas.google.com/g/2005"><error> <domain>GData</domain> <code>required</code> <location type="parameter">postId</location> <internalReason>Post ID is required.</internalReason></error></errors>
