Dell PowerStore 9000T EMC PowerStore REST API Developers Guide - Page 37

Operation POST URI pattern /api/rest// Body where: • is the resource type of the class for which you want to perform an action. • is the action you want to perform. For additional functionality, such as making the request an asynchronous request, you can append one or more request parameters to the URI. For operations without request arguments: Empty. For operations with input data: { "argument1":, "argument2":, . . . } where the comma-separated list contains all required arguments and any optional arguments. Use double quotes around a string, date-time, or ip-address value. The success response for an class-level action differs depending on whether the action performed has output data: • For actions that do not have output data, a successful request returns a 204 No Content HTTP status code and an empty response body. • For actions that have output data, a successful request returns a 200 OK HTTP status code, and the body will have the specified out attributes in a class response body. If the request does not succeed, the server returns a 4xx or 5xx HTTP status code in the response header and a message entity in the response body. Exchanging SSL certificates The following request exchanges SSL certificates with another PowerStore appliance: Headers Accept: application/json Content-Type: application/json Authorization: Request POST /api/rest/x509_certificate/exchange Request body { "service": "Management_HTTP", "address": "10.244.53.108", "port": 8080, "username": "user1", "password": "myPassword" } Response Empty. body Working with asynchronous requests By default, all REST API requests are synchronous, which means that the client/server connection stays open until the request completes and the response is returned. Creating other types of requests 37