On the GoodPHPTutorials.com website there's a new tutorial showing how to get the Authorize.net API to talk back and forth between it and your application.

I have taken the time to abstract the AIM API into my own class that not only simplifies the code we will need to work with that API but also makes it modular and easy to port from application to application. To begin you will need to download the AuthnetAIM class. You can find it here.

He walks you through the setup and configuration of the library and includes a few examples of how to make both simple and more complex transactions through it.

Padraic Brady has posted about a new inclusion that Google has announced will be included in the authentication methods for their APIs - OAuth.

The Google Data API support comes with a few gotchas. Its documentation show a clear preference for using GET instead of POST, though the Google OAuth server does appear to natively support POST requests for everything with the exception that it has a small bug which interprets an empty POST request body as a sort of phantom empty parameter.

He notes that the library he's been working on (and submitted to both the Zend Framework and PEAR) it up to the 0.0.3 release including functionality marked as beta for the Consumer portion.

A new tutorial over on the IBM developerWorks site (from Vikram Vaswani) shows how to pull data from the Google Notebook service into your script via the service's REST API.

Google Notebook is a free service that allows users to save and share notes and Web clippings in an online journal. A REST-based API allows developers to build customized PHP applications around this service using SimpleXML. In this article, you learn how to use the API, with examples of reading notebooks and notebook contents using PHP.

His method grabs the contents of the REST request and drops them into a SimpleXML object for easy manipulation. Different kinds of requests are included - getting the list of notebooks, getting the notebook's contents and how to add on extra parameters to the REST call to get more information in the responses.

In this new tutorial on the IBM developerWorks website, they show you how - with a little simple HTML and PHP - to integrate functionality from the YouTube API into your site.

The YouTube video sharing site allows Web application developers to access public content through its REST-based developer API. [...] This article introduces the YouTube Data API, demonstrates how you can use it to browse user-generated video content; access video metadata, comments and responses; and perform keyword searches.

They help you get started by outlining the format that the YouTube messages use (Atom feeds) and how to run a query against the API and return back the custom data for things like video categories, popularity and the results of keyword searches.

On his blog, Andreas Gohr has posted about various charting applications on the web (in his search for a way to show off the stats for DokuWiki) and looking specifically at the Google Charts.

Because such [popularity] data is much better to comprehend when accompanied by some nice graphs, I had a look at the Google Chart API today.

He also mentions three wrapper libraries that help your apps interface with the Charts API. Of course, he also includes some graphs of the popularity stats showing things like web server usage and PHP versions.

Hasin Hayder has proposed an interesting replacement for the usual caching mechanism - using the Facebook data storage API to cache copies of pages/data/etc.

Why not! All you need is a fast-n-furious caching storage for your Facebook application which stores values against a key, same like a hash table. Facebook data storage API does the same for you. using the batch API in Facebook rest client you can seriously think it as an alternative of memcache.

He shows the simple process for making the object (manually in a preexisting application), inserting data into the object through the API they provide and how to pull that data back out.

On the Developer Tutorials site today, Akash Mehta has posted his look at having search functionality on your website.

Today's websites have a lot of content. [...] Needless to say, effectively searching all that data can be a real challenge, and chances are at the end of the day you'll still be stuck with a slow and ineffective search system. [...] Implementing effective search doesn't have to be hard. In this tutorial, I'll show you how to build a basic site-specific web search in just five lines of code, using the Yahoo! APIs.

He includes a (very) brief look at the search API Yahoo! offers followed by examples of queries and then on to the real deal, a search system that takes in a user query and asks the Yahoo! API for results matching it. The results are outputted below the box.

In a new post, Greg Beaver talks about a few things, the main one being a new release of the phar extension he's made - phar version 2.0.0a1 - a reworking of the previous functionality with loads of new features including:

• Phar now supports tar and zip archives with the same API that is supports phar archives.
• Phar has a front controller for web applications that fully handles MIME types, supports mod_rewrite-like functionality with far more flexibility
• Phar supports phar:// stream wrappers in include_path for PHP 5.2+
• Phar supports creation and modification of data-only tar and zip archives (no executable phar stub) via the PharData class.

There've also been updates to the manual for the project to reflect this new version of its API. You can download this latest version here: source or Windows DLL.

Hasin Hayder has posted an example of a "world time search" he's worked up that uses the geonames.org and Yahoo! developer APIs to pin down the time at any given location.

I recently came by this site WorldTimeEngine where users can search the local time of any place using the name, street address or just latitude and longitude. Since that time I was thinking how easily you can make your own. As long there are some good people over there (For Geocoding API) - its a not a big deal, you know?

His script pulls the location of the place (latitude/longitude) from the Yahoo! geocoding API and passes that back into the geonames web service to get the local time. The result is an array with the lat/long, address you submitted and the time output in a standard string.

In a quick new blog post to the NorthClick blog, Soenke Ruempler points out that, due to some updates made by Rob Richards, the Spread extension for PECL is back in working order again.

Yesterday I got an e-mail that two of my PECL bug reports for the spread module have been fixed. It seems that it gets some recent love from Rob Richards who commited some fixes and cleanups.

The Spread functionality allows developers to create messaging services by acting as a message bus between the clients and between the client/servers.