Uberflip uses standard HTTP response status codes to indicate the success or failure of an API request. As a general rule:
2xxrange: Uberflip's servers received, accepted, and executed a request.
4xxrange: Uberflip's servers were unable to accept the request due to an error in the information provided (most commonly an invalid or missing parameter).
5xxrange: Uberflip's servers received and accepted the request, but an error occurred that prevented the request from being executed.
The request was successful.
The request was successful (only used when creating a new resource).
The request was successful, and there is no additional content to be displayed.
The request could not be accepted, usually due to being malformed.
The request could not be accepted, because no valid API credentials or access token were provided.
The request is not allowed.
The requested resource does not exist.
The requested resources does not accept the method that was used.
The request has timed out and did not complete.
The requested resource does not accept the
The request failed because you have made too many requests to the API, exceeding the rate limit.
Something went wrong on Uberflip's end.
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.