This post is about vRealize Operations Tenant App API documentation reference to help you know what can be done with the API
Tenant APP 8.6 API can be integrated with other solutions and but APIs are not documented in code.vmware.com and vRealize Operations API reference is for version 6.7
API Reference Index for VMware products on this link
The latest version of VMware vRealize Operations is 8.6 released on 2021-10-12 as was announced here
VMware vRealize Operations is 8.6 can be downloaded here
vRealize Operations Tenant App for VMware Cloud Director 8.6 can be downloaded here
Tenant APP API Documentation
For the complete Swagger API JSON file check our GitHub link below
Understanding vRealize Operations Tenant App API
Excerpt of “Using vRealize Operations Tenant App for vCenter as a Service Provider” about using Tenant APP API as published here is below
Service Providers can use the API to build interactive clients of vRealize Operations Tenant App. The API follows the REST style and is available to all licensed users.
The Tenant App clients communicate with the server over HTTP, exchanging representations of Tenant App objects. These representations take the form of JSON elements. You use HTTP GET requests to retrieve the current representation of an object, HTTP POST, and PUT requests to create or modify an object, and HTTP DELETE requests to delete an object.
How the Tenant App API Works
Use a web browser to communicate with the vRealize Operations Tenant App analytics engine, either through the product user interface or through API calls.
The adapter instance collects data from objects in your monitored environment. The Tenant App analytics engine processes the data and displays the complete model in the graphical interface.
Why Use the API
The API is most useful when there is a need to automate a well-defined workflow, such as repeating the same tasks to configure the access control for new Tenant App users. The API is also useful when performing queries on the Tenant App data repository, such as retrieving data for particular assets in your virtual environment. In addition, you can use the API to extract all data from the Tenant App data repository and load it into a separate analytics system.
vRealize Operations Tenant App Terminology
The JSON syntax you use to describe the objects for an adapter corresponds to the API code syntax but differs from what you find in the user interface. The following terms appear in the user interface. Included with the description of each term is the corresponding JSON syntax used in an API call.
| Adapter types | Defines the adapter used to discover particular object types. For example, the vCenter adapter discovers objects connected to vSphere data centers. The EMC adapter discovers EMC storage system objects. JSON syntax: adapterkinds. |
| Object types | The class of entities that represent objects or information sources. Objects report data to the vRealize Operations Manager analytics engine. Virtual machines, datastores, and host systems are examples of object types defined in a vCenter adapter model. JSON syntax: resourcekinds. |
Getting Started with the API
API clients and Tenant App servers communicate over HTTPS, exchanging JSON representations of API objects.
Acquire an Authentication Token
The Tenant App requires API requests to be authenticated. The first step in this workflow is to obtain an authentication token.
To obtain an authentication token, the login request supplies the user credentials in a form that Basic HTTP authentication requires. In this example, the user is logging in to a Tenant App instance with URL https://tenantapp.example.com/.
Procedure
1 POST a request to the login URL to acquire a token.
POST https://tenantapp.example.com/suite-api/api/auth/token/acquire2 Examine the response.
A successful request returns an ops authorization token, which you must include in subsequent API requests.
This example shows a request and response for a user with login user name: tenantapp-user and password: tenantapp-dummy-password.
Request header:
POST https://tenantapp.example.com/suite-api/api/auth/token/acquire Content-Type: application/json
Accept: application/jsonRequest body in JSON format:
{
"username" : "tenantapp-user", "password" : "tenantapp-dummy-password"
}Response in JSON:
200 OK<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ops:auth-token xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ops="http://webservice.vmware.com/vRealizeOpsMgr/1.0/">
<ops:token>898fcd3e-ca04-40bb-9088-d941f9cd8c3e::591dfe08-887e-4d37-ad5d-f68bf73aad9b</ops:token>
<ops:validity>1634800980121</ops:validity>
<ops:expiresAt>Thursday, October 21, 2021 8:23:00 PM NZDT</ops:expiresAt>
<ops:roles/>
</ops:auth-token>
The response code indicates whether the request succeeded, or how it failed.
- If the request is successful, the server returns HTTP response code 200 (OK) and reusable ops authorization token that expires after six hours. This token must be included in each subsequent API request.
- If the credentials supplied in the POST body are invalid, the server returns HTTP response code 401.
What to do next
The obtained token must be included in each subsequent API request as the Authorization header.
Include the Authorization header in the format: vRealizeOpsToken <token value>.
If the token supplied in the Authorization header is invalid or expired, the server returns HTTP
response code 401For information on individual APIs, open the tenant app api documentation url in the format:
https://tenantapp.example.com/tenant-app-api/swagger-ui-htmlWe hope this post is useful. If you want more information, send us your comment using the button below.