AimWebservice Different behaviour between PowerShell & DotNet Http requests

I am seeing different results using the same HTTP request to the AIMWebService. Using a DotNet app Get request for a known Object results in 404 not found, the same result via Powershell results in the details being returned correctly, one this is done the DotNet App will also return the results correctly.

Note: Both PowerShell and DotNet app running from same PC. Also multiple tries with DotNet app always return 404 until the powershell is run

Found out the the Cyberark lookup on object is Case Sensitive on the safe name, but the AIM lookup from doesn’t seem to be