Hi kumargandhi
With the new forwarding feature implemented in the SDK you do not even need the correct API endpoint in the UI.
All you need is the target VC for which the call is intended.
The clone-ticket can be send to any VC in the linked environment, and it will be forwarded to the VC from which vSphere Client the plugin is used. (this feature works for VCs >= 7.0u2 version)
More information on this can be found in the vsphere client docs:
https://vdc-download.vmware.com/vmwb-repository/dcr-public/009a36e4-2f17-46fc-ac27-ea9f8bf8c923/9988...
Section: How to Delegate Session Authority to the Plug-in Server
If your plugin is to work after 7.0u2 you can take advantage of this new feature. Otherwise before 7.0u2 the plugin needs to trust all vCenters in the linked environment and use the getApiEndpoint.
The getApiEndpoint is not dependent on the linked environment, basically the guid is the one which determines for which VC the vsphere client will clone the session. This means that the api-endpoint is the same no matter for which VC you need a cloned ticket.
Again it is best to use the new functionality which eliminates the need for the getApiEndpoint API call.
