This page describes the operation of enumeration APIs within View.
To enumerate objects of a given resource type, use the enumeration API by calling GET against v2.0 against the resource endpoint (without specifying a GUID).
The following query parameters are supported for enumeration requests:
tokenGUIDcontinuation token for the enumerationmax-keysintmaximum number of results to retrieveskipintthe number of results to skip, useful for pagination
Results are always sorted in descending order from the CreatedUtc property.
Example
For example, to enumerate metadata rules from the configuration server, use GET /v2.0/tenants/[tenant-guid]/metadatarules. The result will be similar to the result below.
{
"Success": true,
"Timestamp": {
"Start": "2024-10-21T02:36:37.677751Z",
"TotalMs": 23.58,
"Messages": {}
},
"MaxResults": 10,
"IterationsRequired": 1,
"EndOfResults": true,
"RecordsRemaining": 16,
"Objects": [
{
"GUID": "example-metadata-rule",
... metadata rules details
},
{ ... }
],
"ContinuationToken": "[continuation-token]"
}Enumeration result objects have the following parameters:
Successboolindicating whether or not the enumeration succeededTimestampobjindicates the start time of the operation and the total milliseconds required to completeMaxResultsintindicates the maximum number of results requested. This value is 1000 by defaultIterationsRequiredintindicates the number of internal queries required to satisfy the requestEndOfResultsboolindicates whether or not the end of results have been reached. If this value istrueno further results are available. If this value isfalse, more results have been reached, and the value found inContinuationTokenwill indicate the value that should be specified in thetokenquery in subsequent requests to continue the enumerationRecordsRemainingintspecifies the number of records that remain for a subsequent enumeration at the time of the current requestObjectslistprovides the list of objects included in the enumerationContinuationTokenstringprovides a continuation token if more results exist. This value should be included in the querystring using thetokenkey for the next request