Permission Requirements
Listing and getting saved searches has no role requirement. Creating, updating, deleting, favoriting, and executing saved searches on the/app/v1/ routes requires the organization admin role.
The SavedSearch Object
Parent folder ID. Omitted when the search is at the root level. Moving a search into a folder with
PUT requires the folder’s type to match the search’s type.Example Object
Relationship with Direct Search
Saved searches use the same filter structure as the direct search capabilities in the Content and Assets endpoints. The key differences are that saved searches:- Store the search criteria for reuse
- Can be shared across users within a project
- Track usage statistics
- Allow favoriting for quick access
Filter Operators
Saved searches support all standard filter operators:Sort Options
Sort criteria specify how results are ordered:- Content:
name,createdAt,updatedAt,status - Asset:
name,createdAt,updatedAt,type,size