Cisco Catalyst Center Energy API

openapi: 3.2.0
info:
  title: Cisco Catalyst Center Energy API
  version: 1.0.1
  contact:
    name: Cisco TAC World Wide
    url: https://www.cisco.com/c/en/us/support/web/tsd-cisco-worldwide-contacts.html
    email: tac@cisco.com
  license:
    name: Cisco Catalyst Center License
    url: https://www.cisco.com/c/en/us/products/collateral/software/dna-software-ebook-cte.html
  termsOfService: https://www.cisco.com/c/en/us/about/legal/cloud-and-software/end_user_license_agreement.html
  description: 'Operations tagged energy across 2 of this provider''s published API definitions: cisco-catalyst-center-device-energy-openapi.yml,
    cisco-catalyst-center-sites-energy-openapi.yml. Each path carries the servers of the definition it was published in.'
  x-provenance:
    method: harvested
    authored_by: Cisco Catalyst Center
    harvested_by: API Evangelist
    harvested_on: '2026-08-19'
    first_party: true
    provider_published: true
    source_host: developer.cisco.com
    note: 27 Cisco-published OpenAPI 3.0 Assurance documents (185 operations). Ownership confirmed from the tac@cisco.com
      contact, the Cisco EULA terms-of-service URL and the Cisco Catalyst Center license block carried in each document.
    derived_view: Per-tag view of cisco-catalyst-center-device-energy-openapi.yml, the provider's source document. Operations
      and schemas are the provider's, unmodified; only the partition is ours.
    derived_from: cisco-catalyst-center-device-energy-openapi.yml
    operation_coverage: 12/19
  x-evidence:
  - type: source
    url: https://developer.cisco.com/docs/catalyst-center/
  - type: source
    url: https://developer.cisco.com/dnacenter/
servers:
- url: https://developer.cisco.com/data/api/v1
tags:
- name: energy
  description: Operations related to retrieving overall energy information for Catalyst Center Devices
  externalDocs:
    description: Catalyst Center Assurance user guide
    url: https://www.cisco.com/c/en/us/support/cloud-systems-management/dna-center/products-user-guide-list.html
paths:
  /data/api/v1/energy/networkDevices:
    get:
      tags:
      - energy
      summary: Get devices energy
      description: Retrieves a list of network devices with energy data based on the specified query parameters. It returns
        the most recent snapshot of energy data within the provided start and end times. If no start and end times are specified,
        it defaults to returning the latest available energy data from the past 24 hours.
      operationId: readNetworkDevicesEnergy
      parameters:
      - name: startTime
        in: query
        description: 'Start time from which API queries the data set related to the resource. It must be specified in UNIX
          epochtime in milliseconds. Value is inclusive.


          If `startTime` is not provided, API will default to one day before `endTime`.

          '
        required: false
        style: form
        explode: true
        schema:
          type: integer
          format: int64
        example: 1705348800000
      - name: endTime
        in: query
        description: 'End time to which API queries the data set related to the resource. It must be specified in UNIX epochtime
          in milliseconds. Value is inclusive.


          If `endTime` is not provided, API will default to one day after `startTime`. If `startTime` is not provided either,
          API will default to current time.

          '
        required: false
        style: form
        explode: true
        schema:
          type: integer
          format: int64
        example: 1705435200000
      - name: limit
        in: query
        description: Maximum number of records to return
        schema:
          minimum: 1
          type: integer
          default: 500
      - name: cursor
        in: query
        description: It's an opaque string field indicating the next record in the requested collection.
        schema:
          type: string
      - name: sortBy
        in: query
        description: A field within the response to sort by.
        schema:
          type: string
      - name: order
        in: query
        description: The sort order of the field ascending or descending.
        schema:
          type: string
          default: asc
          enum:
          - asc
          - desc
      - name: id
        in: query
        description: 'The list of Device Uuids (e.g., `6bef213c-19ca-4170-8375-b694e251101c`).


          Examples:


          `id=6bef213c-19ca-4170-8375-b694e251101c` (single device requested)


          `id=6bef213c-19ca-4170-8375-b694e251101c&id=32219612-819e-4b5e-a96b-cf22aca13dd9`

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: siteId
        in: query
        description: 'The UUID of the site. (Ex. `flooruuid`)


          Examples:


          `?siteId=id1` (single id requested)


          `?siteId=id1&siteId=id2&siteId=id3` (multiple ids requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: siteHierarchy
        in: query
        description: 'The full hierarchical breakdown of the site tree starting from Global site name and ending with the
          specific site name. The Root site is named "Global" (Ex. `Global/AreaName/BuildingName/FloorName`)


          This field supports wildcard asterisk (`*`) character search support. E.g. `*/San*, */San, /San*`


          Examples:


          `?siteHierarchy=Global/AreaName/BuildingName/FloorName` (single siteHierarchy requested)


          `?siteHierarchy=Global/AreaName/BuildingName/FloorName&siteHierarchy=Global/AreaName2/BuildingName2/FloorName2`
          (multiple siteHierarchies requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: siteHierarchyId
        in: query
        description: 'The full hierarchy breakdown of the site tree in id form starting from Global site UUID and ending with
          the specific site UUID. (Ex. `globalUuid/areaUuid/buildingUuid/floorUuid`)


          This field supports wildcard asterisk (`*`) character search support. E.g. `*uuid*, *uuid, uuid*`


          Examples:


          `?siteHierarchyId=globalUuid/areaUuid/buildingUuid/floorUuid `(single siteHierarchyId requested)


          `?siteHierarchyId=globalUuid/areaUuid/buildingUuid/floorUuid&siteHierarchyId=globalUuid/areaUuid2/buildingUuid2/floorUuid2`
          (multiple siteHierarchyIds requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: deviceCategory
        in: query
        description: "The list of device deviceCategories. \n\nExamples:\n\n`deviceCategory=Switch` (single device family\
          \ requested)\n\n`deviceCategory=Switch&deviceCategory=Router` (multiple device categories with comma separator)\n"
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            format: string
            enum:
            - Switch
            - Router
      - name: deviceSubCategory
        in: query
        description: 'The list of device sub categories.


          Examples:


          `deviceSubCategory=Cisco Catalyst 9300 Series Switches` (single device family requested)


          `deviceSubCategory=Cisco Catalyst 9300 Series Switches&deviceSubCategory=Cisco Catalyst 9400 Series Switches`

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            format: string
      - name: view
        in: query
        description: 'List of views. View and attribute work in union. Each view will include its attributes. For example,
          view device includes all the attributes related to device. Please refer to `NetworkDeviceEnergyView` model for supported
          list of views


          Examples:

          `view=device&view=energy`

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: attribute
        in: query
        description: "List of attributes. Please refer to `NetworkDeviceEnergyAttribute` for supported list of attributes\
          \    \n\nExamples:\n`attribute=id&attribute=energyConsumed`\n"
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: X-CALLER-ID
        in: header
        description: 'Caller ID is used to trace the origin of API calls and their associated queries executed on the database.
          It''s an optional header parameter that can be added to an API request.

          '
        required: false
        schema:
          type: string
          default: unknown
        example: intent
      responses:
        '200':
          description: Devices Energy Summaries Response model on success
          content:
            application/json; charset=utf-8:
              schema:
                $ref: '#/components/schemas/NetworkDevicesEnergyResponse'
              example:
                response:
                - id: 8f741bdf-788c-48f7-8ab1-017a826e4521
                  deviceName: sda-c9k-100.cisco.com
                  deviceCategory: Switches
                  deviceSubCategory: Cisco Catalyst 9300 Series Switches
                  siteId: 8f741bdf-788c-48f7-8ab1-017a826e4521
                  siteHierarchy: Global/Country1/Site1
                  siteHierarchyId: 8f741bdf-788c-48f7-8ab1-017a826e4521/8f741bdf-788c-48f7-8ab1-017a826e4521
                  energyConsumed: 2023
                  estimatedCost: 2524.23
                  estimatedEmission: 513
                  carbonIntensity: 123
                page:
                  limit: 10
                  cursor: eyJ1dWlkX3Rlcm1zIjoiZTBlM2VkMDgtNjE5OS00ZmVmLWFiNDEtZjA4OTcwMTMzYjdkIn0=
                  count: 20
                  sortBy:
                  - name: name
                    order: asc
                version: '2.0'
        '400':
          description: The client made a request that the server could not understand (for example, the request syntax is
            incorrect).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: The server could not fulfill the request due to internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        1XX:
          description: Informational Responses - The server received the request and sent an informational response.
        2XX:
          description: Successful Responses - The server received the client request, understood it, and accepted it.
        3XX:
          description: Redirection Messages - The client must take additional action to complete the request.
        4XX:
          description: Client Error Responses - The client request caused the error.
        5XX:
          description: Server Error Responses - The server failed to fulfill the request.
        default:
          description: Unexpected Error
    servers:
    - url: https://developer.cisco.com/data/api/v1
  /data/api/v1/energy/clients:
    get:
      tags:
      - energy
      summary: Get clients energy
      description: Retrieves a list of client devices with energy data based on the specified query parameters. It returns
        the most recent snapshot of energy data within the provided start and end times. If no start and end times are specified,
        it defaults to returning the latest available energy data from the past 24 hours.
      operationId: readClientDevicesEnergy
      parameters:
      - name: startTime
        in: query
        description: 'Start time from which API queries the data set related to the resource. It must be specified in UNIX
          epochtime in milliseconds. Value is inclusive.


          If `startTime` is not provided, API will default to one day before `endTime`.

          '
        required: false
        style: form
        explode: true
        schema:
          type: integer
          format: int64
        example: 1705348800000
      - name: endTime
        in: query
        description: 'End time to which API queries the data set related to the resource. It must be specified in UNIX epochtime
          in milliseconds. Value is inclusive.


          If `endTime` is not provided, API will default to one day after `startTime`. If `startTime` is not provided either,
          API will default to current time.

          '
        required: false
        style: form
        explode: true
        schema:
          type: integer
          format: int64
        example: 1705435200000
      - name: limit
        in: query
        description: Maximum number of records to return
        schema:
          minimum: 1
          type: integer
          default: 500
      - name: cursor
        in: query
        description: It's an opaque string field indicating the next record in the requested collection.
        schema:
          type: string
      - name: sortBy
        in: query
        description: A field within the response to sort by.
        schema:
          type: string
      - name: order
        in: query
        description: The sort order of the field ascending or descending.
        schema:
          type: string
          default: asc
          enum:
          - asc
          - desc
      - name: id
        in: query
        description: 'The list of Mac addresses (e.g., `54:9F:C6:43:FF:80`).


          Examples:


          `id=54:9F:C6:43:FF:80` (single device requested)


          `id=54:9F:C6:43:FF:80&id=01:23:45:67:89:AB`

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: siteId
        in: query
        description: 'The UUID of the site. (Ex. `flooruuid`)


          Examples:


          `?siteId=id1` (single id requested)


          `?siteId=id1&siteId=id2&siteId=id3` (multiple ids requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: siteHierarchy
        in: query
        description: 'The full hierarchical breakdown of the site tree starting from Global site name and ending with the
          specific site name. The Root site is named "Global" (Ex. `Global/AreaName/BuildingName/FloorName`)


          This field supports wildcard asterisk (`*`) character search support. E.g. `*/San*, */San, /San*`


          Examples:


          `?siteHierarchy=Global/AreaName/BuildingName/FloorName` (single siteHierarchy requested)


          `?siteHierarchy=Global/AreaName/BuildingName/FloorName&siteHierarchy=Global/AreaName2/BuildingName2/FloorName2`
          (multiple siteHierarchies requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: siteHierarchyId
        in: query
        description: 'The full hierarchy breakdown of the site tree in id form starting from Global site UUID and ending with
          the specific site UUID. (Ex. `globalUuid/areaUuid/buildingUuid/floorUuid`)


          This field supports wildcard asterisk (`*`) character search support. E.g. `*uuid*, *uuid, uuid*`


          Examples:


          `?siteHierarchyId=globalUuid/areaUuid/buildingUuid/floorUuid `(single siteHierarchyId requested)


          `?siteHierarchyId=globalUuid/areaUuid/buildingUuid/floorUuid&siteHierarchyId=globalUuid/areaUuid2/buildingUuid2/floorUuid2`
          (multiple siteHierarchyIds requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: deviceCategory
        in: query
        description: "The list of device deviceCategories. \n\nExamples:\n\n`deviceCategory=AccessPoint` (single device family\
          \ requested)\n\n`deviceCategory=AccessPoint&deviceCategory=OtherPOEDevice` (multiple device categories with comma\
          \ separator)\n"
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            format: string
            enum:
            - AccessPoint
            - WirelessController
            - Sensor
            - OtherPOEDevice
      - name: deviceSubCategory
        in: query
        description: 'The list of device sub categories.


          Examples:


          `deviceSubCategory=IP Phone 7821` (single sub category requested)


          `deviceSubCategory=IP Phone 7821&deviceSubCategory=IEEE PD`

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            format: string
      - name: view
        in: query
        description: 'List of views. View and attribute work in union. Each view will include its attributes. For example,
          view device includes all the attributes related to device. Please refer to `ClientDeviceEnergyView` model for supported
          list of views


          Examples:

          `view=device&view=energy`

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: attribute
        in: query
        description: "List of attributes. Please refer to `ClientDeviceEnergyAttribute` for supported list of attributes \
          \   \n\nExamples:\n`attribute=id&attribute=energyConsumed`\n"
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: X-CALLER-ID
        in: header
        description: 'Caller ID is used to trace the origin of API calls and their associated queries executed on the database.
          It''s an optional header parameter that can be added to an API request.

          '
        required: false
        schema:
          type: string
          default: unknown
        example: intent
      responses:
        '200':
          description: Devices Energy Summaries Response model on success
          content:
            application/json; charset=utf-8:
              schema:
                $ref: '#/components/schemas/ClientDevicesEnergyResponse'
              example:
                response:
                - id: 00:7E:95:79:99:17
                  deviceName: SEP007E95799917
                  connectedDeviceName: ott-sda-c9k-21.cisco.com
                  connectedInterfaceName: GigabitEthernet1/1/0
                  deviceCategory: OtherPOEDevice
                  deviceSubCategory: IP Phone 7821
                  siteId: 8f741bdf-788c-48f7-8ab1-017a826e4521
                  siteHierarchy: Global/Country1/Site1
                  siteHierarchyId: 8f741bdf-788c-48f7-8ab1-017a826e4521/8f741bdf-788c-48f7-8ab1-017a826e4521
                  energyConsumed: 2023
                  estimatedCost: 2524.23
                  estimatedEmission: 513
                  carbonIntensity: 123
                page:
                  limit: 10
                  cursor: eyJ1dWlkX3Rlcm1zIjoiZTBlM2VkMDgtNjE5OS00ZmVmLWFiNDEtZjA4OTcwMTMzYjdkIn0=
                  count: 20
                  sortBy:
                  - name: name
                    order: asc
                version: '2.0'
        '400':
          description: The client made a request that the server could not understand (for example, the request syntax is
            incorrect).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: The server could not fulfill the request due to internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        1XX:
          description: Informational Responses - The server received the request and sent an informational response.
        2XX:
          description: Successful Responses - The server received the client request, understood it, and accepted it.
        3XX:
          description: Redirection Messages - The client must take additional action to complete the request.
        4XX:
          description: Client Error Responses - The client request caused the error.
        5XX:
          description: Server Error Responses - The server failed to fulfill the request.
        default:
          description: Unexpected Error
    servers:
    - url: https://developer.cisco.com/data/api/v1
  /data/api/v1/energy/networkDevices/{id}:
    get:
      tags:
      - energy
      summary: Get device energy by ID
      description: Retrieves network device energy data for a specified time range based on the device ID. Returns the latest
        available snapshot of energy data between the provided start and end times. If no start and end times are specified,
        it defaults to returning the latest available energy data for the past 24 hours.
      operationId: readNetworkDevicesEnergyById
      parameters:
      - name: id
        in: path
        description: The UUID of the Network Device. (Ex. "6bef213c-19ca-4170-8375-b694e251101c")
        required: true
        style: simple
        explode: false
        schema:
          type: string
      - name: startTime
        in: query
        description: 'Start time from which API queries the data set related to the resource. It must be specified in UNIX
          epochtime in milliseconds. Value is inclusive.


          If `startTime` is not provided, API will default to one day before `endTime`.

          '
        required: false
        style: form
        explode: true
        schema:
          type: integer
          format: int64
        example: 1705348800000
      - name: endTime
        in: query
        description: 'End time to which API queries the data set related to the resource. It must be specified in UNIX epochtime
          in milliseconds. Value is inclusive.


          If `endTime` is not provided, API will default to one day after `startTime`. If `startTime` is not provided either,
          API will default to current time.

          '
        required: false
        style: form
        explode: true
        schema:
          type: integer
          format: int64
        example: 1705435200000
      - name: view
        in: query
        description: 'List of views. View and attribute work in union. Each view will include its attributes. For example,
          view device includes all the attributes related to device. Please refer to `NetworkDeviceEnergyView` model for supported
          list of views


          Examples:

          `view=device&view=energy`

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: attribute
        in: query
        description: "List of attributes. Please refer to `NetworkDeviceEnergyAttribute` for supported list of attributes\
          \    \n\nExamples:\n`attribute=id&attribute=energyConsumed`\n"
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: X-CALLER-ID
        in: header
        description: 'Caller ID is used to trace the origin of API calls and their associated queries executed on the database.
          It''s an optional header parameter that can be added to an API request.

          '
        required: false
        schema:
          type: string
          default: unknown
        example: intent
      responses:
        '200':
          description: Device Energy Summaries Response model on success
          content:
            application/json; charset=utf-8:
              schema:
                $ref: '#/components/schemas/NetworkDeviceEnergyResponse'
              example:
                response:
                  id: 8f741bdf-788c-48f7-8ab1-017a826e4521
                  deviceName: sda-c9k-100.cisco.com
                  deviceCategory: Switches
                  deviceSubCategory: Cisco Catalyst 9300 Series Switches
                  siteId: 8f741bdf-788c-48f7-8ab1-017a826e4521
                  siteHierarchy: Global/Country1/Site1
                  siteHierarchyId: 8f741bdf-788c-48f7-8ab1-017a826e4521/8f741bdf-788c-48f7-8ab1-017a826e4521
                  energyConsumed: 2023
                  estimatedCost: 2524.23
                  estimatedEmission: 513
                  carbonIntensity: 123
                version: '2.0'
        '400':
          description: The client made a request that the server could not understand (for example, the request syntax is
            incorrect).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: The client made a request for a resource that does not exist.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: The server could not fulfill the request due to internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        1XX:
          description: Informational Responses - The server received the request and sent an informational response.
        2XX:
          description: Successful Responses - The server received the client request, understood it, and accepted it.
        3XX:
          description: Redirection Messages - The client must take additional action to complete the request.
        4XX:
          description: Client Error Responses - The client request caused the error.
        5XX:
          description: Server Error Responses - The server failed to fulfill the request.
        default:
          description: Unexpected Error
    servers:
    - url: https://developer.cisco.com/data/api/v1
  /data/api/v1/energy/clients/{id}:
    get:
      tags:
      - energy
      summary: Get client energy by ID
      description: Retrieves client device energy data for a specified time range based on the client ID. Returns the latest
        available snapshot of energy data between the provided start and end times. If no start and end times are specified,
        it defaults to returning the latest available energy data for the past 24 hours.
      operationId: readClientDevicesEnergyById
      parameters:
      - name: id
        in: path
        description: "Mac address of a client device (e.g., 54:9F:C6:43:FF:80). It can be specified is any notational conventions\
          \ \n  01:23:45:67:89:AB or 01-23-45-67-89-AB or 0123.4567.89AB and is case insensitive."
        required: true
        style: simple
        explode: false
        schema:
          pattern: ^([0-9A-Fa-f]{2}[:-]){5}([0-9A-Fa-f]{2})$|^[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}$
          type: string
      - name: startTime
        in: query
        description: 'Start time from which API queries the data set related to the resource. It must be specified in UNIX
          epochtime in milliseconds. Value is inclusive.


          If `startTime` is not provided, API will default to one day before `endTime`.

          '
        required: false
        style: form
        explode: true
        schema:
          type: integer
          format: int64
        example: 1705348800000
      - name: endTime
        in: query
        description: 'End time to which API queries the data set related to the resource. It must be specified in UNIX epochtime
          in milliseconds. Value is inclusive.


          If `endTime` is not provided, API will default to one day after `startTime`. If `startTime` is not provided either,
          API will default to current time.

          '
        required: false
        style: form
        explode: true
        schema:
          type: integer
          format: int64
        example: 1705435200000
      - name: view
        in: query
        description: 'List of views. View and attribute work in union. Each view will include its attributes. For example,
          view device includes all the attributes related to device. Please refer to `ClientDeviceEnergyView` model for supported
          list of views


          Examples:

          `view=device&view=energy`

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: attribute
        in: query
        description: "List of attributes. Please refer to `ClientDeviceEnergyAttribute` for supported list of attributes \
          \   \n\nExamples:\n`attribute=id&attribute=energyConsumed`\n"
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: X-CALLER-ID
        in: header
        description: 'Caller ID is used to trace the origin of API calls and their associated queries executed on the database.
          It''s an optional header parameter that can be added to an API request.

          '
        required: false
        schema:
          type: string
          default: unknown
        example: intent
      responses:
        '200':
          description: Device Energy Summaries Response model on success
          content:
            application/json; charset=utf-8:
              schema:
                $ref: '#/components/schemas/ClientDeviceEnergyResponse'
              example:
                response:
                  id: 54:9F:C6:43:FF:80
                  deviceName: SEPAC7E8AB6B5D6
                  connectedDeviceName: ott-sda-c9k-575
                  connectedInterfaceName: GigabitEthernet1/1/0
                  deviceCategory: OtherPOEDevice
                  deviceSubCategory: IP Phone 8865
                  siteId: 8f741bdf-788c-48f7-8ab1-017a826e4521
                  siteHierarchy: Global/Country1/Site1
                  siteHierarchyId: 8f741bdf-788c-48f7-8ab1-017a826e4521/8f741bdf-788c-48f7-8ab1-017a826e4521
                  energyConsumed: 2023
                  estimatedCost: 2524.23
                  estimatedEmission: 513
                  carbonIntensity: 123
                version: '2.0'
        '400':
          description: The client made a request that the server could not understand (for example, the request syntax is
            incorrect).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: The client made a request for a resource that does not exist.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: The server could not fulfill the request due to internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        1XX:
          description: Informational Responses - The server received the request and sent an informational response.
        2XX:
          description: Successful Responses - The server received the client request, understood it, and accepted it.
        3XX:
          description: Redirection Messages - The client must take additional action to complete the request.
        4XX:
          description: Client Error Responses - The client request caused the error.
        5XX:
          description: Server Error Responses - The server failed to fulfill the request.
        default:
          description: Unexpected Error
    servers:
   

# --- truncated at 32 KB (194 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cisco-catalyst-center/refs/heads/main/openapi/cisco-catalyst-center-energy-api-openapi.yml