Skip to content

API Explorer Overview

The API Explorer provides a built-in tool for exploring, testing, and learning the LogicMonitor REST API—without needing API tokens or external tools.

FeatureDescription
Session AuthUses your active LogicMonitor session—no API tokens needed
Endpoint CatalogBrowse all available API endpoints organized by category
Request BuilderBuild and execute requests with guided parameter input
Request HistoryReview past requests and reload them for quick retesting

MethodAction
Welcome ScreenClick API Explorer on the welcome screen
Command PalettePress Ctrl+K and type “API”
New TabClick + and select New API Request
KeyboardPress Cmd+K, M to toggle to API view

Full API Explorer interface showing request builder and response
PanelDescription
Endpoint Catalog (left)Browse and search all available API endpoints by category
Request Builder (center)Method selector, endpoint path, query params, headers, and body
Response Viewer (center-bottom)Formatted API response with multiple view modes
Tools Sidebar (right)Variables, History, Helpers, and Docs tabs

The right sidebar provides four tabs:

TabDescription
VariablesManage reusable environment variables for substitution
HistoryView and reload past API requests
HelpersJSON path helpers to save response values as variables
DocsView endpoint documentation with parameters, schemas, and auto-generated examples

Unlike traditional API tools, you don’t need API tokens:

  1. Log into LogicMonitor in your browser

  2. Open LMDA Composer—it uses your session cookie

  3. All API calls execute with your permissions automatically

The Docs tab in the sidebar provides comprehensive endpoint documentation:

  • Path Parameters — Required path variables with type information and descriptions
  • Query Parameters — Optional query parameters with enum values and constraints
  • Request Body Schema — Nested property details with types, required indicators, and constraints
  • Example Generation — Auto-generated example payloads based on the schema

Select an endpoint from the catalog or enter a path to view its documentation automatically.

The left panel lets you browse the complete LogicMonitor API:

  • Organized by resource category (Devices, Alerts, Settings, etc.)
  • Search across all endpoints by path, method, or description
  • Click an endpoint to load it into the request builder
  • See parameter requirements and example schemas

Build requests with guidance:

  • Method selector (GET, POST, PUT, PATCH, DELETE)
  • Path autocomplete with endpoint suggestions
  • Query parameter and header editors (Form mode)
  • JSON body editor with syntax highlighting (Raw mode)

Responses display in multiple formats:

TabContent
JSONCollapsible, syntax-highlighted JSON tree
RawPlain text response body
HeadersResponse headers with copy functionality
SnippetsGenerated code in cURL, Python, PowerShell, and Groovy

API requests open in tabs just like scripts:

IndicatorMeaning
APITab contains an API request
(dot)Unsaved changes
Request nameAuto-generated from method and path (e.g., “GET /device/devices”)

Work with multiple API requests simultaneously—each in its own tab. Compare responses side by side.


MethodPurpose
GET Retrieve data from the API
POST Create new resources
PUT Replace/update entire resources
PATCH Partial updates to resources
DELETE Remove resources

Test your connection with a simple API call:

  1. Open API Explorer

  2. Method is GET (default)

  3. Enter /setting/version as the endpoint

  4. Click Send Request

  5. View the version response showing your portal’s API version


API calls execute with your user permissions:

  • Only see data you have access to
  • Can only modify resources you can edit
  • Admin endpoints require admin permissions

LogicMonitor applies rate limits to API calls:

  • Standard rate limits apply to all requests
  • Response headers show remaining quota
  • 429 Too Many Requests indicates rate limiting

The status bar shows response timing to help identify slow endpoints.


  • Learning the API — Explore endpoints interactively before writing automation code
  • Quick Operations — Make one-off API calls without building full scripts
  • Debugging — Test specific API calls to troubleshoot integration issues
  • Data Export — Retrieve data for analysis, reporting, or migration