Criteria and search terms that describe the attributes assets must have to be returned, in the format criterion:search_term. To include multiple criteria, separate each search term with the query operators NOT, AND, and OR. Use parentheses to perform advanced searches by applying one criterion to multiple other search terms.
For example, let’s say you want to find assets that:

• Are tagged with the term Flower or Flowers.
• Are tagged with the term Autumn.
• Have the word “sunlit” in their description field.
• Do not include the word “cold” in their description field.
• Are images or videos.

You’d use the following query parameter:
keyword:(Flower OR Flowers) Autumn AND (CoreField.Description:sunlit NOT cold) AND (DocType:Image OR Video)
Notes:

• You can use a space ( ) instead of AND.
• For query construction details and a list of standard Orange Logic criteria, go to query construction.
• To find the specific criteria available for your organization’s Orange Logic environment, use the List Criteria API call.
• You can only include one query parameter in your call. Use operators to include multiple criteria or search terms.

The search words or phrase. This option uses Orange Logic’s AI search feature to perform the search. Orange Logic users with Link accounts can go to the AI search article to learn more.

When you use the semanticquery and query parameters at the same time, Orange Logic prioritizes search terms in this order:

1. The text and title criteria in the query parameter (if applicable).
2. The text in the semanticquery parameter.
3. Other criteria in the query parameter (if applicable).

Notes:

• When you use this parameter, 100 results are returned.

The algorithm that determines the order in which search results are returned. You can choose from these options:

• relevancy: Assets are sorted from most relevant to least relevant based on Orange Logic’s relevancy algorithm. This algorithm is based on a number of factors, such as tags in the context of the total number of tags applied to the asset, the title and description of the asset, keywords of the parent folder(s), tags extrapolated from the tag tree, and more. Each of these elements has different weightings applied to them.
• newest first: Assets are sorted from newest to oldest, based on their Create Date.
• oldest first: Assets are sorted from oldest to newest, based on their Create Date.
• editor choice: Assets are sorted from highest rating to lowest rating, based on the Editor Choice field.
• file name: Assets are sorted from A to Z, based on their filename.
• file name DESC: Assets are sorted from Z to A, based on their filename.
• file size: Assets are sorted from smallest to largest, based on their size.
• file size DESC: Assets are sorted from largest to smallest, based on their size.
• last changed: Assets are sorted from newest to oldest, based on their Date Last Edited.
• last changed ASC: Assets are sorted from oldest to newest, based on their Date Last Edited.
• indexed date DESC: Assets are sorted from newest to oldest, based on the date they were most recently indexed.
• indexed date: Assets are sorted from oldest to newest, based on the date they were most recently indexed.
• start date DESC: Assets are sorted from newest to oldest, based on the asset’s start date.
• start date: Assets are sorted from oldest to newest, based on the asset’s start date.
• manual order: Assets are displayed based on how you reordered them in the container.
• most popular: Assets are sorted from most downloaded to least downloaded.

Notes:

• When you use the sematicquery parameter, the returned values are ordered by the AI search’s relevancy score. If multiple assets have the same relevancy score, they are sorted based on the sort option selected here.
• Your organization might use legacy values for the

Response format; can be XML or JSON.