Blellow Developer's Wiki
API

Blellow API v0.5

Basic Concepts

The REST API is relatively similar to the Twitter API with the addition of Blellow’s unique features. Our goal here is to make it easy for application developers to integrate with us.

Dictionary Example

http://twitter.com/statuses/public_timeline.format

Would become

http://api.blellow.com/everyone.format

Where .format can be .rss, .json, or .xml. Depending on feedback we may also add .atom. A format is required, if it is omitted you will receive an html page from the site or an error. At this time you may not request an rss feed with an http accept header.

Authentication

The Blellow API uses http basic authentication, this is easily done with curl’s -u flag, or equivalent options in your programming language of choice. For example the httpauth option to php’s http://us3.php.net/manual/en/function.http-request.php httprequest function.

Rate Limiting

API calls are limited to 10 write operations per 15 minute period, write operations include posting both public and private messages. You must track your own usage as the api calls as Blellow may silently ignore the request or return a 422 Unprocessable Entity error depending on the specific call. Blellow will also continue to implement anti-spam measures, so please do not post messages that appear to be spam especially many similar messages. These messages may be returned with an error or silently ignored depending on the exact limits they hit.

Quick Start

Blellow Concepts and Terms

API Calls

As time progresses, these calls and signatures will grow. These are the available calls as of 6/22/2009

Element Formats

Blellow data is served in a few different formats; xml, rss, and json. Generally rss provides only a summary while xml and json have access to all the relevant data from the blellow database.

Questions?

Check the FAQ then come ask in the Blellow API group.