Every API here is available over the APIs.io API and to AI agents over MCP.
openapi: 3.2.0
info:
description: 'Cisco Intersight is a management platform delivered as a service with embedded analytics for your Cisco and
3rd party IT infrastructure. This platform offers an intelligent level of management that enables
IT organizations to analyze, simplify, and automate their environments in more advanced ways than the prior
generations of tools. Cisco Intersight provides an integrated and intuitive management experience for
resources in the traditional data center as well as at the edge. With flexible deployment options to address
complex security needs, getting started with Intersight is quick and easy.
Cisco Intersight has deep integration with Cisco UCS and HyperFlex systems allowing for remote deployment,
configuration, and ongoing maintenance. The model-based deployment works for a single system in a remote
location or hundreds of systems in a data center and enables rapid, standardized configuration and deployment.
It also streamlines maintaining those systems whether you are working with small or very large configurations.
The Intersight OpenAPI document defines the complete set of properties that are returned in the
HTTP response. From that perspective, a client can expect that no additional properties are returned,
unless these properties are explicitly defined in the OpenAPI document.
However, when a client uses an older version of the Intersight OpenAPI document, the server may
send additional properties because the software is more recent than the client. In that case, the client
may receive properties that it does not know about.
Some generated SDKs perform a strict validation of the HTTP response body against the OpenAPI document.
This document was created on 2026-08-07T06:46:04Z.'
version: 1.0.11-20260807064027971
title: Cisco Intersight Workflows Energy API
license:
name: Apache License, Version 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
contact:
name: Intersight API support
url: https://intersight.com/help
email: intersight@cisco.com
x-provenance:
method: harvested
authored_by: Cisco Intersight
harvested_by: API Evangelist
harvested_on: '2026-08-19'
first_party: true
provider_published: true
source_host: cdn.intersight.com
note: Cisco publishes the full Intersight OpenAPI 3.0.2 anonymously from its CDN (27.5MB master document; 3,963 operations / 2,448 paths / 5,612 schemas) plus 11 per-service documents covering 100% of the master's paths. Byte-identity reconfirmed 2026-08-19 by SHA-256. Note intersight.com itself is a soft-404 farm — the contract is on the CDN, not the app host.
x-evidence:
- type: source
url: https://cdn.intersight.com/components/an-apidocs/1.0.11-20260807064027971/model/intersight-openapi-v3-1.0.11-20260807064027971.json
- type: source
url: https://intersight.com/apidocs/apirefs/
servers:
- url: https://{server}
variables:
server:
default: intersight.com
description: The Intersight URL for the cloud-based infrastructure management APIs.
tags:
- name: energy
paths:
/api/v1/energy/DailyMetrics:
post:
tags:
- energy
x-intersight-type: SaaS
summary: Create a 'energy.DailyMetrics' resource.
operationId: CreateEnergyDailyMetrics
security:
- cookieAuth: []
- http_signature: []
- oAuth2:
- CREATE.energy.DailyMetrics
- PRIVSET.Account Administrator
- PRIVSET.Sustainability Metrics Viewer
- ROLE.Account Administrator
- ROLE.Sustainability Metrics Viewer
parameters:
- $ref: '#/components/parameters/IfMatch'
- $ref: '#/components/parameters/IfNoneMatch'
requestBody:
description: The 'energy.DailyMetrics' resource to create.
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/energy.DailyMetrics'
responses:
'200':
description: The HTTP 200 status response code indicates that the request has succeeded and the 'energy.DailyMetrics' resource was created as requested. The 'energy.DailyMetrics' resource is created before this response is sent back and the resource is returned in the body of the message.
headers:
Set-Cookie:
$ref: '#/components/headers/Set-Cookie'
x-starship-traceid:
$ref: '#/components/headers/x-starship-traceid'
content:
application/json:
schema:
$ref: '#/components/schemas/energy.DailyMetrics'
links:
GetEnergyDailyMetricsByMoid:
operationId: GetEnergyDailyMetricsByMoid
parameters:
Moid: $response.body#/Moid
description: The 'Moid' value returned in the response can be used as the 'Moid' parameter in 'GET /api/v1/energy/DailyMetrics/{Moid}'.
GetIamAccountByMoid:
$ref: '#/components/links/GetIamAccountByMoid'
GetIamDomainGroupByMoid:
$ref: '#/components/links/GetIamDomainGroupByMoid'
'400':
$ref: '#/components/responses/http_status_400'
'401':
$ref: '#/components/responses/http_status_401'
'403':
$ref: '#/components/responses/http_status_403'
'404':
$ref: '#/components/responses/http_status_404'
default:
$ref: '#/components/responses/default'
/api/v1/energy/Metrics:
post:
tags:
- energy
x-intersight-type: SaaS
summary: Create a 'energy.Metrics' resource.
operationId: CreateEnergyMetrics
security:
- cookieAuth: []
- http_signature: []
- oAuth2:
- CREATE.energy.Metrics
- PRIVSET.Account Administrator
- PRIVSET.Sustainability Metrics Viewer
- ROLE.Account Administrator
- ROLE.Sustainability Metrics Viewer
parameters:
- $ref: '#/components/parameters/IfMatch'
- $ref: '#/components/parameters/IfNoneMatch'
requestBody:
description: The 'energy.Metrics' resource to create.
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/energy.Metrics'
responses:
'200':
description: The HTTP 200 status response code indicates that the request has succeeded and the 'energy.Metrics' resource was created as requested. The 'energy.Metrics' resource is created before this response is sent back and the resource is returned in the body of the message.
headers:
Set-Cookie:
$ref: '#/components/headers/Set-Cookie'
x-starship-traceid:
$ref: '#/components/headers/x-starship-traceid'
content:
application/json:
schema:
$ref: '#/components/schemas/energy.Metrics'
links:
GetEnergyMetricsByMoid:
operationId: GetEnergyMetricsByMoid
parameters:
Moid: $response.body#/Moid
description: The 'Moid' value returned in the response can be used as the 'Moid' parameter in 'GET /api/v1/energy/Metrics/{Moid}'.
GetIamAccountByMoid:
$ref: '#/components/links/GetIamAccountByMoid'
GetIamDomainGroupByMoid:
$ref: '#/components/links/GetIamDomainGroupByMoid'
'400':
$ref: '#/components/responses/http_status_400'
'401':
$ref: '#/components/responses/http_status_401'
'403':
$ref: '#/components/responses/http_status_403'
'404':
$ref: '#/components/responses/http_status_404'
default:
$ref: '#/components/responses/default'
components:
schemas:
energy.DailyMetrics:
title: Energy:Daily Metrics
description: Returns carbon intensity, power breakdown, and electricity rate power metrics for a set of locations and a time span.
x-allOf-name: energy.DailyMetrics
allOf:
- $ref: intersight-system-v3-1.0.11-20260807064027971.json#/components/schemas/mo.BaseMo
energy.Metrics:
title: Energy:Metrics
description: Returns carbon intensity, power breakdown, and electricity rate power metrics for a set of locations and a time span.
x-allOf-name: energy.Metrics
allOf:
- $ref: intersight-system-v3-1.0.11-20260807064027971.json#/components/schemas/mo.BaseMo
parameters:
IfMatch:
name: If-Match
in: header
description: 'For methods that apply server-side changes, and in particular for PUT, If-Match can be used to prevent
the lost update problem. It can check if the modification of a resource that the user wants to upload
will not override another change that has been done since the original resource was fetched.
If the request cannot be fulfilled, the 412 (Precondition Failed) response is returned.
When modifying a resource using POST or PUT, the If-Match header must be set to the value of
the resource ModTime property after which no lost update problem should occur.
For example, a client send a GET request to obtain a resource, which includes the ModTime property.
The ModTime indicates the last time the resource was created or modified. The client then sends
a POST or PUT request with the If-Match header set to the ModTime property of the resource as obtained
in the GET request.'
required: false
schema:
type: string
IfNoneMatch:
name: If-None-Match
in: header
description: 'For methods that apply server-side changes, If-None-Match used with the * value can be used to create
a resource not known to exist, guaranteeing that another resource creation didn''t happen before,
losing the data of the previous put. The request will be processed only if the eventually existing
resource''s ETag doesn''t match any of the values listed. Otherwise, the status code 412
(Precondition Failed) is used.
The asterisk is a special value representing any resource. It is only useful when creating a resource,
usually with PUT, to check if another resource with the identity has already been created before.
The comparison with the stored ETag uses the weak comparison algorithm, meaning two resources are
considered identical if the content is equivalent - they don''t have to be identical byte for byte.'
required: false
schema:
type: string
headers:
x-starship-traceid:
description: A value that uniquely identifies a HTTP request and its response.
schema:
type: string
Set-Cookie:
description: Cookie authentication key for use with the `cookieAuth` apiKey authentication.
schema:
type: string
example: X-Starship-Token=abcde12345; Path=/
responses:
http_status_404:
description: The specified resource was not found. The HTTP body contains a document that provides more details about the error.
headers:
x-starship-traceid:
$ref: '#/components/headers/x-starship-traceid'
content:
application/json:
schema:
$ref: intersight-system-v3-1.0.11-20260807064027971.json#/components/schemas/Error
http_status_400:
description: 'The request could not be understood by the server due to malformed syntax.
The client SHOULD NOT repeat the request without modifications.
For example, the request may contain an incorrect JSON syntax, or the request fails
validation checks.
The HTTP body may contain a document that provides more details about the error.'
headers:
x-starship-traceid:
$ref: '#/components/headers/x-starship-traceid'
content:
application/json:
schema:
$ref: intersight-system-v3-1.0.11-20260807064027971.json#/components/schemas/Error
default:
description: An unexpected error occurred.
headers:
x-starship-traceid:
$ref: '#/components/headers/x-starship-traceid'
content:
application/json:
schema:
$ref: intersight-system-v3-1.0.11-20260807064027971.json#/components/schemas/Error
http_status_403:
description: 'The request was properly authenticated, but the server is refusing to fulfill it.
The HTTP body may contain a document that provides more details about the error.
For example, the user may not have sufficient privileges to perform the request.'
headers:
x-starship-traceid:
$ref: '#/components/headers/x-starship-traceid'
content:
application/json:
schema:
$ref: intersight-system-v3-1.0.11-20260807064027971.json#/components/schemas/Error
http_status_401:
description: 'The request requires user authentication. The client may repeat the request with a suitable Authorization header field.
If the request already included Authorization credentials, then the 401 response indicates that authorization has
been refused for those credentials.
The HTTP body may contain a document that provides more details about the error.'
headers:
x-starship-traceid:
$ref: '#/components/headers/x-starship-traceid'
content:
application/json:
schema:
$ref: intersight-system-v3-1.0.11-20260807064027971.json#/components/schemas/Error
links:
GetIamAccountByMoid:
operationId: GetIamAccountByMoid
parameters:
Moid: $response.body#/AccountMoid
description: The 'AccountMoid' value returned in the response can be used as the 'Moid' parameter in 'GET /api/v1/iam/Accounts/{Moid}'.
GetIamDomainGroupByMoid:
operationId: GetIamDomainGroupByMoid
parameters:
Moid: $response.body#/DomainGroupMoid
description: The 'DomainGroupMoid' value returned in the response can be used as the 'Moid' parameter in 'GET /api/v1/iam/DomainGroups/{Moid}'.
securitySchemes:
cookieAuth:
type: apiKey
in: cookie
description: The authentication cookie obtained from a Single-Sign-On SAML assertion.
name: X-Starship-Token
http_signature:
type: http
scheme: signature
description: "The 'HTTP signature' security scheme. Each HTTP request is cryptographically signed\nas specified in https://datatracker.ietf.org/doc/draft-cavage-http-signatures/.\nSee [Intersight API and SDK documentation](https://intersight.com/apidocs) for details\nabout how to configure the HTTP signature scheme.\nYou must include the following fields in the signed headers.\n 1. '(request-target)'\n 1. '(created)'\n 1. 'Host'\n 1. 'Date'\n 1. 'Digest'\nIn addition, it is recommended that you include at least the following headers.\n 1. '(expires)'\n 1. 'Content-Type'\n* The '(created)' header expresses when the signature was created. The value must be a\n Unix timestamp integer value. Subsecond precision is not supported.\n* The ('expires') header is optional and expresses when the signature ceases to be valid.\n The value must be a Unix timestamp integer value. Subsecond precision is allowed\n using decimal notation.\n It is recommended to set the value of the '(expire)' header to '(created)' plus thirty\n minutes, i.e., the signature is valid for thirty minutes.\n* The 'Digest' header value must be a cryptographic digest of the HTTP request body,\n as specified in RFC 3230.\n* The 'Authorization' header must include the computed signature of the HTTP request.\n The host machine where the API client is running must be synchronized with Internet\n time (i.e., NIST time)."
oAuth2:
type: oauth2
description: 'The client uses the OAuth2 security scheme. To use OAuth2, a client application
must be registered by creating a iam.AppRegistration resource.
The user who creates the iam.AppRegistration resource can specify a list of OAuth2
scopes. These iam.AppRegistration scopes restricts which subset of scopes
a registered client can obtain.
Supported OAuth2 flows are:
**Authorization Code**
In the authorization code flow, the client sends a list of requested scopes to
the authorization URL (/iam/app-authorize). The scope in the authorization request
must be one of the scopes that have been configured in the corresponding
iam.AppRegistration resource.
**Client Credentials**
In the client credentials flow, the scope is selected when the AppRegistration
is created. The client cannot select a specific scope in the token request.'
flows:
authorizationCode:
authorizationUrl: /iam/app-authorize
tokenUrl: /iam/token
refreshUrl: /iam/token
scopes:
ROLE.Account Administrator: 'As an Account administrator, you have complete access to all services and resources in Intersight.
You can perform all administrative and management tasks, including claim and manage devices, create and deploy Server
and HyperFlex Cluster profiles, upgrade firmware, perform server actions, cross launch devices, add and manage users and groups,
configure Identity providers and more.
'
ROLE.Audit Log Viewer: 'As an Audit Log Viewer, you can view audit logs.
'
ROLE.Automation Governance: 'As an Automation Governor, you can approve or reject requests to publish generic objects, including Workflows,
Tasks, CDTs, FaaS, and Service Items. Each request is created for a generic asset, enabling automation governance
to publish these assets.
'
ROLE.Catalog Administrator: 'As a Catalog Administrator, you can create workflows, custom data types, resource selection policies,
service items, catalog items, execute catalog item, and view and perform post-deployment operations on the service item
instance. Also, you can view and publish the catalog items.
'
ROLE.Catalog User: 'As a Catalog User, you can view the catalog items that are assigned to you. You can deploy the catalog item,
track the catalog item execution, view the service item instance that is created or assigned to you, and
perform post-deployment operations on the service item instances.
'
ROLE.Complete Claim: 'As a Complete Claim user you can complete the claim of a previously created Target by
providing the security token of the device.
You do not have access to read the status or details of any devices within the account.
'
ROLE.Device Administrator: 'As a Device Administrator, you can claim and unclaim a device in Intersight, view the device details,
license status, a list of all the claimed devices, and generate API keys.
You cannot perform any other management or administrative task in this role.
'
ROLE.Device Technician: 'As a Device Technician you can claim a device, view the device details, license status, a list of
the claimed devices, and generate API keys. You cannot perform any other management or
administrative task in this role.
'
ROLE.External Syslog Administrator: 'As an External Syslog Administrator, you can configure an external syslog server on an on-prem appliance.
'
ROLE.HCI Cluster Administrator: 'As an HCI Cluster Administrator, you can view and manage HCI Clusters,
view all the cluster dashboard widgets, view cluster details. This role does not include the ability to claim a device.
You must have a Device Technician, Device Administrator, or an Account Administrator role to claim a device.
'
ROLE.HCI Cluster Operator: 'As an HCI Cluster Operator, you can view and manage HCI Clusters,
view all the cluster dashboard widgets, view cluster details. This role does not include the ability to claim a device.
You must have a Device Technician, Device Administrator, or an Account Administrator role to claim a device.
'
ROLE.HyperFlex Cluster Access Operator: 'As a HyperFlex Cluster Access Operator, you can cross launch CLI and HXConnect.
'
ROLE.HyperFlex Cluster Administrator: 'As a HyperFlex Cluster Administrator, you can create, edit, deploy, and manage HyperFlex Clusters,
view all the cluster dashboard widgets, view cluster details, create HyperFlex policies and profiles, execute
capacity planning, and launch HyperFlex Connect. This role does not include the ability to claim a device.
You must have a Device Technician, Device Administrator, or an Account Administrator role to claim a device.
'
ROLE.HyperFlex Cluster Data Protection Administrator: 'As a HyperFlex Cluster Data Protection Administrator, you can perform N:1 backups.
'
ROLE.HyperFlex Cluster Lifecycle Administrator: 'As a HyperFlex Cluster Lifecycle Administrator, you can install, expand, upgrade a HX cluster, execute capacity
planning, OS installation, VC plugin installation, security hardening, and launch HyperFlex Connect as admin.
'
ROLE.HyperFlex Cluster Operator: 'As a HyperFlex Cluster Operator, you can perform health checks and launch HyperFlex Connect.
However, you cannot change cluster configuration.
'
ROLE.HyperFlex Cluster Storage Administrator: 'As a HyperFlex Cluster Storage Administrator, you can perform datastore, iSCSI, and storage container CRUD operations.
'
ROLE.HyperFlex Cluster Syslog Administrator: 'As a HyperFlex Cluster Syslog Administrator, you can configure the external HX Syslog profile.
'
ROLE.HyperFlex Cluster System Administrator: 'As a HyperFlex Cluster System Administrator, you can perform most system administrator tasks,
create backups, view syslogs, and configure encryption.
'
ROLE.HyperFlex Cluster System Operator: 'As a HyperFlex Cluster System Operator, you can perform encryption, health checks, and post-install tasks.
'
ROLE.Integrated Systems Administrator: "As an Integrated Systems Administrator, you can perform all actions related to Integrated Systems (e.g., FlexPod) like\ncreate/edit/delete of an Integrated System. In addition you can perform administrative and management tasks related to \ndevices (including claim), servers, server profiles, UCS domain, switch profiles, hypervisors, network/SAN switches, \nstorage devices. Also, you can define workflow and task definitions and can execute them and view workflow executions.\n"
ROLE.Integrated Systems Operator: "As an Integrated Systems Operator, you can view Integrated Systems (e.g., FlexPod) and can run inventory based actions (e.g., Interoperability check) \nIn addition you can view devices, servers, server profiles, UCS domain, switch profiles, hypervisors, network/SAN \nswitches, storage devices and workflows. This role does not include the ability to claim a target. You must have a\nDevice Technician, Device Administrator, or an Account Administrator role to claim a target.\n"
ROLE.Kubernetes Administrator: 'As a Kubernetes Administrator, you can create, edit, deploy, and manage Kubernetes Clusters. Also, you can
view all the cluster dashboard widgets, and view cluster details. In addition, you also have privileges to
view and manage storage targets associated with the Kubernetes clusters. The capability to view and execute
workflows against the Kubernetes clusters is also granted. It also allows
the user to run workflows to manage VMs on hypervisor endpoints, and manage connected storage.
The ability to create and view IP pools is also allowed.
This role does not include the ability to claim a target.
You must have a Device Technician, Device Administrator, or an Account Administrator role to claim a target.
'
ROLE.Kubernetes Operator: 'As a Kubernetes Operator, you can view Kubernetes Clusters. Also, you can
view all the cluster dashboard widgets, and view cluster details. In addition, you also have privileges to
view storage targets associated with the Kubernetes clusters. The capability to view
workflows is also granted. It also allows the user to view VMs on hypervisor endpoints.
This role also provides the capability to view IP pools.
This role does not include the ability to claim a target.
You must have a Device Technician, Device Administrator, or an Account Administrator role to claim a target.
'
ROLE.Location Management: 'As a user with location management privileges, you can manage location, including creating, updating, and deleting.
'
ROLE.Network Administrator: 'As a Network Administrator, you can create, update, delete and view the Managed network device objects.
The capability to view and execute workflows against the network device is also granted.
This role does not include the ability to claim a target. You must have a Device Technician, Device Administrator,
or an Account Administrator role to claim a target.
'
ROLE.Network Operator: 'As a Network Operator, you can view the Managed network device objects. The capability to view workflows against the
network device is also granted. This role does not include the ability to claim a target. You must have a Device
Technician, Device Administrator, or an Account Administrator role to claim a target.
'
ROLE.Nexus Administrator: 'As a Nexus Administrator, you have the privileges to perform all Nexus related operations. This includes
claiming devices, updating policy configuration, and monitoring the system.
'
ROLE.Nexus Analyst: 'As a Nexus Analyst, you can run and update the available Nexus Cloud analyses such as Sustainability, Conformance, Compliance, and others.
'
ROLE.Nexus Config Administrator: 'As a Nexus Config Administrator, you can create or modify policy configuration and can initiate the
workflow that will activate policy changes.
This role does not allow you to claim or remove devices.
'
ROLE.Nexus Observer: 'As a Nexus Observer, you can generally view the state of all devices. Additional items
include things like viewing configured policies and monitoring active flows. This role does
not include any permission which allows the system to be changed.
'
ROLE.Read-Only: 'As a Read-Only user, you can view the dashboard, table views of the managed devices, change your user preferences,
and generate API keys. You cannot claim a device, add or remove a user, configure Identity providers or
perform any server actions.
'
ROLE.SAN Administrator: 'As a SAN Administrator, you can create, update, delete and view the Managed SAN switch objects.
The capability to view and execute workflows against the SAN switches is also granted.
This role does not include the ability to claim a target. You must have a Device Technician, Device Administrator,
or an Account Administrator role to claim a target.
'
ROLE.SAN Operator: 'As a SAN Operator, you can view the Managed SAN switch objects. The capability to view workflows against the
SAN switches is also granted. This role does not include the ability to claim a target. You must have a Device
Technician, Device Administrator, or an Account Administrator role to claim a target.
'
ROLE.Server Administrator: 'As a Server Administrator, you can view and manage UCS Servers and Fabric Interconnects,
view all the server and Fabric Interconnect dashboard widgets, perform server actions,
view server details, launch management interfaces and the CLI, create and deploy server
policies and profiles, and manage API keys. This role does not include the ability to claim a device.
You must have a Device Technician, Device Administrator, or an Account Administrator role to claim a device.
'
ROLE.Service Designer: 'As a Service Designer, you can create custom data types, tasks, workflows, resource selection criteria,
and use these to design the service items. The service designer can validate the service items by using
the deployment and post-deployment actions.
'
ROLE.Service Operator: 'As a Service Operator, you can view and update the catalog items, service items, and workflows. Also, you can
execute the workflow and validate the catalog or service items.
'
ROLE.Storage Administrator: 'As a Storage Administrator, a user can view and manage Storage devices, view and execute
workflows and view all the storage dashboard widgets.
This privilege does not include the ability to claim a device. You must have a
Device Technician, Device Administrator, or an Account Administrator role to claim a device.
'
ROLE.Support Services: 'As a Support Services user, you can view the dashboard and table views of managed devices, change your user preferences,
collect tech support bundles, and generate API keys. In this role, you cannot claim targets, add or remove users, configure
Identity Providers, or perform server actions.
'
ROLE.Sustainability Metrics Viewer: 'As a Sustainability Metrics Viewer user, you have read access to the Energy Management Capability (EMC) features and the ability
register an OAuth2 application for programmatic access to the APIs.
'
ROLE.Tag Management: 'As a user with tag management privileges, you can manage tag definitions, including creating, updating, and deleting tags.
'
ROLE.UCS Domain Administrator: 'As a UCS Domain Administrator, you can view and manage Switch Profiles and Network Configuration Policies, view Fabric Interconnect dashboard widgets, perform actions on Switch, launch management interfaces and the CLI, create and deploy switch policies and profiles, and manage API keys. This role does not include the ability to claim a device. You must have a Device Technician, Device Administrator, or an Account Administrator role to claim a device.
'
ROLE.Unified Edge Administrator: 'As a Unified Edge Administrator, you can view and manage Switch Profiles, Network and Chassis Configuration Policies, view Unified Edge dashboard widgets, perform actions on Switch and Chassis, launch management interfaces and the CLI, and manage API keys. This role does not include the ability to claim a device. You must have a Device Technician, Device Administrator, or an Account Administrator role to claim a device.
'
ROLE.User Access Administrator: 'As a User Access Administrator, you can add and manage Users and Groups in Intersight, view account details
and audit logs, manage the IdPs, roles, sessions and API keys for non Account Administrator users.
However, you cannot claim a device or perform any management tasks in Intersight.
You cannot add or manage a user with Account Administrator role.
'
ROLE.Virtualization Administrator: 'As a Virtualization Administrator, a user can view and manage hypervisor resources, view
and execu
# --- truncated at 32 KB (383 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/intersight/refs/heads/main/openapi/intersight-energy-api-openapi.yml