REST API Developer's Guide


v2 of LogicMonitor's REST API will allow you to programmatically query and manage your LogicMonitor resources: dashboards, devices, reports, websites, alerts, collectors, datasources, SDTs and more. Comprehensive documentation for available resources and methods can be found here: Additional information can be found in the sections below:

General Information about LogicMonitor's REST API:

For general information about LogicMonitor's REST API, including authentication, rate limiting, and versioning information, see this page. Requests will default to v1 of the API, and you can make v2 requests by including a '?v=2' query parameter or by including a 'X-Version:2' header.

v2 Changes:

Compared to v1, v2 has many changes (including non-backwards compatible changes). The following is a list of major differences, but please look at v2 methods and resources for more details:

  • Status codes - In v1 of the API, there were two status codes for a response: HTTP status code (almost always 200), and a different LM status code in the response body. With v2, we're returning one HTTP status code, and we've considerably narrowed the list of possible status codes that will be returned. This change was made to ensure that response codes are as meaningful and actionable as possible.
  • Response body structure - In v1 of the API, successful responses included 'status', 'errmsg', and 'data' objects at the top level of the response. With v2, since the HTTP status now matches the LM status, the contents of 'data' will be returned at the top level for a successful response. A non-successful response will still include error message fields. Note that this does mean that scripts written for v1 of the API and configured to parse API response should be adjusted to reflect this. Here's an example of before and after:
v1 (before):
HTTP 200 
Response Body:
"data": { 
     "name":"Prod Server 1" 
v2 (after):
HTTP 200
Response Body:
     "name":"Prod Server 1"
  • No Basic authentication support - We've removed support for Basic authentication with v2 of the API. We did this to encourage more use of API tokens for authentication, as there are many additional benefits (separation of UI / API access, audit log entries, more secure). 
  • Support for PATCH - v2 includes support for HTTP PATCH for most resources. You may find this useful for updating just one field of a resource, instead of having to use PUT to update the entire resource (all fields).  You can determine whether PATCH is supported for a given resource by checking the documentation here:
  • Filter syntax - Filter query parameter values should be enclosed in double quotes in v2. This change was made to better accommodate filters that include special characters. E.g. GET /device/devices?filter=name:"Prod-Server-123"


Status Codes

Along with a data object, the response body contains a 'status' field which should display one of the following codes for v2 of the API:

Status Code





The request has been accepted for processing, but the processing has not been completed


Bad request (e.g. a resource cannot be deleted because something else is dependent on it)


Authentication failed


Authentication succeeded; Permission denied


No such resource


The resource already exists


A precondition was not met (e.g. two factor authentication)


Request entity too large (e.g. the report is too large to be generated)


Too many requests (exceeded rate limits)


Internal error