Common API Errors
Tenable.io API returns the following HTTP status codes corresponding to errors:
Code | Status | Description |
---|---|---|
400 | Bad Request | Returned if the request fails because the request payload contains incomplete or invalid input. |
401 | Unauthorized | Returned if Tenable.io cannot process the authentication request for any reason, for example, wrong permissions or an invalid API key. |
403 | Forbidden | Returned if you do not have sufficient permissions to access a resource or complete a task. |
404 | Not Found | Returned if the specified resource either does not exist or cannot be retrieved. |
405 | Method Not Allowed | Returned if the method used in the request is not supported for the specified endpoint. |
406 | Not Acceptable | Returned when the header of the request message contains an invalid accept field that is not supported by the endpoint, for example, the accept header field used with the GET /workbenches/export/{file_id}/download endpoint should be application/octet-stream and not application/json . |
409 | Conflict | Returned when Tenable.io encounters a stateful conflict, for example, when attempting to create a user with a username that already exists. |
413 | Payload Too Large | Returned when the request payload content length is greater than the maximum allowed by the service. |
415 | Unsupported Media Type | Returned when the header of the request message contains a Content-Type field that does not match a known resource. |
429 | Rate Limit Exceeded | Returned if you attempt to send too many requests in a specific period of time. For more information, see Rate Limiting. |
500 | Internal Server Error | Returned if an internal server error occurs in Tenable.io. |
501 | Not Implemented | Returned when Tenable.io does not support the functionality required to fulfill the request, for example, when it does not recognize the request method or does not support the method for a resource. |
503 | Service Unavailable | Returned when Tenable.io is not ready to handle the request. Wait a moment and retry your request. |
You can find additional information about the errors by examining the detailed message in the response.
Updated almost 3 years ago