iDRAC9 with Lifecycle Controller Version 3.36.36.36 Redfish API Guide

Redfish is a web-based API which implies that resources are accessed using client supplied URLs. URLs are required to identify the Redfish resources. The Redfish API uses a simple URL hierarchy which follows a /redfish/v1/ pattern for all resources. To access a Redfish resource, use the URL pattern https://<iDRAC IP>/redfish/v1/<Resource Path>. For more information on the supported resources, see Redfish resources. iDRAC supports the following URL patterns:

• /redfish — URL for the Redfish version object.
• /redfish/v1 — Root URL for version 1 of the Redfish services.
• /redfish/v1/odata — Redfish services expose an OData service document at this URI. This service document provides a standard format for enumerating resources that are exposed by the service by enabling all generic hypermedia-driven OData clients to navigate to the resources of the service.
• /redfish/v1/$metadata — Redfish services expose a metadata document in XML format. This document describes the resources and collections that are available at the service root URI. It also provides references to other metadata documents, which describe the complete set of resource types that are exposed by the service.
• /redfish/v1/$metadata#<Collection or a Singleton resource> — Metadata URL specified as a part of @odata.context property for all resources. This URL returns data in XML format.
• /redfish/v1/JsonSchemas — This URL returns data in JSON format. The output is a collection of the JsonSchemaFile resource instances.
• /redfish/v1/JsonSchemas/<resource URI> — The JSON Schema File resource instance describes the location (URI) of a particular Redfish schema definition being implemented or referenced by a Redfish service. This URL returns data in JSON format.
• /redfish/v1/<other resource specific URIs> — All instrumentation resources follow this pattern.