All available requests in CyberArk Privileged Account Security Web Services
Last Updated Version: v12.2
|Status Name||Status Code||Status Description|
|Success||200||The request succeeded. The actual response will depend on the request method used.|
|Created||201||The request was fulfilled and resulted in a new resource being created.|
|Bad Request||400||The request could not be understood by the server due to incorrect syntax.|
|Unauthorized||401||The request requires user authentication.|
|Forbidden||403||The server received and understood the request, but will not fulfill it. Authorization will not help and the request MUST NOT be repeated.|
|Not Found||404||The server did not find anything that matches the Request-URI. No indication is given of whether the condition is temporary or permanent.|
|Conflict||409||The request could not be completed due to a conflict with the current state of the resource.|
|Internal Server Error||500||The server encountered an unexpected condition which prevented it from fulfilling the request.|
NOTE: If you are having issues with DEL or PUT methods, make sure that your Password Vault Web Access (PVWA) Server’s IIS instance does not include WebDav Publishing. This will cause known issues.
Having trouble with CyberArk’s REST API? Check out the /r/CyberArk subreddit on Reddit!