5.5.1

Table Of Contents
Delete the Permissions of a Workflow
You can delete the permissions of a workflow by using the Orchestrator REST API. You can delete the
existing permissions of a workflow before you set new permissions.
Procedure
1 Make a GET request and retrieve the ID of the workflow from the list of returned workflows:
GET http://{vcoHost}:{port}/vco/api/workflows/
2 Make a DELETE request at the URL of the workflow's permissions:
DELETE http://{vcoHost}:{port}/vco/api/workflows/{workflowID}/permissions/
If the DELETE request is successful, you receive the status code 204, and the response body is empty.
Set the Permissions for a Workflow
You can set the permissions for a workflow by using the Orchestrator REST API.
Prerequisites
Review the types of permissions that you can set and the syntax that you can use in the request body. See
“REST API Permissions,” on page 40.
Procedure
1 Make a GET request and retrieve the ID of the workflow from the list of returned workflows:
GET http://{vcoHost}:{port}/vco/api/workflows/
2 In a REST client application, add request headers to define the properties of the workflow for which
you want to set permissions.
3 In the request body, specify the permissions that you want to set.
4 Make a POST request at the URL of the workflow's permissions:
POST http://{vcoHost}:{port}/vco/api/workflows/{workflowID}/permissions/
If the POST request is successful, you receive the status code 201. Information about the workflow's
permissions is available in the response body.
Retrieve the Permissions of an Action
You can retrieve information about the permissions of an action by using the Orchestrator REST API.
Procedure
1 Make a GET request and retrieve the ID of the action from the list of returned actions:
GET http://{vcoHost}:{port}/vco/api/actions/
2 Make a GET request at the URL of the action's permissions:
GET http://{vcoHost}:{port}/vco/api/actions/{actionID}/permissions/
If the GET request is successful, you receive the status code 200. Information about the action's permissions is
available in the response body.
Chapter 2 Using the vCenter Orchestrator REST API
VMware, Inc. 41