/
Appendix: Common HTTP Status Codes
Appendix: Common HTTP Status Codes
The 2xx range is returned for successful requests.
The 4xx range is returned due to errors made by the requestor. The 5xx range is returned due to server errors.
The following is not an exhaustive list, but representative of the most likely codes returned by the platform.
Common HTTP Status Codes | ||
---|---|---|
Code | Reason | Description |
200 | OK | The request succeeded. |
201 | Created | The server created a new item, for example, a new threat batch. The server will generally return a Location URI in the response header indicating the location of the newly created item. |
204 | No Content | No content needed to be returned from the server, for example, if an entity has been deleted. |
400 | Bad Request | There was an error in the request due to bad syntax. There may be, for example, errors in the query parameters or in the body of the request. Check your syntax against the API documentation. |
401 | Unauthorized | The user has not submitted valid credentials. Make sure you are using the proper API key in your transmission. |
403 | Forbidden | The user does not have access to the requested resource. |
404 | Not Found | The server did not find a resource matching the request URI. |
500 | Internal Server Error | The server encountered an unexpected condition which prevented it from fulfilling the request. |
503 | Service Unavailable | The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. |