[Released] Behaviour of Asset Test History API with SiteID
Posted: Mon Feb 20, 2023 2:51 pm
Whilst testing the Asset Test History API with Postman I have encountered an anomoly with the 'SiteID'.
I have found the Site ID does not make any difference to this API call only the Asset ID.
I had generated a method to iterate all my Site ID's and their respective assets but by accident when hacking the URL whilst testing I discovered the site ID appears to be irrelevant in this method.
i.e. if I call using site 445 and asset 5 (the site for asset 5) I get the same result as when I change the site to 123.
( /api/v1.0/companies/{companyID}/sites/{siteID}/assets/{assetID}/testHistory/ )
I dont really think it's causing a proplem as Assets ID's are unique just curious about the reason for this. What it does mean is that site is actually irrelevant and a place holder interger would suffice or am I missing something?
I have found the Site ID does not make any difference to this API call only the Asset ID.
I had generated a method to iterate all my Site ID's and their respective assets but by accident when hacking the URL whilst testing I discovered the site ID appears to be irrelevant in this method.
i.e. if I call using site 445 and asset 5 (the site for asset 5) I get the same result as when I change the site to 123.
( /api/v1.0/companies/{companyID}/sites/{siteID}/assets/{assetID}/testHistory/ )
I dont really think it's causing a proplem as Assets ID's are unique just curious about the reason for this. What it does mean is that site is actually irrelevant and a place holder interger would suffice or am I missing something?