Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell Unity™ Family Unisphere® Management REST API Programmer's Guide

PDF

Request parameters

The REST API supports the following request parameters:

Request parameter Applicable request types Description
compact Collection query and instance query requests Omits metadata from each instance in the query response. Values are:
  • true (implied when you use &compact without a value)
  • false (default)

For more information, see Omitting metadata from responses.

fields Collection query and instance query requests Specifies a comma-separated list of attributes to return in a response. If you do not use this parameter, a query will return the id attribute only.

When using fields, you can:

  • Use dot notation syntax to return the values of related attributes.
  • Optionally, define a new attribute from field expressions associated with one or more existing attributes.

For more information, see Specifying the attributes to return in a query response, Extending queries to include related data, and Defining new attributes from existing attributes.

filter Collection query request Filters the response data against a set of criteria. Only matching resource instances are returned. Filtering is case insensitive.

When using filter, you can use dot notation syntax to filter by the attributes of related resource types.

For more information, see Filtering response data and Extending queries to include related data.

groupby Collection query request Groups the specified values and applies the @sum function to each group.

For example, you could use groupby with @sum to return a summary of disk sizes for each disk type.

For more information, see Aggregating response data.

language All request types Overrides the value of the Accept-language: header. This is useful for testing from a plain browser or from an environment where URL parameters are easier to use than HTTP headers.

The language parameter specifies the localization language for error messages, events, alerts, and other localizable responses.

Valid values are:

  • de-DE: German
  • en-US: English (default)
  • es-MX: Latin American Spanish
  • fr-FR: French
  • ja-JP: Japanese
  • ko-KR: Korean
  • pt-BR: Brazilian Portuguese
  • ru-RU: Russian
  • zh-CN: Chinese

For more information, see Localizing response text.

orderby Collection query request

Specifies how to sort response data. You can sort response data in ascending or descending order by the attributes of the queried resource type. And you can use dot notation syntax to sort response data by the attributes of related resource types.

For more information, see Sorting response data and Extending queries to include related data.

page Collection query request Identifies the page to return in a response by specifying the page number. If this parameter is not specified, the server returns all resource instances that meet the request criteria in page 1.

For more information, see Paginating response data.

per_page Collection query request Specifies the number of resource type instances that form a page. If this parameter is not specified, the server returns all resource instances that meet the request criteria in the page specified by page (or in page 1, if page is also not specified).
NOTE The server imposes an upper limit of 2000 on the number of resource instances returned in a page.

For more information, see Paginating response data.

with_entrycount Collection query request Indicates whether to return the entryCount response component in the response data. The entryCount response component indicates the number of resource instances in the complete list. You can use it to get the total number of entries when paging returned a partial response.

By default, the entryCount response component is not returned. Set with_entrycount=true to return the entryCount response component.

For more information, see Paginating response data.

timeout Most non-GET requests Executes the request in the background. Most active management requests (ones that attempt to change the configuration) support this option. The documentation for each API method in the Unisphere Management REST API Reference Guide specifies whether the method supports this option.

For more information, see Working with asynchronous requests.

To use request parameters, append the parameters to the request URI. The first request parameter appended to the URI begins with a ? character. Additional request parameters begin with & instead of ?. You can combine request parameters and can use them in any order. If a request parameter is repeated, all but the last one is ignored.

Example 1

The following request uses a fields query parameter to return the name, and rpm attributes, a filter query parameter to return disk instances that have an RPM of 15000, and a compact query parameter to omit metadata from each instance in the query response. It also sets the with_entrycount query parameter to true, so that the entry count is included in the response data. For readability purposes, this example omits URI encoding for the space character (%20) and % character (%25).

Request

GET api/types/disk/instances?fields=rpm,name&filter=rpm eq 15000&compact=true&with_entrycount=true

Response

 {
  "@base": "https://10.108.53.216/api/types/disk/instances?filter=rpm eq 15000&fields=rpm,name,id&per_page=2000&compact=true",
  "updated": "2015-12-02T21:03:14.446Z",
  "links": [
    {
      "rel": "self",
      "href": "&page=1"
    }
  ],
  "entryCount": 20,
  "entries": [
    {
      "content": {
        "id": "dpe_disk_0",
        "name": "DPE Disk 0",
        "rpm": 15000
      }
    },
    {
      "content": {
        "id": "dpe_disk_1",
        "name": "DPE Disk 1",
        "rpm": 15000
      }
    },
    {
      "content": {
        "id": "dpe_disk_2",
        "name": "DPE Disk 2",
        "rpm": 15000
      }
    },
.
.
.

Example 2

The following request uses the per_page and page query parameters to group returned disk instances into chunks of two instances per page and to return only the instances on page three. It also uses fields query parameter to return the name, pool and tierType attributes, and the compact query parameter to omit metadata from each instance in the query response:

Request

GET api/types/disk/instances?per_page=3&page=2&fields=name,pool,tierType&compact=true

Response

{
  "@base": "https://10.245.23.125/api/types/disk/instances?fields=name,tierType,id,pool.id&per_page=3&compact=true",
  "updated": "2015-11-19T22:47:53.424Z",
  "links": [
    {
      "rel": "self",
      "href": "&page=2"
    }
  ],
  "entries": [
    {
      "content": {
        "id": "dae_0_1_disk_3",
        "tierType": 20,
        "name": "DAE 0 1 Disk 3",
        "pool": {
          "id": "pool_1"
        }
      }
    },
    {
      "content": {
        "id": "dae_0_1_disk_4",
        "tierType": 20,
        "name": "DAE 0 1 Disk 4",
        "pool": {
          "id": "pool_1"
        }
      }
    },
    {
      "content": {
        "id": "dae_0_1_disk_5",
        "tierType": 20,
        "name": "DAE 0 1 Disk 5",
        "pool": {
          "id": "pool_1"
        }
      }
    }
  ]
}

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\