/api/space/opennms/requisitions

A requisition is a group of nodes. OpenNMS APIs allows you to manage the provisioning of requisitions. Requisitions allow you to monitor services in the network. They track status of network devices. You can get information about the pending or deployed requisitions using a GET operation on "active" requisitions.

For more information about referencing a Space device ID as a foreign source and ID pair within OpenNMS APIs, see the "Mapping Space Device IDs to OpenNMS Node IDs" section of the Fault and Performance APIs topic.

The following operations are supported on this resource:

  • GET - Get all active requisitions.
GET /requisitions Version 1

This API is used to retrieve information about all the active requisitions.

Sample Usage

GET /requisitions


  • Accept Headers:
    application/vnd.net.juniper.space.opennms+xml;version=1

  • Sample Output XML:

    <requisitions count="1" totalCount="1">
       <model-import date-stamp="2017-02-06T11:34:18.032Z" foreign-source="space" last-import="2017-02-06T11:34:18.176Z">
          <node foreign-id="5832730" node-label="AD_Scale11_1" devicePlatform="EX9208">
             <interface descr="mgmt0" ip-addr="10.20.175.1" status="1" snmp-primary="P">
                <monitored-service service-name="ICMP" />
                <monitored-service service-name="SNMP" />
             </interface>
             <category name="Routers" />
             <category name="Medium" />
             <category name="_Global" />
             <category name="Monitor_SNMP" />
          </node>
          <node foreign-id="6783002" node-label="elite2-qfx" devicePlatform="QFX10002-36Q">
             <interface descr="mgmt0" ip-addr="192.168.27.181" status="1" snmp-primary="P">
                <monitored-service service-name="ICMP" />
                <monitored-service service-name="SNMP" />
             </interface>
             <category name="Switches" />
             <category name="Medium" />
             <category name="_Global" />
             <category name="Monitor_SNMP" />
          </node>
       </model-import>
    </requisitions>

  • Access Control

    The following capabilities are required to access this API: cap_fmpm_Alarm