The Cisco Catalyst Center Intent API is a northbound API that allows external systems, applications, and automation workflows to interact with Catalyst Center at an abstracted intent level. It is not primarily a device-by-device command interface. The purpose of an intent-based platform is to let administrators or applications express the desired business or network outcome, while the controller translates that intent into the required operational changes, workflows, and device-level configurations. That makes “northbound API” and “business outcome oriented” the correct selections. “Procedural” is incorrect because procedural automation describes step-by-step instructions, while an intent API focuses on the desired result. “Device-oriented” is also wrong because device-level control is normally handled through southbound mechanisms or lower-level APIs and protocols. “Southbound API” is incorrect because southbound communication is controller-to-device communication, while the Intent API is used above the controller by applications and integrations. The ENCOR automation concept is that Catalyst Center exposes intent-based RESTful northbound APIs for network discovery, assurance, provisioning, and policy workflows. References/topics: ENCOR Automation, Cisco Catalyst Center, Intent API, northbound APIs, intent-based networking, controller abstraction.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit