It’s also important to note that the available API endpoints in vSphere 6.7 are:

In vSphere 6.7, API Explorer was moved to the Developer Center which allowed for APIs to be executed directly from within the vSphere Client versus using the older method of vSphere 6.5. In the past, it was recommended to browse to (this method is still valid in vSphere 6.5, 6.7, and 7.0) login with the vSphere SSO Domain administrator credentials, then browse and use the APIs of a selected endpoint. Accessing API Explorer has changed since its inception.

The first thing noticeable is an updated Overview page describing Developer Center in more detail than in past vSphere versions and also highlighting its capabilities.ĪPI Explorer was introduced in vSphere 6.5 and allows customers to browse and invoke vSphere REST APIs and provides information about the API endpoints. While in the vSphere Client the Developer Center shows off API Explorer & Code Capture as it did in vSphere 6.7, but with a few enhancements. Let’s start with Developer Center, a single point of entry for developers and vSphere Admins that provides tools to manage and test APIs as well as capturing vSphere Client actions into usable code snippets. I’d like to shine a light on all three of them in this post. There are some enhancements to the vSphere APIs, Code Capture, and the vSphere Developer Center features that make those easy-to-use tools even more powerful for people interested in automating their environments. VMware vSphere 7 has been extremely popular since its release, bringing many new enhancements and features to virtual infrastructure (we’ve highlighted many of the updates on this blog!).

Replay media catcher 7 code