08-22-2025 03:42 AM
My customer keep saying that i am not using the Latest Intersight API. How do i know or verify what API version I am using .
What is the Latest Intersight API version and where to check the latest Document and know what is different/change from previous version ?
08-22-2025 05:38 AM
Are you using the SaaS version of Intersight or the on-prem connected/private virtual appliances? SaaS version everyone should be the same and you can see the schema version if you hover over the download links for the Intersight OpenAPI docs https://intersight.com/apidocs/downloads/ or in the top left corner of https://intersight.com/apidocs/apirefs/All/introduction/. The on-prem appliances would depend on the version of appliance installed.
What is the issue that's prompting you to look into the API versions?
09-01-2025 03:08 AM
Thanks Brian - Few more context . These are the list of APIs i am using ( SaaS version ) .i dowloaded schema version 2 and 3 . I don't see a difference between these version for the below APIs .Is there a way to find teh difference or changes between these schema versions?
Also is there a difference in these version in teh way we authenticate ? I currently use API key and secret key for authentication .
https://intersight.com/api/v1/organization/Organizations
https://intersight.com/api/v1/iam/Accounts
https://intersight.com/api/v1/equipment/Chasses
https://intersight.com/api/v1/compute/Blades
https://intersight.com/api/v1/equipment/FanModules
https://intersight.com/api/v1/equipment/Fans
https://intersight.com/api/v1/equipment/IoCards
https://intersight.com/api/v1/compute/RackUnits
https://intersight.com/api/v1/adapter/Units
https://intersight.com/api/v1/pci/Devices
09-02-2025 07:58 AM
Hi,
Is your customer running into some issue with the automation/extensions you have created for them that is prompting them to think it’s the API version?
If you and your customer are both using SaaS you would have the same API version. You can prove this to them by going to the apidocs (https://intersight.com/apidocs/apirefs/All/api/v1/server/Profiles/get/) and checking the API Reference on the left side of the screen on your instance versus theres.
As SaaS is always using the latest the only way to see the differences would be if you have a schema previously downloaded in the past and you ran a diff against the currently downloaded one. I’m not aware of a public repository that contains links to the previous schemas. Typically the only time I’ve seen issues is if the developer was using SaaS and the end customer had a PVA/CVA that may be a few revisions behind and didn’t yet have support for X feature that was added.
Authentication is the same as well with API key and secret keys although OAuth2 is also available if needed
11-24-2025 02:15 AM
Hi Brian - This is related to fabric interconnect under cisco intersight . Is my understanding right when it comes to the hierarchy and relation between FI , chassis and rack servers ( Check below image ) . I don't get any relationship info. as part of the FI payload . How else can i get this info. , please
11-24-2025 06:32 AM
Hi,
Correct, if you want to work downwards from the fabric interconnect level something similar to the logic in this powershell example below should work.
You'd grab /api/v1/network/ElementSummaries to get the DeviceMoID for the fabric interconnect. You would then make a second call to /api/v1/compute/PhysicalSummaries and filter for servers that have Owners set to the DeviceMoID of the fabric interconnect as well as returning an expanded Ancestors field (contains the chassis info).
$fabricInterconnect = Get-IntersightNetworkElementSummary -Filter "Serial eq 'FDO12345'"
$servers = Get-IntersightComputePhysicalSummary -Filter "Contains(Owners,'$($fabricInterconnect.Results.DeviceMoId)')" -Expand 'Ancestors'
Write-Host "Inventory for Fabric Interconnect:" $fabricInterconnect.Results.Name
foreach ($server in $servers.Results) {
Write-Host "Server Name: $($server.Name), Model: $($server.Model), Chassis Model: $($server.Ancestors.ActualInstance.Model), Chassis Serial: $($server.Ancestors.ActualInstance.Serial) "
}
Output:
Server Name: cx-imm-fi4-1-4, Model: UCSB-B200-M5, Chassis Model: UCSB-5108-AC2, Chassis Serial: FOX1907
Server Name: cx-imm-fi4-1-1, Model: UCSB-B200-M5, Chassis Model: UCSB-5108-AC2, Chassis Serial: FOX1907
Server Name: cx-imm-fi4-1-3, Model: UCSB-B200-M5, Chassis Model: UCSB-5108-AC2, Chassis Serial: FOX1907
Server Name: cx-imm-fi4-1-2, Model: UCSB-B200-M5, Chassis Model: UCSB-5108-AC2, Chassis Serial: FOX1907
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide