List assets

List all assets in your account, optionally filtered by creation date, job type, or search criteria. Supports pagination and sorting. Each asset is identified by its asset_id (the asset’s GUID).

Sample Use Cases

• Populate a media library or dashboard with recent content.
• Search for assets created in a specific window or with a particular external ID.
• List only assets in a specific state (e.g., ready) or job type (e.g., live, clip).

Authentication

API Scopes:
  - video.services.assets:read
  - video.services.assets:write

## Using Content Search

Basic Search

A simple search will query the following fields: id, desc, and external_id.

Operators

We provide operators to search on specific indexed fields. The following operators are currently available:

id: Search on the _id field.

name: desc: title: Search on the desc field.

cms_type: Search by content type. Valid values of cms_type are clip, event, event_active, file, and live

external: ext: external_id: Search on the external_id field.

meta: Search meta data. You can search all values, or specify a key with key=. See examples below.

state: Search by that state of the asset. Valid values of state are ready, slicing, error, and encoding.

Operators must be immediately followed by a colon :. There can be a space after the colon, or no space.

Special Characters

Double quotes "" Surrounding a phrase in quotes will do a phrase specific search to give you better results.

Minus - Negates a word, for example, if you add -test to a query, it will exclude any results with the word test. You can combine this with quotes to negate phrases.

Plus + Adding the plus symbol before a word or phrase (phrases must be in quotes) will ensure that word or phrase is included in the result set.

Asterisk * This will do a wildcard or substring search. This can be helpful when looking for an ID and you don't want to type the whole ID.

Comma , Used for chaining queries. See below.

Equals = When using the meta operator, use the equals to separate key and values.

Chaining Queries

You can chain queries and operators with a comma. This will allow you to get very specific with your searches on various fields.

Examples

Query: test beam Results: assets that have the words test or beam in any of the indexed fields in order of created date.

Query: test*,*beam* Results: assets that have words that start with test or have words with beam in them in any of the indexed fields in order of created date.

Query: "O’Hare" Results: assets with O’Hare in the indexed fields (need the quotes because of the ‘ to prevent a search for O and Hare)

Query: “C.Brown” Results: assets with C.Brown in the indexed fields (need the quotes because of the . to prevent a search for C and Brown).

Query: name:spiderman Results: assets where the desc field contains the word spiderman.

Query: id: d3de* Results: assets where the _id field starts with d3de.

Query: external: m*, name: +red -blue Results: assets that have an External ID that starts with m and must contain the word red but must not contain the word blue.

Query: meta: foo=bar Results: assets that contains value where the metadata key is foo.

Query: meta: My Privacy=private Results: assets that contain meta key of My Privacy with meta value private. Note that meta keys are case sensitive.

Query: meta: myfield=* Results: assets that have a metadata key of myfield.

Query: name: "the natural" Results: assets where the desc field contains the phrase the natural.

Query: cms_type: -live Results: assets where they are all types except live events.

Query: cms_type: clip Results: assets where they are only clips.

Query: meta: myfield=* Results: assets that have a metadata key of myfield.

Query: state: +ready Results: assets in the "ready" state.