Please refer to "How Do You Retrieve APIs Using vSphere API Explorer".
Scenarios:
If you check the “operationsmanager.log” or “domainmanager.log” you should be able to find the task for when the cluster was stretched, and it should have the entire JSON in the logs.
Other than by this method, there is no way to retrieve the JSON for the task.
See the example below of what you might find in the logs.
"clusterStretchSpec": {
"deployWithoutLicenseKeys": false,
"hostSpecs": [ {
"azName": "",
"hostName": "",
"hostNetworkSpec": {
"networkProfileName": "",
"vmNics": [ {
"id": "",
"moveToNvds": false,
"uplink": "",
"vdsName": ""
} ]
},
"id": "",
"ipAddress": "",
"licenseKey": "",
"password": "",
"serialNumber": "",
"sshThumbprint": "",
"username": ""
} ],
"isEdgeClusterConfiguredForMultiAZ": false,
"networkSpec": {
"networkProfiles": [ {
"description": "",
"name": "",
"nsxtHostSwitchConfigs": [ {
"ipAddressPoolName": "",
"uplinkProfileName": "",
"vdsName": "",
"vdsUplinkToNsxUplink": [ {
"nsxUplinkName": "",
"vdsUplinkName": ""
} ]
} ]
} ],
"nsxClusterSpec": {
"ipAddressPoolsSpec": [ {
"description": "",
"ignoreUnavailableNsxtCluster": false,
"name": "",
"subnets": [ {
"cidr": "",
"gateway": "",
"ipAddressPoolRanges": [ {
"end": "",
"start": ""
} ]
} ]
} ],
"uplinkProfiles": [ {
"name": "",
"supportedTeamingPolicies": { },
"teamings": [ {
"activeUplinks": [ "" ],
"policy": "",
"standByUplinks": [ "" ]
} ],
"transportVlan": 0
} ]
}
},