8/7/2019 Babbl API - V2 - Statuses (A Twitter Client using OAuth Echo)

http://slidepdf.com/reader/full/babbl-api-v2-statuses-a-twitter-client-using-oauth-echo 1/3

Babbl.me API Documentation - v2 - statuses

Description

The Babbl API can be used by Twitter clients to upload a long post to Babbl, and receive a tweet-sized

message with a link to the complete post. In addition, the response includes data points such as thedate created, and the Twitter user ID and screen name for confirmation.

Babbl uses OAuth Echo to ensure valid requests from Twitter clients. More information on OAuth Echo

and Twitter is located at http://dev.twitter .com/pages/oauth_ echo  .

The Update method will return a 200 if successful. If unsuccessful, it will pass either the return value

received from Twitter, or a custom value from Babbl indicating the error.

To use the Babbl API you must have an API key. To obtain your API key, email dave@babbl.me  .

URL

http://babbl.me/2/statuses/update. format 

Available Formats

xml, json

HTTP Method

POST

Headers

X-Verify-Credentials-Authorization (Required)

Example (using sample values from http://dev.twitter.com/pages/auth)

OAuth realm="http://api.twitter.com/",

oauth_consumer_key="GDdmIQH6jhtmLUypg82g",

oauth_signature_method="HMAC-SHA1",

oauth_token="819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw",

oauth_timestamp="1272325550",

oauth_nonce="oElnnMTQIZvqvlfXM56aBLAf5noGD0AQR3Fmi7Q6Y",oauth_version="1.0",

oauth_signature="yOahq5m0YjDDjfjxHaXEsW9D%2BX0%3D"

X-Auth-Service-Provider (Required; must be the value below)

https://api.twitter.com/1/account/verify_credentials.xml

8/7/2019 Babbl API - V2 - Statuses (A Twitter Client using OAuth Echo)

http://slidepdf.com/reader/full/babbl-api-v2-statuses-a-twitter-client-using-oauth-echo 2/3

Parameters

key (Required): Your API Key.

status (Required): The long tweet. Must be URL encoded.

Responses

If you receive a HTTP 200 OK header with an XML or JSON body, the message has been uploaded to

Babbl successfully. A 200 response with no body means the tweet was less than or equal to 140

characters and did not need to be shortened.

400 Could be due to several factors; check the StatusDescription for more information.

403 Typically due to a bad API key; check the StatusDescription for more information.

Other responses from Twitter will be passed back to the caller as-is.

Samples

The following link was created via the API. Sample output from that API call is below. Please note the

new tweet is URL encoded.

http://babbl.me/wcvrq 

Sample XML Response

<status>

<created_at>Sun Mar 06 19:11:01 +0000 2011</created_at><id>wcvrq</id>

<text>This+is+a+sample+long+message+that+was+shortened+using+Babbl.me

.+You+can+type+in+as+much+as+you+want%2c+and+...+http%3a%2f 

%2fbabbl.me%2fwcvrq</text>

<user>

<id>222539314</id>

<screen_name>babbl_me</screen_name>

</user>

</status>

Sample JSON Response

{

created_at: 'Sun Mar 06 19:04:58 +0000 2011',

id: 'wcvrq',

text: 'This+is+a+sample+long+message+that+was+shortened+using+Babbl.me.

+You+can+type+in+as+much+as+you+want%2c+and+...+http%3a%2f%2fbabbl.me

%2fwcvrq',

8/7/2019 Babbl API - V2 - Statuses (A Twitter Client using OAuth Echo)

http://slidepdf.com/reader/full/babbl-api-v2-statuses-a-twitter-client-using-oauth-echo 3/3

user: {

id: 222539314,

screen_name: 'babbl_me'

}

}