Response status and error codes
When LiSA receives a request to an API endpoint, a number of different HTTP status codes can be returned in the response depending on the original request.
Status Code | Explanation |
|---|---|
200 OK | The request was successfully processed by LiSA. |
201 Created | The request has been fulfilled and a new resource has been created. |
202 Acceted | The request has been accepted, but not yet processed. |
400 Bad Request | The request wasn't understood by the server, generally due to bad syntax or because the Content-Type header wasn't correctly set to application/json. |
401 Unauthorized | The necessary Authentication are not present in the request or are incorrect. |
403 Forbidden | The server is refusing to respond to the request. This status is generally returned if you haven't requested the appropriate scope for this action. |
404 Not Found | The requested resource was not found but could be available again in the future. |
422 Unprocessable Entity | The request body was well-formed but contains semantic errors. A 422 error code can be returned from a variety of scenarios including, but not limited to:
The response body provides details in the error parameters. |
429 Too Many Requests | The request was not accepted because the application has exceeded the rate limit. Learn more about LiSA Rate limits |
500 Internal Server Error | An internal error occurred in a LiSA service. |
503 Service Unavailable | The server is currently unavailable. |
504 Gateway Timeout | The request could not complete in time. LiSA waits up to 15 seconds for a response. |
