API Documentation
The Tweetmeme API attempts to conform to the design principles of Representational State Transfer (REST). You’ll find that you can simply change the file extension on most any request to get results in the format of your choice. Tweetmeme presently supports the following data formats: XML, JSON, and PHP
Parameters
Some API methods take optional or requisite parameters. Where applicable, we’ve documented those parameters. Remember to convert to UTF-8 and URL encode parameters that take complex strings. Please note that the page parameter begins at 1, not 0.
Rate Limiting
Clients are allowed 250 requests per 60 minute time period, starting from their first request. Whenever any API call is made, the headers `X-RateLimit-Limit` and `X-RateLimit-Remaining` will be set with the total limit and the number of API calls remaining in the current 60 minute period. If you exceed the rate limit for a particular 60 minute period, all API calls will fail, responding with a 403 Forbidden status code and an error message detailing that you have exceeded your limit, in the format requested. If you are developing an application that requires more frequent requests to the TweetMeme API, please fill in our Whitelist form and we will get back to you.
Error Messages
When the Tweetmeme API returns error messages, it does so in your requested format. For example, an error from an XML method might look like this:
<?xml version="1.0" encoding="UTF-8"?> <result> <status>failure</status> <reason>unknown method</reason> </result>
The API
We have split the API up into 4 sections which correspond to particular features of TweetMeme. Click the links below to view the methods, parameters and expected responses for API calls in that feature set.
We also have a list of libraries you can download to access the API. Check those out here.
(39 votes, average: 4.08 out of 5)