The vRealize Automation REST API provides consumers and administrators access to all services in its service catalog that support the vRealize Automation user interface. All services have a set of use cases that can be achieved programmatically by using these REST APIs. vRealize Automation 7.1 and later documents these APIs in swagger format. We have prepared a set of API samples to help accelerate a developer's ability to consume and integrate vRealize Automation programmatically.

• Postman Rest Client
• (Optional but recommended) Learn how to use Postman, it is quite simple.

• Import vRA - Postman Environment.postman_environment.json
• Define Postman environments
  • va-fqdn: Hostname/IP for the Cafe virtual appliance (or load balancer), No HTTPS, just FQDN/IP. If no default port then suffix with ":port"
  • username: A tenant user with the format of username@domain
  • password: The password for the above username
  • tenant: The tenant for which the APIs are executed.
  • page: Default page when more than one page is returned in a GET call
  • limit: Page limit, It limits the number of objects returend in per page
  • system-user: A system level user e.g. [email protected]
  • system-password: The password for system level user
  • system-tenant: The system tenant e.g. vsphere.local
• Select "vRA - Postman Environment in Postman"

Example:

* va-fqdn: vra-prod.company.com
* username: [email protected]
* password: ...
* tenant: prod
* system-user: [email protected]
* system-password: ...
* system-tenant: vsphere.local

You can import the folder or the individual collection in the folder.

These API samples are created on top of vRealize Automation 7.3. Any version specific samples can be found under the respective release tag.

Most of the vRealize Automation API calls are authorized by relevant roles. Before executing any API, make sure you login with relevant user authorized to perform the operation. Each of these use cases should have a login method. Send a login call after setting postman environment and it will retrieve the token and will set in environment variable in Postman. There is no need to copy the token over to next API method authorization header as all the APIs headers are set. Here are the steps:

Set environment in Postman

Login

Use any of the Login calls available in samples collection.

When login is successful the environment variable {{token}} will be set.

Subsquent API Calls

Once the token is acquired, you can make subsequent calls as below. The {{token}} will be automatically passed to the request as acquired by login call.

Some API calls may require you to replace variables in URLs, request body etc. All variables are formatted as {{variable-name}}. You should replace them with a desired value before executing the method. You do not need to replace environment variables that you define as described above.

Before - The call in the postman collection will be:

https://{{va-fqdn}}/catalog-service/api/consumer/resources?$filter=owners/ref eq '{{username@domain}}'&page={{page}}&limit={{limit}}

After - you just need to replace {{username@domain}} with desired value.

https://{{va-fqdn}}/catalog-service/api/consumer/resources?$filter=owners/ref eq '[email protected]'&page={{page}}&limit={{limit}}

• Expand documentation of these use cases with Postman's guidelines.
• Please read the respective README.md file for each folder what use case are provided as samples.

The vra-api-samples-for-postman project team welcomes contributions from the community. Before you start working with vra-api-samples-for-postman, please read our Developer Certificate of Origin. All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch. For more detailed information, refer to CONTRIBUTING.md.

All files are released under the terms of the MIT License, see the LICENSE file in the root of this project.