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 Code


200 OK

The request was successful.

201 Created

The request was successful (only used when creating a new resource).

204 No Content

The request was successful, and there is no additional content to be displayed.

400 Bad Request

The request could not be accepted, usually due to being malformed.

401 Unauthorized

The request could not be accepted, because no valid API credentials or access token were provided.

403 Forbidden

The request is not allowed.

404 Not Found

The requested resource does not exist.

405 Method Not Allowed

The requested resources does not accept the method that was used.

408 Request Timeout

The request has timed out and did not complete.

415 Unsupported Media Type

The requested resource does not accept the content-type that was used.

429 Too Many Requests

The request failed because you have made too many requests to the API, exceeding the rate limit.

500, 502, 503, 504

Something 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.