List Asset Filters
Listing, Sorting and Filtering Asset Filters
This endpoint returns the list of asset filters in the specified project.
Sorting
The results from this endpoint can be ordered using the $orderby query parameter. Specify a list of field names, separated by commas
where each one can optionally specify asc or desc.
Sorting is valid on the following fields: created, createdBy, id, name, updated, updatedBy
Filtering
The $filter query parameter allows for asset filters to be filtered on the basis of fields in the schema using OData query syntax.
See this document for more details on the syntax used.
Filters are valid on the following fields: created, createdBy, createdByEmail, createdByName, id, name, updated, updatedBy, updatedByEmail, updatedByName
Examples:
?$top=10 - Returns only the first 10 asset filters from the list.
?$orderby=name desc - Sorts asset filters by name in descending order.
?$filter=name eq 'descriptive name' - Returns asset filters that match the provided name.
?$orderby=created desc - Sorts asset filters by creation date in descending order.
?$filter=created ge 2021-01-01T00:00:00Z - Returns asset filters created after January 1, 2021.
RBAC Capability Required: ams.assetfilter.get
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Query parameters
Specifies a non-negative integer n that limits the number of items returned from a collection.
The service returns the number of available items up to but not greater than the specified value n.
Specifies a start offset to support paginated results.
Use @odata.nextLink in the result object to enumerate the collection -
it will be present only if there's more than one page of entities.
Response
@odata.nextLink URL if the page length and number of items match.