Author Archive

The AdSense API is a free beta SOAP service that allows you to directly integrate AdSense into your service offerings. Targeted towards websites that offer services like web hosting, web publishing, social networking and blogging, the AdSense API allows your users to participate in the AdSense program without leaving your website. You can help monetize your users' web content on your website and tailor your AdSense offerings to the user by customizing the ad formats, placement, colors, and more. The AdSense API also offers AdSense for Search and AdSense Referrals integration in addition to reports that will allow your users to view their ad performance and earnings generated from their web pages.



By offering AdSense to your users, you will also receive a share of the revenue when users choose to add AdSense to their hosted content. Integrating with the AdSense API is easy. If you own a site in which you register users who manage web content, and your site has more than 100,000 daily pageviews, you may qualify for participation in the AdSense API (BETA). If you'd like to participate, apply to be a developer. Once you're approved, just download the AdSense API WSDLs and the SOAP toolkit in the programming language of your choice and start making money for yourself and for your users with the AdSense program.

Jon Udell at InfoWorld has been tinkering with the first GData API (Google Calendar's), check out what he has to say:

"Along with HTTP Basic, Digest, and a couple of others, this Python HTTP library [httplib2] will now handle Google-style authentication. That's really the only tricky thing about using Google Calendar's API. Everything else is URLs and Atom entries. There are Java and C# wrappers for this stuff, but I'm having a ball just using Python's interactive mode to explore the Calendar API. Among the things I can easily do: search for entries matching dentist, search for entries after June 10, receive the results of any query as an Atom or RSS feed..."



"Most discussion of Gcal has (appropriately) focused on its user interface, which puts many a conventional fat client to shame in terms of both its responsiveness and its ease of use. From my perspective, though, what matters equally is an API that's powerful, flexible, and easy to use."

The Google Desktop Team just announced a Google Desktop Gadget Contest! The Desktop blog has the details, but here are a few highlights:

• The contest runs through July 31 (winners will be announced August 21)
• Everyone who submits a published Gadget will get a limited edition Google Desktop Developer T-shirt (there are other Google-y prizes too)
• Top prizes: $5,000 for 1st place, $2,000 for 2nd place, and $1,000 for 3rd place
• Primary judging criteria: popularity, visual appeal, use of new features (such as transparency/animation, Google Talk API integration, personalization, etc.)

And be sure to check out the Google Desktop Gadget Designer, a new IDE and WYSIWYG UI creator for making Google Desktop Gadgets.

Google Checkout, our recently unveiled checkout option, has an API that exposes sophisticated functionality and programmatic interaction via XML over HTTP. Once you've created a sandbox account, the Checkout API's equivalent of "Hello World" is quite easy using cURL:



curl -d '' https://:\

@sandbox.google.com/cws/v2\

/Merchant//request



When you're ready to start integrating with the Google Checkout API, read through the Developer's Guide, Sample Code and Developer's Cookbook (for implementation-focused articles), and connect with other API developers in the Developer's Forum.

Google engineer Mihai Parparita's latest Maps mashup is just too nifty not to mention here on Code: Overheard in NY + Maps' API + Reader = Overplot



His blog post explains a few of the specific problems he encountered while creating it:

• "The most basic issue with implementing this is geocoding all of the location strings (like "Canal & Broadway") to a latitude/longitude pair... It is not perfect, but since the set of addresses is pretty tightly constrained, I was able to add some rewriting rules to make the input more easily parsed. As of right now, 54% of the addresses are geocoded."
• "I didn't want to directly scrape the HTML of the site to extract all of the quotes. I ended up using the data stored in Google Reader's archive of the site's feed. This allowed me to get at the quotes themselves more easily, without having to worry about the chrome of the site."
• "Instead of each marker being its own overlay, I put all of them in the same overlay (see the QuotesOverlay class). Additionally, I did not split each marker into several layers (shadow, image, click area) - having the shadow be part of the image works well enough."

Read more at persistent.info.