Use offset in conjunction with limit for paging. The offset is the number of items from the beginning of the result set to the first item included in the response.

Use limit in conjunction with offset for paging. The limit is the maximum number of items to include in the response.

The expression to use for filtering responses. You can filter on the following properties: customerId, id, name, possibleValues, currentValue, settingDescription, lastUpdatedBy, lastUpdatedAt, externalApplicationName. You can combine multiple comparison operators using AND. The comparisons supported are the following: “eq” : Valid for number, boolean and string properties. “gt” : Valid for number or string timestamp properties. “lt” : Valid for number or string timestamp properties “in” : Valid for an array of strings Syntax: “eq” : filter= eq {host:port}/data-services/v1beta1/settings?filter= eq “gt” : filter= gt {host:port}/data-services/v1beta1/settings?filter= gt “lt” : filter= lt {host:port}/data-services/v1beta1/settings?filter= lt “in” : filter= in {host:port}/data-services/v1beta1/settings?filter= in

• Use AND to filter on multiple properties: {host:port}/data-services/v1beta1/settings?filter= eq and lt
• To filter multiple values on one property e.g. filter=name in ('foo','bar') {host:port}/data-services/v1beta1/settings?filter=foo%bar%20in%20severity Examples: GET /data-services/v1beta1/settings?filter=name eq 'SETTINGNAME' GET /data-services/v1beta1/settings?filter=name eq 'SETTINGNAME' and lastUpdatedBy eq 'CREATED' GET /data-services/v1beta1/settings?filter=relatedObjectType in ('NIMBLE-VOLUME') Filters are supported on following attributes: customerId, id, name, possibleValues, currentValue, settingDescription, lastUpdatedBy, lastUpdatedAt, externalApplicationName

The property to sort by followed by a direction indicator ("asc" or "desc"). If no direction indicator is specified the default order is ascending.