- Notes, cautions, and warnings
- Additional resources
- Welcome
- REST API overview
- JSON request components
- JSON response components
- JSON encodings
- Preparing to make a request
- Querying a resource
- Retrieving data for multiple occurrences in a collection
- Retrieving data for a specified resource instance
- Omitting metadata from responses
- Specifying the attributes to return in a query response
- Paginating response data
- Filtering response data
- Sorting response data
- Aggregating response data
- Defining new attributes from existing attributes
- Extending queries to include related data
- Localizing response text
- Creating other types of requests
- Downloading and uploading files
- Downloading and uploading NAS server configuration files
- Downloading and uploading x.509 certificates
- Downloading configuration capture files
- Downloading service information files
- Downloading import session report files
- Downloading Data at Rest Encryption files
- Uploading upgrade candidates and language packs
- Uploading license files
- Perl example
Dell Unity™ Family Unisphere® Management REST API Programmer's Guide
HTTP request headers
The following table describes the HTTP request headers that are used by the Unisphere Management REST API. The API uses these headers in standard ways.
| HTTP header | Value | Description |
|---|---|---|
| Accept: |
application/json; version=<n.n>
where <n.n> is the version number for the desired response. |
Format and version of the body content desired in the response.
All requests use Accept: application/json, which is the default and only value accepted. If the Accept header is not specified, the system defaults to the current version. If the client requests a version that the server does not support, the server returns an error. If the client requests multiple versions, the server returns the latest supported version that was requested. |
| Accept-language: | Locale name | Localization language for error response messages, events, alerts, and other localizable query results.
Valid values are:
NOTE Support for all supported locales except en-US requires the installation of language packs.
If the requested dialect is not available, the API tries to match on the language, alone. For example, de-AA will match with de-DE. If the API cannot find a match, it uses en-US instead of returning an error message. For more information, see Localizing response text. |
| Content-type: | application/json | Body content type of the request. |
| Set-Cookie: | Login session ticket | Because the API uses cookie-based authentication, the HTTP client must support cookies in order to use the API. More than one cookie may be required to use the REST API.
For more information, see Connecting and authenticating. |
| EMC-CSRF-TOKEN: | <token> | CSRF token used to mitigate Cross-Site Request Forgery vulnerabilities. The token is gathered from a
GET response and required to send with
POST and
DELETE requests. The token is good for the entirety of the session.
For more information, see Connecting and authenticating. |
| X-EMC-REST-CLIENT: | true | Required to send in all requests if using Basic authentication.
For more information, see Connecting and authenticating. |
| Application-Type: | <plugin name>/<plugin version> | Optional. REST client name and version. |
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: <>()\