Save, verify or refresh LST configuration
put
/rest/{version}/configuration/lst
Executes configuration management action to either verify, save or refresh LST configuration to the specified filename in the /code/lst directory. This is applied only to ECB.
Request
Path Parameters
-
version(required):
REST API version string.
Available values: v1.2
Query Parameters
-
action(required):
Specifies which action to take with the configuration. Action can be to back up a configuration to a file from a particular configuratiosource, or activate the saved configuration.
Available values: verify, save, refresh -
filename:
The filename parameter must be included and specify a valid LST filename that present in the file system in the /code/lst directory. Specifying an already existing filename will result in a failure.
Header Parameters
-
Authorization(required):
The value in the Authorization header must be the string "
Bearer {access token}
", where{access token}
is a valid, unexpired token received in response to a prior/rest/{version}/auth/token
request.
Response
200 Response
For action as 'save', OK response with response body.
204 Response
For action as 'verify' and 'refresh'. There will be no success response body.
400 Response
The request is malformed in some way or is missing required information and therefore cannot be processed.
401 Response
Unauthorized - Request lacks valid authentication credentials.
403 Response
This request requires the client credentials to have administrator privileges.
404 Response
Resource not found
423 Response
The request requires the configuration lock and failed because the client does not currently own the lock. If another client or user currently owns the configuration lock, the error message is "Resource locked by another user". If no client or user owns the configuration lock, the error message is "User does not have the lock".