Hi,
The online document intro page says “The endpoint /evidenceLocks for managing evidence locks”, but we don’t see any endpoint.
Is the document missing, or its still not implemented
Thanks,
Vega
Hi,
The online document intro page says “The endpoint /evidenceLocks for managing evidence locks”, but we don’t see any endpoint.
Is the document missing, or its still not implemented
Thanks,
Vega
I found the documentation here (link included): - MIP VMS Evidence Locks API reference
Evidence locks are dynamic data, so doing
GET /api/rest/v1/evidenceLocks
is not in line with REST semantics for GET, which is expected to return static representations. My guess is that you tried this and therefore concluded there was no endpoint (forgive me if I’m guessing wrong).
Instead, you need to create a task-based search, for example:
POST /api/rest/v1/evidenceLocks?task=searchTime
This creates an evidence-lock–related task and returns the result asynchronously.
Documentation for the task-based approach is here (link included): Create an evidenceLock-related task
using RestfulCommunication sample
trying this
http://vmsaddress/api/rest/v1/evidenceLocks?task=searchTime
body
{
“devicePaths”: [
{
“type”: “cameras”,
“id”: “CE2A474F-BCAD-44FB-B23D-4CE9B14E99A4”
}
],
“page”: 0,
“size”: 500
}
always getting an empty array
We have evidence lock for the camera and can get using SDK’s MarkedDataSearch but not with API.
Are we missing anything?
Thanks,
Vega
Working with this we have now discovered a bug.
What we found is that the “size” must be in the URI.
So this works..
POST /api/rest/v1/evidenceLocks/?task=searchTime&size=500
and works with the same body as you have.
For now I hope you can use this workaround.