Error codes

The error codes correspond to the HTTP status codes and are sent as  a HTTP status code, as well as a XML/JSON response. The XML/JSON response always describes the exact reason of failure.

200
– Success!

400
– Bad request, you did something wrong. Have a look at the response for an exact description.

401
– Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided.

403
– The request was a legal request, but the API is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.

404
– The requested API method could not be found.

418
– Somehow you reached our teapot. The responding entity may be short and stout.

500
– A generic error message, given when no more specific message is suitable. A.k.a. we screwed up. Have a look at the response for an exact description.

503
– The API is currently unavailable (because it is overloaded or down for maintenance). This is a temporary state. have a look at our Status page for more info.

This page is last updated on May 28, 2010 by

Comment Form

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

RSS Mobypicture product news

  • We won in court. Sort of. August 31, 2017
    This guy, Bram Gorissen took us to trial over a picture. He said he was sueing many blogs and platforms for supposed infringement of his copyright. He took a picture of a train in 2011, posted the picture on a popular Dutch forum, fok.nl. "As a courtesy to the owner of that platform" who is […]
  • Do you remember all of these? August 15, 2017
  • Supporting Bas support two great initiatives July 10, 2017
    I met Bas at the beginning of this year at an IPAN event. It was the first event where I spoke about Kinder.