DEVELOPER CENTER
Hi Team,
Please add the id field to the response of:
GET /api/v1.0/companies/{companyID}/sites/{siteID}/assets/{assetID}/testHistory/
This is currently the only endpoint that reliably returns a complete list of test history records for an asset, but it's also the only one that doesn't expose each record's own ID.
The alternative /testHistories/ endpoint does return the test history ID, but it doesn't reliably return all records. We've confirmed that it omits untested/"No Test" assets and, in some cases, records that are clearly visible in the Simpro UI return no data (support ticket 1376693).
The /testHistories/{testHistoryID} endpoint requires the test history ID up front, making it impossible to use unless that ID has already been obtained elsewhere.
As a result, when a test result ID is surfaced elsewhere in Simpro (for example, in Simpro Mobile), there's currently no reliable way for an integration synchronising via the per-asset testHistory endpoint to map that ID back to the corresponding test record.
Adding the id field to the per-asset testHistory response would resolve this limitation while preserving the reliability of the existing endpoint. It would also bring the response into line with the other test history endpoints and enable integrations to correlate records consistently across the platform.
Regards
Include (Test Result) ID in the per-asset testHistory endpoint response
Forum rules
- Check the documentation first. Before posting questions, please check the documentation to ensure it doesn't already cover what you need.
- No spam. All automated messages, advertisements, and links to competitor websites will be deleted immediately.
- Post in relevant sub-forums only. Messages posted in the wrong topic area will be removed and placed in the correct sub-forum by moderators.
- Respect other users. No flaming or abusing fellow forum members. Users who continue to post inflammatory, abusive comments will be deleted from the forum after two warnings are issued by moderators.
- Harassment. No threats or harassment of other users will be tolerated. Any instance of threatening or harassing behavior is grounds for deletion from the forums.
- Adult content. No profanity or pornography is allowed. Posts containing adult material will be deleted.
- Bandwidth. All images and signatures must be 500 x 500 pixels or smaller. Posts containing over-sized images and signatures will be removed.
- Illegal content. No re-posting of copyrighted materials or other illegal content is allowed. Any posts containing illegal content or copyrighted materials will be deleted.
-
SimproAPITeam
- Posts: 831
- Joined: Wed May 01, 2024 2:31 am
Re: Include (Test Result) ID in the per-asset testHistory endpoint response
Hi,
Thanks for the detailed write-up — that's a clear and reasonable request.
Adding the id field to the per-asset test history response (GET /api/v1.0/companies/{companyID}/sites/{siteID}/assets/{assetID}/testHistory/) so it aligns with the other test history endpoints is a sensible enhancement, and the use case you've described — correlating records surfaced elsewhere (e.g. Simpro Mobile) back to this endpoint — makes sense.
To get this tracked and considered for development, please submit it via our product portal here:
https://helpguide.simprogroup.com/artic ... uct-portal
This allows it to be visible, voted on, and prioritised alongside other requests.
Regarding the reliability issues you've noted with the /testHistories/ endpoint (missing untested assets and records not returned despite being visible in the UI) — it's good that this has already been raised under a support ticket, so that will continue to be investigated separately.
,Regards
Thanks for the detailed write-up — that's a clear and reasonable request.
Adding the id field to the per-asset test history response (GET /api/v1.0/companies/{companyID}/sites/{siteID}/assets/{assetID}/testHistory/) so it aligns with the other test history endpoints is a sensible enhancement, and the use case you've described — correlating records surfaced elsewhere (e.g. Simpro Mobile) back to this endpoint — makes sense.
To get this tracked and considered for development, please submit it via our product portal here:
https://helpguide.simprogroup.com/artic ... uct-portal
This allows it to be visible, voted on, and prioritised alongside other requests.
Regarding the reliability issues you've noted with the /testHistories/ endpoint (missing untested assets and records not returned despite being visible in the UI) — it's good that this has already been raised under a support ticket, so that will continue to be investigated separately.
,Regards
Simpro API Team | Simpro Software Group