Reference Guide
Table 2. HTTP response headers in the REST API (continued)
HTTP header Description
named DELL-EMC-TOKEN. Use the value of token from the response header obtained
from the GET call as a Header value in the subsequent calls for this session.
Content-Range Paginated responses contain this header, which indicates how many instances were
successful and how many were returned.
HTTP status codes
Every response to a REST API request includes an HTTP status code, which indicates whether the request was successful. If
requests are unsuccessful (that is, if they return 4xx and 5xx HTTP status codes) the system returns a message entity that
describes the problem.
The following table describes the HTTP status codes that apply to the REST API:
Table 3. HTTP status codes in the REST API
Status
code
Name Applies to Description
200
OK
All of the following:
● GET requests
● Action PATCH requests with
output data
● Action POST requests with
output data
Successful request.
For a GET request, the response body contains
the requested resource. For an action POST and
PATCH request, the response body contains the
output arguments.
201
Created
POST requests for creating
resources
Successful request.
The response body contains the id attribute
only.
202
Accepted
Asynchronous POST, PATCH, and
DELETE requests
Request is in process.
The response body is the ID of the job resource
instance executing the request.
204
No Content
Non-GET requests.
Successful request.
There is no body content in the response.
206
Partial Content
GET requests
Successful request.
The response body contains a partial response.
Used for pagination of a long response.
400
Bad Request
All requests
Problem with request intercepted before
execution.
The system detected a problem with the
request and did not proceed. The request may
have a badly formed URI or badly formed
parameters, headers, or body content.
401
Unauthorized
All requests
Authentication error.
The username and password combination or the
auth-cookie sent with the request are not valid.
403
Forbidden
All requests
Authorization error.
14 REST responses