Google Base Data API good news for Blogger bloggers

happygeek 0 454 Views

I was reading the and noticed that Google software engineer Matthias Zenger happened to announce the availability of the updated Google Base Data API last week.

This lets you develop applications that can dynamically interact with Google Base, obviously. Perhaps a little less obviously it also allows you to query other users' published content, making domain-specific search mashups a possibility. The API is ReST-full and based on the GData protocol, which combines XML-based syndication formats with feed-publishing, using a mix of Atom and RSS.

What excites me even more, although I admit to being fairly easily pleased, is the fact that this means that Blogger now has a GData API as well, allowing client applications to both view and update content as GData feeds. There is a very useful official document that not only is packed full of handy sample code, but also has plenty of links to downloadable client libraries for C# and Java developers. The API works with both the current and Beta versions of Blogger, meaning a seamless transition for any client application should be a reality.

Dani AI

Generated

Short update and practical notes following ’s 2006 post about the GData-enabled Google Base and Blogger hooks. The original GData announcement (Matthias Zenger) showed how Atom/RSS-style feeds and the AtomPub model let clients read/write Blogger and Google Base programmatically. (developers.googleblog.com)

Important timeline: Google Base’s Data API was deprecated as Google consolidated shopping/product APIs and the Base API was retired (developers were given until June 1, 2011). Product- and merchant-focused functionality moved to the Content/Merchant APIs, so any Google-Base-based mashups that relied on the Base feed endpoints need migration. (developers.googleblog.com)

Blogger today uses a JSON/REST API (Blogger API v3); public reads can use an API key, while private actions require OAuth 2.0. New projects should use the v3 docs and client libraries rather than the old Atom/GData feeds. A minimal public fetch looks like:

curl "https://www.googleapis.com/blogger/v3/blogs/BLOG_ID/posts?key=YOUR_API_KEY"

See the official getting-started docs for endpoints, auth scopes, and client libraries. (developers.google.com)

Practical migration checklist (short):

  • Inventory what you used from GData (feed types, write/update, query features) and map product data to the Content/Merchant APIs where relevant. (developers.google.com)
  • Replace ClientLogin/GData auth with OAuth 2.0 (or API keys for public reads). (developers.google.com)
  • Swap XML/Atom parsing for JSON handling (Blogger v3 returns JSON).
  • Use Google’s official client libraries (they handle auth, retries, paging) and watch quota/scale limits during testing.

This preserves the spirit of ’s original suggestions while giving concrete, up-to-date pointers for anyone finding this thread years later.

Member Avatar for roger.s
roger.s 0 Newbie Poster

Nice post on google's development - Can u post more tech articles on what you work & what you see is the trend in google's development labs.

Storage Professionals Office Life Regular day tasks- interesting blog on Storage area networking jobs http://storage-jobs.blogspot.com

Member Avatar for happygeek
happygeek 2,411 Most Valuable Poster

Sure. I try to post a good balanced mix of news and opinion here, but am happy to up the tech ante every now and then :)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Edit Preview