com.vmware.vapi.rest.httpNotFound after successful login (vCenter 6.0 Update 3c REST API)

[aenagy]

After trying to follow this (vSphere Automation REST API Postman Resources and Samples - Samples - VMware {code} ) and this (Kyle Ruddy - Get Started Making vSphere API Calls the Easy Way with Postman - YouTube ) I am stuck. I have been able to install Postman, import the JSON files, create a environment for vSphere (vCenter Server Appliance 6.0 Update 3c build 7037393) (using FQHN) and authenticate. The result from the Login is:

{
    "value": "214c5126c0ff010024798b861374b708"
}

... and a "vmware-api-session-id" cookie has been created. So far, so good. The problem is that if I now try something simple like get a list of datacenters|hosts|vms then the result is always:

{
    "name": "com.vmware.vapi.rest.httpNotFound",
    "localizableMessages": [
        {
            "defaultMessage": "Not found.",
            "id": "com.vmware.vapi.rest.httpNotFound"
        }
    ],
    "majorErrorCode": 404
}

I have tried both "Inherit from parent" and "Basic" for Authorization TYPE. In both cases the results are the same. The credentials I am using allow me to login to the Web Client with no problems.

What else can/should I try?

[hespino2]

Hola que tal?, te cuento que a mi me pasa lo mismo, pero descubri que al realizar la misma consulta pero a una Vcenter con version 6.5, esta funciona como debe. Estoy verificando com solucionar esto. Te contare si se de algo. Saludos. Heber.

[aenagy]

hespino2​:

The client has no immediate plans, that I know of, to upgrade to vSphere 6.5.

(Google translate is really handy.)

[daphnissov]

vSphere 6.0 did not have, to my knowledge, any RESTful API available.

EDIT: It was limited to Content Library and Tagging in 6.0. It was further expanded in 6.5 to encompass basic VM workflows as indicated here. The error message you see (or saw) indicates that resource is not available.