REST API Status Codes
Last updated on 23 September, 2022When an unsuccessful request is made, in LogicMonitor REST API v2 and v3, the response body will contain an errorCode field with one of the following codes:
| HTTP Status Code | API v2 & v3 Error Code | Description |
| 202 | 1202 | The request has been accepted for processing, but the processing has not been completed. |
| 400 | 1400 | Bad request (resource cannot be deleted because something else is dependent on it) |
| 401 | 1401 | Authentication failed |
| 403 | 1403 | Authentication succeeded; permission denied. |
| 404 | 1404 | No such resource |
| 409 | 1409 | The resource already exists |
| 412 | 1412 | A precondition was not met (two factor authentication) |
| 413 | 1413 | Request entity too large (the report is too large to generate) |
| 429 | 1429 | Too many requests (exceeded rate limits) |
| 500 | 1500 | Internal error |
Along with a data object, the response body contains a ‘status’ field which should display one of the following codes for v1 of the API:
| Status Code | Description |
| 200 | Success |
| 1201 | The update was partially successful. |
| 600 | The record already exists. |
| 1041 | RBAC issue |
| 1403 | Two-factor authentication is required. |
| 403 | Authentication failure |
| 2403 | User must enable two-factor authentication |
| 3403 | Incorrect password |
| 1001 | Internal error |
| 1007 | Request failed – possibly due to duplicate records |
| 1069, 500 | No such record |
| 1013, 1004, 1015, 1022, 1027, 1033, 1037, 1060, 1058, 1048 | No such Device DataSource, Device Group, Instance Group, DataSource, Instance, Collector, Datapoint, Widget, SDT |
| 1101 | Query timed out |
| 1010 | Device Group was not deleted |
| 1014 | Instance group cannot be created |
| 1301 | Save failed |
| 1074 | Report too large |
| 1073 | Collector is down |
| 1040 | Import DataSource failed |