REST API status codes
The Skytap REST API uses HTTP standards for error and status reporting. This table contains some of the more common HTTP codes that you may encounter when using the API.
Skytap may also display additional information in the response body.
| HTTP code | Description |
|---|---|
| 200 | Success |
| 302 | URL redirection |
| 401 | Unauthorized – Authentication is required and has failed, or authorization hasn’t been provided |
| 404 | Not found – Resource can’t be found, may be available in the future. |
| 406 | Not Acceptable – Request succeeded but couldn’t generate a response that matches the content type in the Accept header. |
| 409 | Conflict – Request is well-formed but conflicts with another resource or permission. |
| 422 | Invalid parameter – Request well-formed but contained semantic errors. Also used to indicate that a runstate change was attempted on a busy resource. |
| 423 | Resource is busy; please wait and try your request again shortly. – For more information, see API best practices: Checking for busyness. |
| 429 | Too many HTTP requests in a given period of time. – For more information, see API best practices: Checking for busyness. |
| 500 | System error – Given when no specific error message is available. |
For more information on the full range of HTTP status codes, see the Wikipedia List of HTTP status codes.