Errors & Validation
This page outlines the different responses to requests and what they mean
Code | Response | Description |
---|---|---|
200 | OK | The request was successful. This is for PUT , PATCH and DELETE requests. |
201 | OK | The request was successfully created. This is for POST requests. |
202 | Accepted | The request has been accepted for processing, but has not yet started or completed. The request will be processed in the background. |
400 | Invalid Input | The server cannot or will not process the request due to an incorrect request. This is typically due to malformed syntax, invalid request message framing, or deceptive request routing. |
401 | Authentication Required | The access token has expired or is no longer valid. Please generate a new access token. |
403 | Forbidden | The server understands the request but cannot allow access. This is typically due to insufficient user access, authentication issues, file permissions, or firewall restrictions. |
404 | Resource Not Found | The origin server was unable or unwilling to find the resource requested. |
442 | Unprocessable Entity | The request structure and syntax is valid, but the data within it is illogical, incomplete or violates expected rules. This is typically due to missing required fields, incorrect data types, or invalid data format. |
500 | Internal Error | The server has encountered an unexpected condition or configuration problem that prevents it from processing the request. Halaxy is always alerted to new errors. |
503 | Service Unavailable | The service is currently unable to handle the request. This is typically due to the server being down for maintenance or overloaded. This may also happen during software updates. |
Updated about 1 month ago