Error Handling

UMVA API Error Handling

The UMVA API uses HTTP status codes to indicate the success or failure of API requests. Below is a summary of these codes and what they mean in our context.

Summary:

  • Codes in the 2XX range mean that the API request was processed successfully.
  • Codes in the 4XX range mean that something was wrong with the data that you sent, such as missing required parameters or using incorrect API credentials.
  • Codes in the 5XX range indicate an error in processing on UMVA’s end.

Common HTTP Codes:

Code Description
200 OK - Request was successful
202 Accepted - Request has been accepted and acknowledged. We will process the request and notify you of the status afterwards.
400 Bad Request - Malformed request or missing required parameters
401 Unauthorized - Missing required headers, wrong Public or Secret Key, etc.
403 Forbidden - You are trying to access a resource for which you don't have proper access rights.
404 Not Found - You are trying to access a resource that does not exist
422 Unprocessable Entity - All required parameters were provided, but they are not valid for the request
500 Internal Server Error - There was a glitch on our servers. Retry the request later or contact support
503 Service Unavailable - Temporarily offline for maintenance. Please try again later