I spoke to our developers this morning and our API calls all use https, um, and 8443 in the URL they're accessing, but they're still getting 404 errors. This was working properly prior to 3.0.2.
Any other ideas?
The update to 3.1 appears to have resolved the issue.
View solution in original post
what version of vSphere are you collecting from? and can you update to Usage Meter 3.1 on this instance?
We're collecting from 5.0 (U2, I believe). And yes...I think you're right. An Upgrade to 3.1 seems to be our next step.
I was just updated: They're 403 errors, not 404.
From our developers: The API only seems to work when your computer has logged into the VMware frontend at https://[usagemeterIP]/um/. When you’re logged in through that the tokens start working and the API will work on that computer.
Thanks for letting us know.