Cisco Platforms and Development
Know each platform's entry point
Questions here ask which API, auth scheme, and endpoint family belongs to which Cisco product.
Catalyst Center (formerly DNA Center) exposes an intent API at /dna/intent/api/v1/.... You authenticate by POSTing credentials to /dna/system/api/v1/auth/token, receive a token valid for about one hour, then send it in the X-Auth-Token header. Meraki uses https://api.meraki.com/api/v1 with an X-Cisco-Meraki-API-Key header; the hierarchy is organizations → networks → devices, and it supports action batches (bulk writes in one call) and webhooks for events. Meraki rate limits are low (roughly 5 calls per second per organization), so batch and cache rather than looping.
Webex APIs (webexapis.com/v1) use OAuth 2.0 bearer tokens for people-scoped access or bot tokens, covering rooms, memberships, and messages, with webhooks for incoming events. ACI is programmed through the APIC REST API using distinguished names (DNs like uni/tn-<tenant>/ap-<app>) and MO classes. NSO uses service models and network element drivers to push configuration. Intersight manages compute with a REST API and SDKs. pyATS/Genie is Cisco's Python test framework for parsing device output and validating state.
On-box, IOS XE supports NETCONF (SSH, port 830) and RESTCONF (HTTPS) driven by YANG models, plus SNMP and CLI. DevNet sandboxes provide always-on or reservable lab environments for practice.
Trap: mixing auth styles across platforms (sending a Meraki key as a bearer token), assuming every Cisco API uses the same versioning scheme, or forgetting that tokens expire. Always check the base URL, header name, and token lifetime before writing code.