Paged List Entity (2019/03)

the paged list entity is structured as follows entity items entity\[] entity\[] read only read only the subset of items contained only within this one page of the complete list of entities totalitemcount int int read only read only the number of requested entities contained within the whole network pagesize int int read only read only the maximum number of objects that can be contained in the response body 100 is the default and also the maximum istruncated bool bool read only read only whether or not there are additional pages in the subset if this value is true, add nextmarker in your url "marker" parameter to get the next paged subset (you can also include the "pagesize" option if the "marker" parameter is present) nextmarker string string read only read only the marker of the last item in the paged subset this value is useful if the istruncated entry in the response body indicates that the number of device webpages exceeds the pagesize sortexpression string string read only read only an expression that has been previously applied to the list of returned items note that if the customer does not supply an expression, the default expression will be calculated the sort expression specifies the entry used for sorting, and the ascending/descending (asc/desc) sorting order for example, " \[contentuploadstatus] \[starttime] asc " is the default setting for devices (by serial number in ascending order), but the default setting will change depending on what entity type is being returned by the paged list call the server will parse, validate, and clarify the expression, so the returned expression might be slightly different than the expression provided by the customer