Uberflip uses standard HTTP response status codes to indicate the success or failure of an API request. As a general rule:

  • 2xx range: Uberflip's servers received, accepted, and executed a request.
  • 4xx range: Uberflip's servers were unable to accept the request due to an error in the information provided (most commonly an invalid or missing parameter).
  • 5xx range: Uberflip's servers received and accepted the request, but an error occurred that prevented the request from being executed.

HTTP Status Codes

Status CodeMeaning
200 OKThe request was successful.
201 CreatedThe request was successful (only used when creating a new resource).
204 No ContentThe request was successful, and there is no additional content to be displayed.
400 Bad RequestThe request could not be accepted, usually due to being malformed.
401 UnauthorizedThe request could not be accepted, because no valid API credentials or access token were provided.
403 ForbiddenThe request is not allowed.
404 Not FoundThe requested resource does not exist.
405 Method Not AllowedThe requested resources does not accept the method that was used.
408 Request TimeoutThe request has timed out and did not complete.
415 Unsupported Media TypeThe requested resource does not accept the content-type that was used.
429 Too Many RequestsThe request failed because you have made too many requests to the API, exceeding the rate limit.
500, 502, 503, 504Something went wrong on Uberflip's end.


Handling Errors

The Uberflip API can return errors for various reasons, such as invalid parameters, authentication problems, or network issues. As a result, you should write your code to gracefully handle all possible API exceptions.