Search API

Overview

The Cloudinary API search method allows you fine control on filtering and retrieving information on all the assets in your account with the help of query expressions in a Lucene-like query language. A few examples of what you can accomplish using the search method include:

• Searching by descriptive attributes such as public ID, filename, folders, tags, context, etc.
• Searching by file details such as type, format, file size, dimensions, etc.
• Searching by embedded data such as Exif, XMP, etc.
• Searching by analyzed data such as the number of faces, predominant colors, auto-tags, etc.
• Requesting aggregation counts on specified parameters, for example the number of assets found broken down by file format.

The search method is part of the Admin API. See the documentation for more information on authentication, pagination, error handling and usage limits.

IMPORTANT: This functionality is available only to customers with the Advanced Extra plan or higher. Contact us to activate this feature for your account.

Quick example

Find images tagged with 'kitten', that have been uploaded within the last day, and are larger than 1MB in size. In the response, sort the results by public_id in descending order, and limit the returned results to 30 resources:

Cloudinary::Search.expression('resource_type:image AND tags=kitten AND uploaded_at>1d AND bytes>1m').sort_by('public_id','desc').max_results(30).execute

Tiers

The search capabilities described here are available to customers with the Advanced Extra plan or higher. The search functionality is furthermore divided into 2 tiers:

• Tier 1 includes support for using the search method with a large selection of fields, operators, and search syntax.
• Tier 2 includes extra search functionality at an additional cost, including support for search expressions based on image analysis and metadata fields as well as support for aggregated counting information in the response. Functionality that is limited to tier 2 is noted as such. Please contact support to activate this option.

Note: All customers have access to the basic search (listing) functionality as described in the Browse resources section of the Admin API documentation.

Syntax

Cloudinary::Search.execute

new \Cloudinary\Search()->execute();

cloudinary.api.search().execute()

cloudinary.v2.search.execute(function(error, result) {console.log(result)});

cloudinary.search().execute(ObjectUtils.emptyMap());

GET https://api.cloudinary.com/v1_1/<cloud_name>/resources/search

Parameters

All the parameters of the search method are optional. Including no parameters in the method call will return the 50 most recently created resources in descending order of creation time.

• expression - The (Lucene-like) string expression specifying the search query. If this parameter is not provided then all resources are listed (up to max_results). For details, see the expressions section below.
• sort_by - An array of key value pairs where the key is the field to sort by and the value is the direction. Valid sort directions are asc or desc (the default value). If this parameter is not provided then the results are sorted by relevance (results with higher relevance are listed first). You can specify more than one sort_by parameter; results will be sorted according to the order of the fields provided.
• max_results - The maximum number of results to return. Default 50. Maximum 500.
  
• next_cursor - When a search request has more results to return than max_results, the next_cursor value is returned as part of the response. You can then specify this value as the next_cursor parameter of the following request.
• with_field - The name of an additional asset attribute to include for each asset in the response. Possible value: context, tags, and for Tier 2 also image_metadata, and image_analysis.
• aggregate - (Tier 2 only) The names of fields (attributes) for which aggregation counts should be calculated and returned in the response. Supported parameters: resource_type, type, pixels (only the image assets in the response are aggregated), duration (only the video assets in the response are aggregated), format, and bytes. For aggregation fields without discrete values, the results are divided into categories. For example:
  • bytes are divided into small (<500 kb), medium (500 - 5mb), large (5mb - 100 mb), and huge (>100 mb).
  • Video duration is divided into short (< 3 minutes), medium (3-12 min), and long (> 12 min).

Examples

1. Find assets containing 'cat' in any field (attribute), include context metadata and tags in the details of each resource, and limit the returned results to 10 resources:

   Cloudinary::Api.search.expression('cat').with_field('context').with_field('tags').max_results(10).execute

2. Find assets containing 'cat' in any field but not 'kitten' in the tags field, sort the results by public_id in descending order, and calculate an aggregation count based on the values of the format field:

   Cloudinary::Api.search.expression('cat -tags:kitten').sort_by('public_id','desc').aggregate('format').execute

For more examples of expressions, see the expression examples section below.

Response

The response includes the total count of assets matching the search criteria, the time taken to process the request, any aggregation counts requested (tier 2 only), and the details of each of the assets (resources) found.

Sample JSON Response:

{
  "total_count": 32,
  "time": 30,
  "aggregations": {
    "format": {
      "png": 4,
      "jpg": 21,
      "mp4": 3,
      "doc": 4
    }
  },
  "next_cursor": "b16b8bd80426df43a107f26b0348",
  "resources": [
  {
    "public_id": "sample",
    "folder": "",
    "filename": "sample",
    "format": "png",
    "version": 1492606756,
    "resource_type": "image",
    "type": "upload",
    "created_at": "2017-04-03T09:56:49+00:00",
    "uploaded_at": "2017-04-19T12:59:16+00:00",
    "bytes": 3381,
    "backup_bytes": 16905,
    "width": 241,
    "height": 51,
    "aspect_ratio": 4.7254901960784315,
    "pixels": 12291,
    "context": {},
    "image_analysis": { 
      "face_count": 0,
      "faces": [],
      "grayscale": true,
      "illustration_score": 1,
      "transparent": false,
      "colors": {
        "gray": 96.7
      }
    },
    "url": "http://res.cloudinary.com/demo/image/upload/v1492606756/sample.png",
    "secure_url": "https://res.cloudinary.com/demo/image/upload/v1492606756/sample.png",
    "status": "active",
    "access_mode": "public"
  },
  {
    "public_id": "dog",
     …
     …
  }
  …
}

Expressions

The expression parameter in the search method describes the query string for filtering the assets in your account. A query string contains search terms that can be combined with Boolean operators to form a more complex query. You can also limit your search to specific fields or you can run your query on all fields.

If your search term contains a space or other reserved characters such as a colon, place the search term in quotes. For example, "hello dolly" or "16:9"

You can also append an asterisk to the end of your search term in order to look for the search term as a prefix. For example, to search for "cat", "cats" or "catfish", you can use the search term:

cat*

Fields

By default, the term is searched for in all the asset's string fields, except for strings with a value that is limited to a fixed list (e.g. access_mode is limited to the values 'public' or 'authenticated'). The search can be confined to a specific field (including fields not automatically included in the default search) by typing the field name followed by a colon : (or other relevant operator) and then the term you are looking for. For example, if you want to find assets of type "authenticated":

type:authenticated

Field names are case sensitive. For a list of supported fields, see the Expression fields reference.

Field operators

When using fields in your query, you need to indicate the relationship between the search value and the field. For example, whether you are searching for assets where the field value is greater than, less than, or equal to the value you specify. The following operators are supported: : = > >= < <= [ ] { }

The supported operators and values you can use for a particular field depend on the type of that field, as detailed in Field types and supported operators.

String operators - exact or tokenized searches

Using the = operator finds a match where the value is an exact match, whereas using the : operator finds a match where the value matches any complete token within the string value (e.g., whitespace within the string value breaks it up into individual tokens (or words)). For example:

tags=cat

Finds a match only when the tag equals cat

tags:cat

Finds a match as long as one of the tokens in a tag entry includes cat, for example, a tag value of "cat and dog" returns a match but "catfish" doesn't.

Notes:

• Some string fields support only exact matches. In these cases, even if you use a : operator, it will still behave as an exact match search. Fields that support exact match only are indicated in the Expression fields reference table.
• The values of some string fields are case-sensitive, and some are a combination: case-sensitive when performing an exact (=) search and case-insensitive when performing a tokenized (:) search. Those that support exact match only are usually case-sensitive, while free text fields are either case-insensitive or a combination. The case sensitivity of each string field is indicated in the Expression fields reference table.

Range operators - inclusive or exclusive ranges

To search for a value that falls within a specific range, enclose the range values within square brackets to include the specified values or within curly brackets to exclude the specified values, and separated with the TO operator. For example, to find assets with a file size within the range 1000 to 20000 bytes:

bytes:{1000 TO 20000}

You can also search for an alphabetic range, using any alphanumeric characters in your range query, for example, searching for public_ids with names that are alphabetically between "a" and "mz":

public_id:[a TO mz]

Boolean Operators

Boolean operators allow search terms to be combined through logic operators. Note that Boolean operators must be ALL CAPS.

Notes:

• Use parentheses to group terms to form sub-queries. This can be useful if you want to control the boolean logic for a query. For example, to search for either "cat" or "lion", and "animal" use the query:

  (cat OR lion) AND animal

• If only a single term is used in the expression without an operator then the + operator is implied. For example, the following expressions are identical:

  animal
  +animal

• If part of the query evaluates to 'must have', either by using the + operator or by an intersection of 2 terms with the AND operator, then any additional terms linked with the OR operator will only be used for prioritizing the order of the results. For example, to search for "animals" and prioritize results that also have "cats":

  +animals OR cats
  +animals cats

Expression examples

1. Assets containing "shirt" and with a tag that exactly matches "cotton":

   shirt AND tags=cotton

2. Images with a width between 200 and 1028, and an aspect_ratio of 16:9:

   resource_type:image AND width:{200 TO 1028} AND aspect_ratio:"16:9"

3. Originally created before January 15th 2017 and uploaded (overwritten) between 1 and 4 weeks ago:

   created_at<2017-01-15 AND uploaded_at:[1w TO 4w]

4. Uploaded less than 2 days ago and still pending moderation:

   uploaded_at>2d AND moderation_status:pending

5. PNG images with some transparency:

   format:png AND transparent:true

6. Images with more than 2 faces:

   resource_type:image AND face_count>2

7. Images larger than 10 MB or videos longer than 3 minutes:

   (resource_type:image AND bytes>10000000) OR (resource_type:video AND duration>180)

Expression Fields Reference

You can use the following fields to limit your search criteria. The operators that you can use with a field depend on the field's value type. For details, see Field types and supported operators. You can use all fields for all resource types (image, video, raw) unless otherwise specified. Additionally, all string fields support both exact and tokenized search unless otherwise specified.

Field types and supported operators