Skip to main content

Redfish API

This section provides information about the Redfish API.

  • OData Support
    OData Properties are used to provide information about resources, such as ID, type, context, etc.accessed by a URI. The following are the properties used in Redfish.
  • Protocol Version
  • URI Query Rule
    URIs, as described in RFC3986, may also contain a query (?query) and a frag (#frag) component. Queries are addressed in the clause Query Parameters as Redfish Scalable Platforms Management API Specification DSP0266 described. Fragments (frag) should be ignored by the server when used as the URI for submitting an operation.
  • URI Rules
  • Redfish Collection
  • Authorization
    As per current implementation, Basic Auth is considered as first priority and Session Auth is considered as second priority and hence we will be returning Status Codes as below:
  • Read Requests (GET)
    The GET method is used to retrieve a representation of a resource. That representation can either be a single resource or a collection.
  • Data Modification Requests
    Clients create, modify, and delete resources by issuing the appropriate Create, Update, Replace or Delete operation, or by invoking an Action on the resource. All the data modification requests will be validated in the following order.
  • Error Response
  • Resource Properties
    This section describes the resource properties.
  • Collection Capabilities Annotation