Users of the AdWords API need to be aware of the need to have an approved Developer Token by October 1st, or risk losing their connection to Google; plus news from other areas of Google related to code.
Did you register your AdWords token yet? We’re letting you know again, because October 1st will be here very soon, and losing connectivity to the Googleplex because that approved Developer Token isn’t in place would be a Bad Thing.
Specifically, developers using V4 of the AdWords API should be aware of a couple of items beyond the need for the Developer Token. Jon Diorio, Senior Product Marketing Manager at Google, posted about using V4 after October 1st:
If you plan on using V4 on or after October 1, you have two options:
1) Simply leave your headers as they are (using the older “token” header). Given the fact that V4 will be shut down on October 29, we’re not requiring developers to modify their code so late in the V4 lifecycle.
2) Go ahead and update your headers to include both “developerToken” and “applicationToken”. While V4 users are not required to do this, the system will still accept these headers.
As of October 1st, Google begins charging developers “for all operations conducted with their Developer Token (regardless of whether they are using V4 or V5),” Diorio wrote.
Google has several API programs open beyond the AdWords, even though the AdWords API is probably the most significant due to its role in Google’s revenue chain. On the Google Code blog, a Googler named Eric Case brought this post to the attention of developers:
We recently noticed a post on the Data API Discussion list in which Philipp Kewisch started an unofficial Google APIs IRC channel (network: irc.freenode.net, channel: ##google-apis):
“I was working on a program that uses the Google Calendar API and thought it would be great if there was a channel that could answer my small questions quicker than the groups. I myself can offer some insight into raw protocol usage in some languages, javascript, php, and probably a bit of perl – all focused on the Google Calendar API.”
The Googlers won’t be online, but other developers should be available. The channel will be as effective as developer participation makes it, and there’s usually something to be learned from others.
Ajax developers will want to take a peek at the example Google made in combining information from the Future of Web Apps conference and the Ajax Search API + Maps combination.
The map provides a quick back-and-forth navigation through green arrow buttons to move through results for a query. While scrolling through those results, the map updates to show that location along with opening an info bubble atop the pushpin.
—
Tag:
Add to 
Bookmark Murdok: 
David Utter is a staff writer for Murdok covering technology and business.
