generated: '2026-08-19'
method: probed
source: https://developer.cisco.com/docs/support-apis/application-registration/
description: >-
  Cisco does not publish a sandbox, test mode, test tenant or set of test values for
  the Support APIs. There is no test-vs-live key distinction — a client credential is
  either entitled against real customer support data or it does not work at all.
  The Cisco API Console does carry an "Interactive APIs" tab, which is the only
  try-it surface, and it is behind the same sign-in as the contracts: the console
  returns HTTP 403 to an anonymous client. No `Sandbox` pointer is wired into
  apis.yml, because nothing here is reachable without an entitled account.
sandbox_published: false
test_mode: false
test_credentials: false
test_values_published: false
try_it_console:
  name: Cisco API Console — Interactive APIs
  url: https://apiconsole.cisco.com/
  status_anonymous: 403
  requires: >-
    A Cisco.com account granted Support API access by an SNTC Delegated
    Administrator, or an onboarded PSS partner account.
  source_quote: >-
    "Once signed in, the Cisco API Console has three main tabs towards the top" —
    Documentation, Interactive APIs, My Apps & Keys.
sample_values_in_docs:
  note: >-
    The reference pages and the first-party Postman collection do carry real example
    identifiers (PID WS-C2960-8TC-S, serial FOC10220LK9, bug CSCtb58779, release
    12.2(44)SE6, MDF ID 282202801). They are illustrative inputs against production
    data, not sandbox fixtures.
  postman_environment: postman/cisco-support-apis-postman-environment.json
evidence:
  - url: https://apiconsole.cisco.com/files/SN2INFO_v2.wadl
    status: 403
  - url: https://apix.cisco.com/sn2info/v2/coverage/status/serial_numbers/FOC10220LK9
    status: 403