Status and Error Codes
WatchGuard public APIs use HTTP status codes to indicate the success or failure of a request:
| Status Code | Description |
|---|---|
|
200 Success |
The request succeeded. |
|
201 Created |
The request succeeded and the resource was created. |
|
202 Accepted |
The request succeeded and will be processed asynchronously. |
|
204 No Content |
The server processed the request successfully, but did not return a response. |
|
207 Multi-Status |
The response body contains multiple statuses for different parts of a batch or bulk request. |
|
301 Moved Permanently |
The requested resource has a new permanent URI. This and future requests should use the returned URI. |
|
303 See Other |
The response to the request can be found at a different URI with the GET method. |
|
304 Not Modified |
The requested resource has not been modified since the date specified in the request headers. |
|
307 Temporary Redirect |
The requested resource has a temporary URI. |
|
400 Bad Request |
The API does not understand the request because of bad syntax. This could be because:
To resolve this error, make sure that the request matches the expected syntax. |
|
401 Unauthorized |
Authentication failed because credentials are missing or invalid. |
|
403 Forbidden |
The request failed because you do not have permission to perform the action or access the resource. |
|
404 Not Found |
The resource specified in the request does not exist. To resolve this error, make sure that the request includes a valid resource. |
|
405 Method Not Allowed |
The method is not allowed for the resource specified in the request. |
|
406 Not Acceptable |
The resource can only generate content that is not acceptable based on the Accept headers sent in the request. |
|
408 Request Timeout |
The server timed out while it waited for the request. |
|
409 Conflict |
The request could not complete because of a conflict. For example, two clients tried to create the same resource. |
|
410 Gone |
The requested resource no longer exists. |
|
412 Precondition Failed |
A precondition in a request header field failed. For example, the |
|
415 Unsupported Media Type |
The request includes a media type that the server or resource does not support. |
|
423 Locked |
The requested resource is locked. |
|
428 Preconditioned Required |
The server requires the request to be conditional. |
|
429 Too Many Requests |
The request exceeds the quota of allowed API requests for each day. Each day starts at 00:00 UTC. |
|
500 Server Error |
An error occurred on the server. |
For more information about errors related to a specific public API, see the documentation for that API.