VMware Cloud Foundation Operations Orchestrator API Operations Index
All available VMware Cloud Foundation Operations Orchestrator API Operations
Retrieves a specified action environment repository
Updates specified action environment repository
Deletes specified action environment repository
Retrieves a list of all action environment repositories
Creates an action environment repository
Retrieves a specified action environment
Updates specified action environment
Deletes specified action environment
Retrieves a list of all action environments
Creates an action environments
Re-installs the dependencies of the specified action environment
Updates the action with the given ID with the parameters provided in the request body
Returns the current debug context
Execute a debugger operation in the current debug context
Execute a debugger operation that changes the debug context
Retrieves a list of all actions
When a request is sent to this endpoint with "application/octet-stream" or "multipart/form-data" as the value for the Content-Type header this operation is equivalent to "Import an action in the given category":
Imports an action in a given category. The action binary content should be available as multi-part content (see RFC-2387 for details).
Details of working with multi-part resources depend on the used client's HTTP/REST library. For example, in Spring it will look like:
Sample client code:
-------------------
String url = "https://localhost:8281/vco/api/actions/";
MultiValueMapparts = new LinkedMultiValueMap ();
Resource r = new FileSystemResource("D:/path/to/some.action");
parts.put("file", Arrays.asList(r));
parts.put("categoryName", "com.vmware.basic");
new RestTemplate().postForLocation(url, parts);
-------------------
Downloads action bundle with the specified id.
Updates action bundle with the specified id.
Deletes action bundle with the specified id.
Runs an action with given category and name
Runs an action with given id
The icon's binary data is returned and response Content-type is set to correct media type, for example "Content-Type:image/png"
Retrieves logs for a given action execution. When a request is sent to this endpoint with "application/zip" as the desired response content type, this operation is equivalent to "Export all action run logs": Exports all logs for a given action execution
The returned definition contains base data for the action, as well the input parameter's definitions and the output type.
The returned definition contains base data for the action, as well the input parameter's definitions and the output type. When a request is sent to this endpoint with "application/zip" or "application/octet-stream" as the desired response content type, this operation is the equivalent to "Export an action with given id":
Exports an action by its ID. If the request is successful, the action binary content is available as an attachment with MIME type application/zip (that is, a normal ZIP file) with a default file name {actionname}.action.
It is up to the client application to properly fetch and process this attachment, i.e. by saving it to the local file system.
The exported action has the same internal format as the actions exported by using the VCF Operations Orchestrator client.
Deletes an action with a given id.
If the action is referenced by some workflows, it is considered to be 'in use'and the delete operation will fail, unless the 'force' option is provided.
Retrieves a list of dependencies for the given action
Retrieves the result of a given asynchronous action execution
Cancels a given action execution
Retrieve an VCF Operations Orchestrator's authorization group.
Update an VCF Operations Orchestrator's authorization group.
Delete an VCF Operations Orchestrator's authorization group.
Creates an VCF Operations Orchestrator's authorization group.
Delete an VCF Operations Orchestrator's authorization group.
Retrieve the VCF Operations Orchestrator's authorization groups.
Creates an VCF Operations Orchestrator's authorization group.
A REST endpoint to retrieve tags attached to an element.
A REST endpoint for attaching tag to entity.
A REST endpoint for listing all catalog entry points. Each VCF Operations Orchestrator plug-in exposes its own catalog entry point that is accessible at /catalog/{pluginname}. The VCF Operations Orchestrator server exposes a separate catalog entry point that is accessible at /catalog/System
A REST endpoint for retrieving the root elements in a namespace. All VCF Operations Orchestrator plug-ins that have an inventory, usually provide a single root element. The VCF Operations Orchestrator server does not have a single root. Instead, for the System namespace, the VCF Operations Orchestrator REST API returns a list that contains links to all system types (workflows, tasks, etc.)
If the request is successful, the API responds with an HTTP 200 OK status code and the requested list of objects
A REST endpoint for retrieving an element by its type and ID. All VCF Operations Orchestrator objects can be accessed or identified by their unique combination of namespace, type and ID.
All types that a VCF Operations Orchestrator plug-in defines, and the system types that the VCF Operations Orchestrator server defines, have default icon images. If the request is successful, the API responds with an HTTP 200 OK status code and the requested icon image as a downloadable attachment that has an 'image/png' MIME type.
Every VCF Operations Orchestrator plug-in can define relations between its types. For example, hierarchy structures can be defined as 'CHILDREN' relations between parent and children types. If the request is successful, the API responds with an HTTP 200 OK status code and a list containing the child objects that are accessible through a given relation, if any.
Plug-in metadata contains information about the types that this plug-in defines and their attributes or relations.
If the request is successful, the API responds with an HTTP 200 OK status code and the requested icon image as a downloadable attachment that has an 'image/png' MIME type.
To remove global tag form entity tag name must be prefixed with ":".
Endpoint for retrieving details for a category.
Updates the category with the given ID. The type of the category can't be changed.
Endpoint for adding child categories.
Deletes a category with a given ID.
Endpoint for retrieving all categories.
Endpoint for adding categories in root.
Retrieves the definition of a configuration. The returned definition contains base data for the configuration. When a request is sent to this endpoint with "application/vcoobject+xml" as the desired response content type, this operation is the equivalent of "Export configuration": Exports a configuration by its ID. If the request is successful, the configuration binary content is available in the body of the response message. It is up to the client application to properly fetch and process this attachment, for example, by saving it to the local file system. The exported configuration has the same internal format as the configurations exported by using the VCF Operations Orchestrator client.
Update а configuration.
Deletes a configuration with a given ID. If the configuration is referenced by some workflow it is considered to be 'in use' and the delete operation will fail, unless the 'force' option is provided.
Retrieves a list of all configurations.
Creates new configuration.
When a request is sent to this endpoint with "multipart/form-data" as the request body content type, this operation is equivalent to "Import configuration":
Imports configuration in a given category. The configuration binary content should be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client's HTTP/REST library. For example, in Spring it will look like:
Sample client code:
-------------------
String url = "https://localhost:8281/vco/api/configurations/";
MultiValueMapparts = new LinkedMultiValueMap ();
Resource r = new FileSystemResource("D:/path/to/some.vsoconf");
parts.put("file", Arrays.asList(r));
parts.put("categoryId", "828080808080808080808080808080807F818080013217004819830adebdb10ea");
new RestTemplate().postForLocation(url, parts);
-------------------
Retrieves a list of dependencies for the given configuration
Imports a workflow in a given category. The workflow binary content should be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client's HTTP/REST library. For example, in Spring it will look like:
Sample client code:
-------------------
String url = "https://localhost:8281/vco/api/content/packages/";
MultiValueMapparts = new LinkedMultiValueMap ();
Resource r = new FileSystemResource("D:/path/to/some.workflow");
parts.put("file", Arrays.asList(r));
new RestTemplate().postForLocation(url, parts);
-------------------
Returns a list of all deployed packages.
Imports a package. The package binary content should be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client's HTTP/REST library. For example, in Spring it will look like:
Sample client code:
-------------------
String url = "https://localhost:8281/vco/api/content/packages/";
MultiValueMapparts = new LinkedMultiValueMap ();
Resource r = new FileSystemResource("D:/path/to/some.package");
parts.put("file", Arrays.asList(r));
new RestTemplate().postForLocation(url, parts);
-------------------
Imports an action in a given category. The action binary content should be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client's HTTP/REST library. For example, in Spring it will look like:
Sample client code:
-------------------
String url = "https://localhost:8281/vco/api/content/packages/";
MultiValueMapparts = new LinkedMultiValueMap ();
Resource r = new FileSystemResource("D:/path/to/some.action");
parts.put("file", Arrays.asList(r));
new RestTemplate().postForLocation(url, parts);
-------------------
Returns links to entity type that can be exported, imported, or deleted from the VCF Operations Orchestrator database content. Currently, only packages, workflows, and actions are supported. Other VCF Operations Orchestrator objects, for example resources, can be imported or exported by wrapping them inside a package.
Returns a list of all deployed workflows.
Exports a package by its ID. If the request is successful, the package binary content is available as an attachment with MIME type application/zip (that is, a normal ZIP file) with a default file name {workflowname}.workflow. It is up to the client application to properly fetch and process this attachment, for example by saving it to the local file system. The exported package has the same internal format as the workflows exported by using the VCF Operations Orchestrator client.
Deletes a workflow with a given ID. If the workflow is referenced by some other workflows, or is running, it is considered to be 'in use' and the delete operation will fail, unless the 'force' option is provided.
Exports a package by its name. If the request is successful, the package binary content is available as an attachment with MIME type application/zip (that is, a normal ZIP file) with a default file name {packagename}.package. It is up to the client application to properly fetch and process this attachment, for example by saving it to the local file system. The exported package has the same internal format as the packages exported by using the VCF Operations Orchestrator client
Deletes a package with a given name. If a package has some content (workflows, actions or other elements put inside it), it is considered to be 'in use' and the delete operation will fail, unless the 'force' option is provided.
Returns a list of all deployed actions.
Export an action by its fully qualified name (category name + action name). If the request is successful, the action binary content is available as attachment with MIME type application/zip (that is, a normal ZIP file) with a default file name {actionname}.action. It is up to the client application to properly fetch and process this attachment, for example by saving it to the local file system. The exported action has the same internal format as the actions exported by using the VCF Operations Orchestrator client.
Deletes an action with a given fully qualified name. If the action is referenced by some workflows, it is considered to be 'in use' and the delete operation will fail, unless the 'force' option is provided.
Send custom event.
Retrieves the breakpoints for a workflow
Sets multiple breakpoints for a workflow
Removes all set breakpoints for a workflow
Sets a single breakpoint for a workflow
StepReturn the workflow execution
Step over the workflow execution. Moves the debugger to the next item.
Step into the workflow execution
Resumes the workflow execution
Changes the value of a variable while stopped on a breakpoint.
Evaluate a script on the current debug location of the workflow execution.
Retrieves the current global debugger state
Sets the global debugger state
Retrieves the current debugger location for a requested workflow run
Retrieve the variables in the current debug location of the workflow execution.
Retrieves the debugger mode for a requested workflow run
Applicable only for supported runtimes
Retrieves the available system features.
Retrieves the available features.
Get form by item id
Update form.
Create a form.
Delete a form.
Get form by item id
Update form.
Delete a form.
Get all forms for a workflow.
Create a form.
Execute item with a form.
Execute all items with their forms.
Get the evaluation context of an item.
Get the evaluation context of an item.
Get user interaction form.
Get user interaction evaluation context.
If the request is successful, the API responds with an HTTP 200 OK status code and a list containing the child objects that are located at this hierarchy level. The user can navigate hierarchy using 'up'/'down' links in the result. If there is no 'up' link, you are at the root level. If there is no 'down' link, you have reached a leaf object which is not a parent or other objects in this hierarchy. Depending on the level where you invoke the service, the results should be interpreted differently.
Returns a list of all logs settings.
Updates the log configuration.
Exports a package by its name. If the request is successful, the package binary content is available as attachment with MIME type application/zip (that is, a normal ZIP file) with a default file name {packagename}.package<. It is up to the client application to properly fetch and process this attachment, for example by saving it to the local file system. The exported package has the same internal format as the packages exported by using the VCF Operations Orchestrator client. When a request is sent to this endpoint with "application/xml" or "application/json" as the desiredresponse content type, this operation is the equivalent to "": Returns details of the package, with list all contained workflows and actions.
Create new package.
Deletes a package with a given name.
Takes 3 options for deleting a package:
- deletePackage - deletes the package without the content
- deletePackageWithContent - deletes the package along with the content. If other packages share elements with this package, they will be deleted
- deletePackageKeepingShared - deletes the package along with the content. If other packages share elements with this package, the elements will not be removed.
If no option parameter is provided, the default one is used: deletePackage
Update package.
Updates the version of the elements in a package
Returns a list of all deployed packages.
Imports a package. The package binary content should be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client's HTTP/REST library. For example, in Spring it will look like:
Sample client code:
-------------------
String url = "https://localhost:8281/vco/api/packages/";
MultiValueMapparts = new LinkedMultiValueMap ();
Resource r = new FileSystemResource("D:/path/to/some.package");
parts.put("file", Arrays.asList(r));
new RestTemplate().postForLocation(url, parts);
-------------------
Add all workflows from given category and its subcategories to package
Add workflow and its dependencies to package
Add all resource elements from resource category and its children to package
Add resource element and its dependencies to package
Rebuild package.
Add environment repository to package
Add environment to package
Recursive add configuration category resources to package
Add configuration element and its dependencies to package
Add action and its dependencies to package
Add all actions and its dependencies from given category to package
Analyses uploaded package file and returns details about package elements and certificate. The package binary content should be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client's HTTP/REST library. For example, in Spring it will look like:
Sample client code:
-------------------
String url = "https://localhost:8281/vco/api/packages/";
MultiValueMapparts = new LinkedMultiValueMap ();
Resource r = new FileSystemResource("D:/path/to/some.package");
parts.put("file", Arrays.asList(r));
new RestTemplate().postForLocation(url, parts);
-------------------
Imports a package based on a import specification. The package binary content should be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client's HTTP/REST library. For example, in Spring it will look like:
Sample client code:
-------------------
String url = "https://localhost:8281/vco/api/packages/";
MultiValueMapparts = new LinkedMultiValueMap ();
Resource r = new FileSystemResource("D:/path/to/some.package");
parts.put("file", Arrays.asList(r));
new RestTemplate().postForLocation(url, parts);
-------------------
Delete workflow element
Delete resource element
Delete configuration element
Delete action element
Creates a pending plug-in installation and returns the contents of the package
Retrieves all installed plug-ins
Marks the plug-ins with matching IDs. for removal
Updates the log level and/or state of matching plug-ins
Retrieves a pending plug-in installation and returns the contents of the package
Cancels a plug-in installation with a matching ID
Confirm or reject the pending plug-in install
Retrieves an installed plug-in's metadata
Marks the plug-in with matching ID for removal
Retrieves an installed plug-in's icon
Retrieves the icon of a plugin from the installation package with the provided id
Get policy
Updates the policy. Can be used to set startup behavior and priority
Delete policy
Get policy state
Updates the policy state. Can be used to start or stop a policy
Get policy template When a request is sent to this endpoint with a desired response content type of "application/vcoobject+xml", this operation is the equivalent to "Export policy template": Exports a policy template by its ID. If the request is successful, the policy template xml content is available in the body of the response message. It is up to the client application to properly fetch and process this attachment, for example, by saving it to the local file system
Update policy template
Delete policy template
Get all policies
Create policy
Get all policy templates
Create policy template
Policy information about each individual event that occurs when a policy is active. When a request is sent to this endpoint with "application/zip" as the desired response content type, this operation is equivalent to "Export all policy logs": Export all policy information about each individual event that occurs when a policy is active.
Retrieves a list of usages for the given policy template
Retrieves a list dependencies for the given policy template
Get all policies in state
The returned definition contains base data for the resource. When this endpoint is called with the MIME type of the specified resource as the desired response content type, this operation is the equivalent of "Export resource": Exports a resource by its ID. If the request is successful, the resource binary content is available in the body of response message. It is up to the client application to properly fetch and process this attachment, for example by saving it to local file system. The exported resource has the same internal format as the resource exported using VCF Operations Orchestrator client.
Update resource metadata. Mime type can't be updated separately from content.
Update resource content.
If the resource is referenced by some workflow, it is considered to be 'in use' and the delete operation will fail, unless the 'force' option is provided.
Retrieves a list of all resources.
Imports a resource in a given category. The resource binary content should be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client's HTTP/REST library. For example, in Spring it will look like:
Sample client code:
-------------------
String url = "https://localhost:8281/vco/api/resources/";
MultiValueMapparts = new LinkedMultiValueMap ();
Resource r = new FileSystemResource("D:/path/to/some.vsoconf");
parts.put("file", Arrays.asList(r));
parts.put("categoryId", "828080808080808080808080808080807F818080013217004819830adebdb10ea");
new RestTemplate().postForLocation(url, parts);
-------------------
Retrieves a list of usages for the given resource
Returns a human-readable representation of the VCF Operations Orchestrator server configuration.
Imports/exports the server configuration. The exported file is available as an attachment with MIME type application/zip. To perform an export request, an empty file must be attached to the request. Otherwise, the server tries to import a configuration.
The format of the exported or imported file is same as that of files exported or imported by using the VCF Operations Orchestrator configuration interface. The configuration binary content must be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client HTTP/REST library. For example, in Spring it will look like:
Sample client code that imports a server configuration:
-----------------------
MultiValueMapparts = new LinkedMultiValueMap https://localhost:8281/vco/api/server-configuration", parts, Void.class);();
parts.add("file", new FileSystemResource("/path/to/vco_config_file.zip"))
;parts.add("password", "secret")
;parts.add("importIdentity", Boolean.FALSE);
getRestTemplate().postForEntity("
-----------------------
Returns supported VCF Operations Orchestrator types.
Get subset of the server configuration settings
Returns supported VCF Operations Orchestrator Polyglot Runtimes.
Returns supported VCF Operations Orchestrator scripting API.
Returns supported VCF Operations Orchestrator scripting API for a plugin.
Returns supported VCF Operations Orchestrator scripting API for actions grouped by categories.
Currently, there is only one version.
The XSD schema file defines the elements and types used by the REST service. You can use it to generate stub classes (in Java or other programming language).
The XSD schema file defines the elements and types used by the REST service. You can use it to generate stub classes (in Java or other programming language)
A REST endpoint for retrieving server health status calculated on its health components (DB, authentication and etc.).
A REST endpoint for retrieving server readiness health status calculated on its health components (DB, authentication and etc.).
A REST endpoint for retrieving server liveness probe.
Redirect '/vco/api/docs' to '/vco/api/docs/index.html'
A REST endpoint for retrieving server build properties
Lists the available top-level service entry points.
Gets the configured system properties and their values
Updates the values and descriptions of the provided properties
Clears the provided system properties
Gets advanced properties and their current values.
Returned list contains users created at least one tag. Global tags are listed under system user GLOBAL.
Retrieves list of tag created by specific user. Global tags are listed under system user GLOBAL.
Removes all tags created by specified owner.
Retrieves list of tag instance created by specific user. Retrieved information is composed of reference to tagged object, tag name, tag value and is this instance global or private.
Retrieves list of tag created by current and GLOBAL users.
Retrieves list of tags created GLOBAL users and type.
Endpoint for retrieving all tasks.
Use this endpoint to schedule a new task.
Endpoint for retrieving a single task.
Use this endpoint to update an already scheduled task. If the scheduling date is changed, the original task is rescheduled. It is not allowed to update the scheduled workflow. To update the scheduled workflow, remove the current task and schedule a new one.
Use this endpoint to delete a scheduled task.
Use this endpoint to update the credentials of an already scheduled task.
Endpoint for retrieving all task executions until the current date.
Returns a list of all user interactions.
Updates the user search with the id provided in the model with the model's data. Can be used to update recent search usage.
Deletes the user search with the provided ID
Retrieves a list user searches that correspond to the provided context
The creates search is associated with the user making the request
Returns the solution user and whether the current user has admin rights as well as its member groups.
Endpoint for retrieving workflow statistics.
A REST endpoint for listing VCF Operations Orchestrator Server instance services.
A REST endpoint for getting all available users that can be used for setting permissions. If maxResult requestparameters is not used the groups returned will be limited to 50
A REST endpoint for getting all available user groups that can be used for setting permissions. If maxResult request parameters is not used the groups returned will be limited to 50
Retrieve the VCF Operations Orchestrator Server Authentication configuration type and login url.
Searches for users and groups by certain criteria.
Retrieves all workflow runs for a given workflow and filters by current user's permissions.
Creates a new instance of a workflow's run, by using the passed parameters. The workflow run is an asynchronous, so the call does not return a response body.
Retrieves user interaction details for a workflow run. If a workflow run with ID: executionId has a user interaction request, the workflow run is suspended until a user answers the interaction request. This API call returns the user interaction parameter, which has to be filled to answer it.
Answers a user interaction for a specific workflow run. If a workflow run with ID: executionId has a user interaction request, the workflow run is suspended until a user answers the interaction request. To answer a user interaction, use this API call with appropriate parameters.
Cancel an user interaction for a specific workflow run.
Retrieves a workflow run for a given workflow. When request parameter showDetails is set to true additional information will be retrieved. In this case the result contains current execution stack of the workflow run.
Deletes a specific workflow run
Provides logs generated by workflow scripting and system events.
Retrieves statistics for given workflow run.
Retrieves the current state for a requested workflow run
Cancels a workflow run
Provides information about each individual event that occurs when the workflow runs. This information includes a description of the event, the user who triggered it, the type and origin of the event, and the time and date when it occurred.
The schema data is returned and response Content-type is set to correct media type, for example "Content-Type:application/json"
Updates workflow's schema for a given workflow ID and schema
Validate provided workflow content
Get all workflows
Creates new workflow.
When a request is sent to this endpoint with "application/octet-stream" or "multipart/form-data" as the value for the Content-Type header this operation is equivalent to "Import/upload a workflow":
Imports a workflow in a given category. The workflow binary content should be available as multi-part content (see RFC-2387 for details).
Details of working with multi-part resources depend on the used client HTTP/REST library. For example, in Spring it will look like:
Sample client code:-------------------String url = "https://localhost:8281/vco/api/workflows/";MultiValueMapparts = new LinkedMultiValueMap ();Resource r = new FileSystemResource("D:/path/to/some.workflow");parts.put("file", Arrays.asList(r));parts.put("categoryId", "");new RestTemplate().postForLocation(url, parts); -------------------
Validate existing workflow by workflow id
Retrieves all scheduled tasks for a requested workflow.
Retrieves all user interactions for a requested workflow.
The returned definition contains base data for the workflow, as well the input and output parameter definitions. It also has links to the workflow presentation and workflow category in which this workflow is located.
To retrieve the input and output parameter definitions localized, add Accept-Language header, with the appropriate locale. In advance, localization resource should be present for the workflow, otherwise it defaults to the standard input and output parameter definitions.
When a request is sent to this endpoint with "" or "" as the desired response content type, this operation is the equivalent to "Export/Download a workflow": Exports a workflow by its ID. If the request is successful, the workflow binary content is available as an attachment with MIME type application/zip (that is, a normal ZIP file) with a default file name {workflowname}.workflow. It is up to the client application to properly fetch and process this attachment, for example by saving it to local file system. The exported workflow has the same internal format as the workflows exported by using the VCF Operations Orchestrator client.Retrieves a list of usages for the given workflow
The icon's schema image binary data is returned and response Content-type is set to correct media type, for example "Content-Type:image/png"
The icon's binary data is returned and response Content-type is set to correct media type, for example "Content-Type:image/png"
Retrieves a list of dependencies for the given workflow
Deletes a workflow with a given ID. If the workflow is referenced by some other workflows, or is running, it is considered to be 'in use' and the delete operation will fail, unless the 'force' option is provided.