Anatomy of an API request
Routers are exposed in Zenoss Resource Manager and Collection Zones via router endpoint URLs. Each router is available at a distinct URL. See the following chart for some common router endpoints:
|Router Name||Router Endpoint URL|
The Content-Type must be set to Application/json
Authorization (a username and password or API key) need to be present in the headers of your API request.
Routers require an
action field to be defined, which is typically the name of the router being leveraged.
When making an API call, the method being invoked needs to be specified in the router request's
Most router methods accept, or even require, other pieces of information. Arguments used by router methods are passed in the
A tid is a temporary transaction ID for a router request.
Example API Request
- Action: DeviceRouter
- Method: addDevice
- deviceName: example-device.zenoss.com
- deviceClass: /Server/Linux
- productionState: 1000
- Tid: 1