ISE APIs

pxGrid Cloud provides a mechanism for clients on the cloud to consume ERS APIs and Open APIs from Cisco ISE.

ERS and Open APIs: In order to invoke ERS and Open APIs, you need to append the API path to https://<REGIONAL_HOST>/api/dxhub/v2/apiproxy/request/<device_id>/direct/. ERS and Open API URLs start with "/ers" and "/api" respectively. For more details about Cisco ISE APIs, see Cisco ISE API Reference Guide.

pxGrid APIs: Information pertaining to pxGrid API references can be found here. Note that ServiceLookup is not required while accessing pxGrid APIs using pxGrid Cloud. Use the appropriate Regional URL.

Step 1 – Define pxGrid base URL as https://<<REGIONAL_HOST>>/api/dxhub/v2/apiproxy/request/<<device_id>>/direct/pxgrid.

Step 2 – Obtain the mapping keyword for the service required, and append it to the base URL.

pxGrid Service → pxGrid Cloud Service pxGrid Topic → pxGrid Cloud Topic
com.cisco.ise.session → session sessionTopic → sessions
com.cisco.ise.session → session groupTopic → userGroups
com.cisco.ise.config.anc → anc statusTopics → operationStatus
com.cisco.ise.mdm → mdm endpointTopic → endpoints
com.cisco.ise.config.profiler → profiler topic → profiles
com.cisco.ise.radius → radius failureTopic → failures
com.cisco.ise.trustsec → trustsec policyDownloadTopic → policyDownloads
com.cisco.ise.config.trustsec → trustsec securityGroupTopic → securityGroups
com.cisco.ise.config.trustsec → trustsec securityGroupAclTopic → securityGroupAcls
com.cisco.ise.sxp → trustsec bindingTopic → bindings
com.cisco.ise.echo → echo echoTopic → echo

Step 3 – Append the required API end point to the base URL (For example - https:///api/dxhub/v2/apiproxy/request//direct/pxgrid/trustsec/getSecurityGroups).

Note:

  • In case of on-prem connections, you have to perform a ServiceLookup to obtain a restBaseUrl, and then construct the required URL by appending the REST end point. When using pxGrid APIs on pxGrid Cloud, ServiceLookup is not required.