Hitachi

JP1 Version 12 JP1/Operations Analytics REST API Reference Guide


1.2.6 HTTP status codes description

Status code

Name

Description

200

OK

Request processed normally

201

Created

Returned instead of 200 when a resource is successfully created

204

No Content

Returned instead of 200 when a request was successful but there is no response to return

303

See Other

Returned instead of 200 if another URI processes the request

400

Bad Request

The request is invalid. This includes invalid values specified for the query parameter.

401

Unauthorized

Notifies you that access to the resource requires authentication. The authentication method is shown in the WWW-Authenticate header. If the request including the authorization header is already applied, this code indicates that the authentication for the user information or the HSSO token was rejected. Possible reasons include incorrect user information (user ID or password) incorrect HSSO token, and a lack of rights to use JP1/OA.

403

Forbidden

The user does not have the permissions required to do the operation.

404

Not found

The specified resource or operation was not found.

405

Method Not Allowed

A valid method was not available for the specified resource. Always list the available methods.

406

Not Acceptable

The specified response format is not supported.

409

Conflict

Conflicts with other data in the server prevent the request from completing.

412

Precondition Failed

The request was not accepted because of a failure in the preconditions.

414

Request-URI Too Long

The request line is too long.

415

Unsupported Media Type

The specified request format is not supported.

500

Server-Side Error

An error occurred in a server process.

503

Service Unavailable

An error occurred on the repository server.

For the status codes of 4XX and 5XX, a response body might be returned in "text/html" or "text/plain" form. In this case, "Content-Type: text/html" or "Content-Type: text/plain" is in a response header.

Responses provide more detailed contents of errors for which causes are hard to identify only with the status codes of 4XX and 5XX.

Whether to use these status codes depend on the APIs. See the description for each API.