Error codes
ESET Connect API uses the following sub-set of error codes:
OAuth Service
Error code |
Reason |
Returned message |
---|---|---|
202 |
The response query takes longer than 50 seconds, and the query has been cached. See the pending response behavior. |
Accepted |
4xx |
•empty request data •null/empty/invalid grant_type •null/empty client_id •null/empty client_secret |
•invalid credentials •invalid token |
404 |
The response cache has been cleared. See the pending response behavior. |
Not Found |
415 |
Request data is not form content type |
|
500 |
Unknown internal error (stack trace is present in log message) |
|
503 |
IDS returns empty response |
|
504 |
Response timeout—after more than 180 seconds. See the pending response behavior. |
Timeout |
xxx |
when IDS returns unsuccessful response (HTTP code is copied from the IDS response) |
|
Domain services, connectors
Error code |
Explanation |
---|---|
HTTP 403 |
All user errors |
HTTP 500 |
All backend-side errors |
Status codes used in logs
Error code |
Explanation |
---|---|
0 (OK) |
|
3 (InvalidArgument) |
invalid access token |
7 (PermissionDenied) |
API not enabled for token |
8 (ResourceExhausted) |
access token expired |
13 (Internal) |
unspecified error |
14 (Unavailable) |
error from IDS |
16 (Unauthenticated) |
token validation failed |