Solved

API endpoint to check supported API versions?


Badge +5
I didn't see this in the API explorer, but was wondering if there is a API endpoint to check what versions of the API are supported for a given Prism instance now that there are at least 4 versions of the API (0.8, 1, 2.0, 3)? Typically REST API's do this through an un-versioned enpoint such as "/version". Any chance something like this exists?

Thanks,
Andrew
icon

Best answer by ckousoulis 17 April 2018, 19:08

Yes, we're tracking the introduction of a "versions" API that sits outside of the namespace of any particular API suite. Product and API documentation describes which APIs are supported for public use, so that's your best way to determine what to code against. For now, v2 should be used against a cluster for cluster management operations, and v3 should be used against Prism Central for datacenter management operations. We're looking at service discovery as well as versioning for an API that sits outside a specific suite, which is why we haven't yet introduced a generic versions API that just points to v2/v3.

View original

5 replies

Userlevel 7
Badge +30
No, we dont have this today.

Just out of my own curiosity, do you have an example of where someone else has done this? I haven't seen it personally, and I'd love to get a point of reference
Userlevel 7
Badge +35
Hi @regana

we never heard back and wanted to know if you got what you needed.
Badge +5
As far as I know this was never resolved. Found this example after a quick Google search: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_versions.htm

We have a similar endpoint in our products REST API:

/versions will return JSON that looks like this:
code:

{
"count": 1,
"result": {
"current": "2.0",
"supported": [
"1.0", "2.0"
],
"software": "3.0.0-2554"
},
"time": "0.117mS"
}

Userlevel 7
Badge +30
We're doing something like this in the v3 APIs, but didn't launch this specific /version(s) endpoint in the 5.6 GA that just came out @ckousoulis is the man with a plan on this
Badge +5
Yes, we're tracking the introduction of a "versions" API that sits outside of the namespace of any particular API suite. Product and API documentation describes which APIs are supported for public use, so that's your best way to determine what to code against. For now, v2 should be used against a cluster for cluster management operations, and v3 should be used against Prism Central for datacenter management operations. We're looking at service discovery as well as versioning for an API that sits outside a specific suite, which is why we haven't yet introduced a generic versions API that just points to v2/v3.

Reply