API Documentation

Mobypicture has a REST based API, with the most used functions on the website. The API is in active development, if you have any comment, feedback or feature-request. Please contact us or leave a comment.

API-calls are HTTP-requests made to http://api.mobypicture.com or to https://api.mobypicture.com (SSL).

To use the API you have to get a developer key. This also allows you to promote your mobypicture enabled app on the mobypicture website.

API 2.0

This is currently the preferred API for uploading content to Mobypicture. It is compatible with most media providers, like twitpic and yfrog.

Available methods

Error codes

The 2.0 API uses HTTP Codes to provide feedback about errors. Only successful calls return a 200 OK header, calls which can’t be authenticates return a 401 error code, etcetera. Additional explanation is given in JSON or XML.

API 1.0

our current and most complete API. Built to be simple in use and extensive in features. Almost everything you can do on our website is available in our API, from registering new users to add and retrieve comments.

Available methods

Error codes

A list of error codes is available. these error codes do not correspond with HTTP Codes and all calls always return a 200 OK header.

Authentication

Other API uses

Besides our REST API there are some other ways to interact with Mobypicture

Rate limits

Only the calls to SearchPosts are currently limited to 5 calls per 10 seconds. A 007 rate limit reached error will be returned.

This page is last updated on February 10, 2011 by

About Mobypicture Developers

Build your own applications on top of Mobypicture, like over 600 others have done before you using our extensive API.

You can find find out more about the usage of the Mobypicture API in the API Documentation. To use the API you have to get a developer key. This also allows you to promote your Mobypicture enabled app on the Mobypicture website.

Get a Mobypicture developer key