Hi everyone,
I am currently working on an integration that fetches devices (like cameras and hardware) using the MIP VMS RESTful Config API. To handle the large payloads, I am using the standard offset-based pagination with the page and size query parameters.
While reviewing the API documentation, I noticed there are no parameters exposed to specify a sorting order (e.g., sortBy or orderBy). I ran some tests to understand how the Management Server handles the ordering behind the scenes.
Specifically, I fetched devices using page=0 with size=20 and compared it against making two separate calls for page=0 with size=10 and page=1 with size=10. The results showed that the server consistently returns the items in the exact same sequence across different scenarios.
However, looking at the JSON responses, I cannot figure out what specific field or logic the server is using to sort these items by default (e.g., it doesn’t appear to be strictly alphabetical by displayName or ordered by lastModified date).
My questions are:
-
Could anyone clarify what the exact default sorting criteria is for list endpoints (like
/camerasor/hardware)? Is it based on the internal object ID, database insertion order, or something else? -
Because the dataset can shift if a device is added or deleted while we are paginating, knowing this default order will help us build a more robust sync logic to prevent missing devices or hitting duplicates.
Thanks in advance for your insights!