Caution: The documentation you are viewing is
for an older version of Zend Framework.
You can find the documentation of the current version at:
Zend_Service_Technorati - Zend_Service
Zend_Service_Technorati provides an easy, intuitive and object-oriented interface for using the Technorati API. It provides access to all available » Technorati API queries and returns the original XML response as a friendly PHP object.
» Technorati is one of the most popular blog search engines. The API interface enables developers to retrieve information about a specific blog, search blogs matching a single tag or phrase and get information about a specific author (blogger). For a full list of available queries please see the » Technorati API documentation or the Available Technorati queries section of this document.
Note: API Key limits
You can make up to 500 Technorati API calls per day, at no charge. Other usage limitations may apply, depending on the current Technorati API license.
Once you have a valid API key, you're ready to start using Zend_Service_Technorati.
In order to run a query, first you need a Zend_Service_Technorati instance with a valid API key. Then choose one of the available query methods, and call it providing required arguments.
Example #1 Sending your first query
Each query method accepts an array of optional parameters that can be used to refine your query.
Example #2 Refining your query
A Zend_Service_Technorati instance is not a single-use object. That is, you don't need to create a new instance for each query call; simply use your current Zend_Service_Technorati object as long as you need it.
Example #3 Sending multiple queries with the same Zend_Service_Technorati instance
You can get one of two types of result object in response to a query.
The first group is represented by
Zend_Service_Technorati_*ResultSet objects. A result set object
is basically a collection of result objects. It extends the basic
Zend_Service_Technorati_ResultSet class and implements the
SeekableIterator PHP interface. The best way to consume
a result set object is to loop over it with the PHP
Example #4 Consuming a result set object
Because Zend_Service_Technorati_ResultSet implements the
SeekableIterator interface, you can seek a specific result object using its
position in the result collection.
Example #5 Seeking a specific result set object
SeekableIteratorworks as an array and counts positions starting from index 0. Fetching position number 1 means getting the second result in the collection.
The second group is represented by special standalone result objects. Zend_Service_Technorati_GetInfoResult, Zend_Service_Technorati_BlogInfoResult and Zend_Service_Technorati_KeyInfoResult act as wrappers for additional objects, such as Zend_Service_Technorati_Author and Zend_Service_Technorati_Weblog.
Example #6 Consuming a standalone result object
Please read the Zend_Service_Technorati Classes section for further details about response classes.
Each Zend_Service_Technorati query method throws a Zend_Service_Technorati_Exception exception on failure with a meaningful error message.
There are several reasons that may cause a Zend_Service_Technorati query to fail. Zend_Service_Technorati validates all parameters for any query request. If a parameter is invalid or it contains an invalid value, a new Zend_Service_Technorati_Exception exception is thrown. Additionally, the Technorati API interface could be temporally unavailable, or it could return a response that is not well formed.
You should always wrap a Technorati query with a
Example #7 Handling a Query Exception
From time to time you probably will want to check your API key daily usage. By default Technorati limits your API usage to 500 calls per day, and an exception is returned by Zend_Service_Technorati if you try to use it beyond this limit. You can get information about your API key usage using the Zend_Service_Technorati::keyInfo() method.
Zend_Service_Technorati::keyInfo() returns a Zend_Service_Technorati_KeyInfoResult object. For full details please see the » API reference guide.
Zend_Service_Technorati provides support for the following queries:
» Cosmos query lets you see what blogs are linking to a given URL. It returns a Zend_Service_Technorati_CosmosResultSet object. For full details please see Zend_Service_Technorati::cosmos() in the » API reference guide.
Example #9 Cosmos Query
The » Search query lets you see what blogs contain a given search string. It returns a Zend_Service_Technorati_SearchResultSet object. For full details please see Zend_Service_Technorati::search() in the » API reference guide.
Example #10 Search Query
The » Tag query lets you see what posts are associated with a given tag. It returns a Zend_Service_Technorati_TagResultSet object. For full details please see Zend_Service_Technorati::tag() in the » API reference guide.
Example #11 Tag Query
The » DailyCounts query provides daily counts of posts containing the queried keyword. It returns a Zend_Service_Technorati_DailyCountsResultSet object. For full details please see Zend_Service_Technorati::dailyCounts() in the » API reference guide.
The » BlogInfo query provides information on what blog, if any, is associated with a given URL. It returns a Zend_Service_Technorati_BlogInfoResult object. For full details please see Zend_Service_Technorati::blogInfo() in the » API reference guide.
Example #14 BlogInfo Query
The » GetInfo query tells you things that Technorati knows about a member. It returns a Zend_Service_Technorati_GetInfoResult object. For full details please see Zend_Service_Technorati::getInfo() in the » API reference guide.
Example #16 GetInfo Query
The following classes are returned by the various Technorati queries. Each
Zend_Service_Technorati_*ResultSet class holds a type-specific
result set which can be easily iterated, with each result being contained in a type
result object. All result set classes extend
Zend_Service_Technorati_ResultSet class and implement the
SeekableIterator interface, allowing for easy iteration and seeking to a
Note: Zend_Service_Technorati_GetInfoResult, Zend_Service_Technorati_BlogInfoResult and Zend_Service_Technorati_KeyInfoResult represent exceptions to the above because they don't belong to a result set and they don't implement any interface. They represent a single response object and they act as a wrapper for additional Zend_Service_Technorati objects, such as Zend_Service_Technorati_Author and Zend_Service_Technorati_Weblog.
The Zend_Service_Technorati library includes additional convenient classes representing specific response objects. Zend_Service_Technorati_Author represents a single Technorati account, also known as a blog author or blogger. Zend_Service_Technorati_Weblog represents a single weblog object, along with all specific weblog properties such as feed URLs or blog name. For full details please see Zend_Service_Technorati in the » API reference guide.
Zend_Service_Technorati_ResultSet is the most essential result set. The scope of this class is to be extended by a query-specific child result set class, and it should never be used to initialize a standalone object. Each of the specific result sets represents a collection of query-specific Zend_Service_Technorati_Result objects.
Zend_Service_Technorati_ResultSet implements the
SeekableIterator interface, and you can iterate
all result objects via the PHP
Example #17 Iterating result objects from a resultset collection
Zend_Service_Technorati_CosmosResultSet represents a Technorati Cosmos query result set.
Note: Zend_Service_Technorati_CosmosResultSet extends Zend_Service_Technorati_ResultSet.
Zend_Service_Technorati_SearchResultSet represents a Technorati Search query result set.
Note: Zend_Service_Technorati_SearchResultSet extends Zend_Service_Technorati_ResultSet.
Zend_Service_Technorati_TagResultSet represents a Technorati Tag query result set.
Note: Zend_Service_Technorati_TagResultSet extends Zend_Service_Technorati_ResultSet.
Zend_Service_Technorati_DailyCountsResultSet represents a Technorati DailyCounts query result set.
Note: Zend_Service_Technorati_DailyCountsResultSet extends Zend_Service_Technorati_ResultSet.
Zend_Service_Technorati_Result is the most essential result object. The scope of this class is to be extended by a query specific child result class, and it should never be used to initialize a standalone object.
Zend_Service_Technorati_CosmosResult represents a single Technorati Cosmos query result object. It is never returned as a standalone object, but it always belongs to a valid Zend_Service_Technorati_CosmosResultSet object.
Note: Zend_Service_Technorati_CosmosResult extends Zend_Service_Technorati_Result.
Zend_Service_Technorati_SearchResult represents a single Technorati Search query result object. It is never returned as a standalone object, but it always belongs to a valid Zend_Service_Technorati_SearchResultSet object.
Note: Zend_Service_Technorati_SearchResult extends Zend_Service_Technorati_Result.
Zend_Service_Technorati_TagResult represents a single Technorati Tag query result object. It is never returned as a standalone object, but it always belongs to a valid Zend_Service_Technorati_TagResultSet object.
Note: Zend_Service_Technorati_TagResult extends Zend_Service_Technorati_Result.
Zend_Service_Technorati_DailyCountsResult represents a single Technorati DailyCounts query result object. It is never returned as a standalone object, but it always belongs to a valid Zend_Service_Technorati_DailyCountsResultSet object.
Note: Zend_Service_Technorati_DailyCountsResult extends Zend_Service_Technorati_Result.
Zend_Service_Technorati_GetInfoResult represents a single Technorati GetInfo query result object.
Zend_Service_Technorati_BlogInfoResult represents a single Technorati BlogInfo query result object.
Zend_Service_Technorati_KeyInfoResult represents a single Technorati KeyInfo query result object. It provides information about your Technorati API Key daily usage.