VMware Cloud Community
FGShepherdP10
Enthusiast
Enthusiast
Jump to solution

API Collection Fails on 3.0.2

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?

Labels (1)
Tags (3)
Reply
0 Kudos
1 Solution

Accepted Solutions
FGShepherdP10
Enthusiast
Enthusiast
Jump to solution

The update to 3.1 appears to have resolved the issue.

View solution in original post

Reply
0 Kudos
6 Replies
IamTHEvilONE
Immortal
Immortal
Jump to solution

what version of vSphere are you collecting from?  and can you update to Usage Meter 3.1 on this instance?

Reply
0 Kudos
FGShepherdP10
Enthusiast
Enthusiast
Jump to solution

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.

Reply
0 Kudos
FGShepherdP10
Enthusiast
Enthusiast
Jump to solution

I was just updated: They're 403 errors, not 404.

Reply
0 Kudos
FGShepherdP10
Enthusiast
Enthusiast
Jump to solution

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.

Reply
0 Kudos
FGShepherdP10
Enthusiast
Enthusiast
Jump to solution

The update to 3.1 appears to have resolved the issue.

Reply
0 Kudos
dbriccetti
Hot Shot
Hot Shot
Jump to solution

Thanks for letting us know.

Reply
0 Kudos