Zenoss

Zenoss API for Collection Zone and Resource Manager

The long-standing Zenoss JSON router API, still documented and supported for Zenoss Cloud Collection Zones and on-premises Zenoss Resource Manager / Service Dynamics. Every call is an HTTP POST of a JSON envelope — {"action": "", "method": "", "data": [...], "tid": } — to a router path under /zport/dmd (for example device_router, events_router, triggers_router). 61 routers are documented, covering devices, events, event classes, triggers, templates, reports, jobs, users, LDAP, SAML IdP, licensing, ZenPacks, impact and vendor-specific surfaces (AWS, Azure, vSphere, Hyper-V, OpenStack, Cisco UCS, EMC Isilon, SMI-S). Collection Zones authenticate with a z-api-key header; Resource Manager uses HTTP Basic. Zenoss states that some of this functionality will be replaced by the newer /v1 API services over time.

Documentation GitHub

Documentation

📖

Documentation

https://docs.zenoss.com/api/background.html

📖

APIReference

https://docs.zenoss.com/api/reference/devicerouter.html

📖

GettingStarted

https://docs.zenoss.com/api/how-to/use-curl.html

📖

Authentication

https://artifacts.apis.io/zenoss/authentication/zenoss-authentication.yml

Other Resources

🔗

Conventions

https://artifacts.apis.io/zenoss/conventions/zenoss-conventions.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/zenoss:zenoss-router-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

aid: zenoss:zenoss-router-api
name: Zenoss API for Collection Zone and Resource Manager
description: 'The long-standing Zenoss JSON router API, still documented and supported for Zenoss Cloud
  Collection Zones and on-premises Zenoss Resource Manager / Service Dynamics. Every call is an HTTP POST
  of a JSON envelope — {"action": "<Router>", "method": "<method>", "data": [...], "tid": <n>} — to a
  router path under /zport/dmd (for example device_router, events_router, triggers_router). 61 routers
  are documented, covering devices, events, event classes, triggers, templates, reports, jobs, users,
  LDAP, SAML IdP, licensing, ZenPacks, impact and vendor-specific surfaces (AWS, Azure, vSphere, Hyper-V,
  OpenStack, Cisco UCS, EMC Isilon, SMI-S). Collection Zones authenticate with a z-api-key header; Resource
  Manager uses HTTP Basic. Zenoss states that some of this functionality will be replaced by the newer
  /v1 API services over time.'
humanURL: https://docs.zenoss.com/api/background.html
baseURL: https://{collection-zone-host}/cz0/zport/dmd
tags:
- Monitoring
- Event Management
- Infrastructure
properties:
- type: Documentation
  url: https://docs.zenoss.com/api/background.html
- type: APIReference
  url: https://docs.zenoss.com/api/reference/devicerouter.html
- type: GettingStarted
  url: https://docs.zenoss.com/api/how-to/use-curl.html
- type: Authentication
  url: authentication/zenoss-authentication.yml
- type: Conventions
  url: conventions/zenoss-conventions.yml