Reference Guide

Request
body
(Optional)
{
"description": "DB copy before application upgrade"
}
Response
body
{
"id": "57cdb822-490e-4755-b8b3-99bb779b1472"
}
Performing a class-level action
Some resource types have operations that let you perform class-level actions. For example, exchanging SSL certificates with
another PowerStore appliance.
To perform a class-level action, use the following request components:
Headers For operations without request arguments:
Accept: application/json
Authorization: <auth_cookie>
For operations with request arguments:
Accept: application/json
Content-Type: application/json
Authorization: <auth_cookie>
Operation
POST
URI
pattern
/api/rest/<resource_type>/<action_name>
where:
● <resource_type> is the resource type of the class for which you want to perform an action.
● <action_name> 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.
Body For operations without request arguments:
Empty.
For operations with input data:
{
"argument1":<value>,
"argument2":<value>,
.
.
.
}
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.
40
Creating other types of requests