Query DAM assets using tree paths and tags
Searches and retrieves DAM assets using tree path pattern matching, tag-based variant filtering, wildcard name matching, and partial search. Requires a company admin Bearer token with media view permission, or a token granted the dam:browse scope. Results are cursor-paginated over matching asset paths - pass limit (default 50, max 100) and the opaque meta.next_cursor from the previous response as cursor. A missing path, an invalid path pattern, or too many tags returns 400.
Authorizations
Bearer token authentication
Body
Required tree path pattern for hierarchical filtering
Optional comma/semicolon-separated tag string for variant filtering. Comma = OR, Semicolon = AND
Optional asset name with wildcard support
Optional partial search across asset names and descriptions (case-insensitive)
Optional tag names to exclude, as a comma-separated string or an array. Variants carrying these tags are left out of the tree.
Optional asset categories to exclude (images, videos, audio, text, data, documents, other), as a comma-separated string or an array.
Maximum number of asset paths to return per page. Defaults to 50 and is clamped to the range 1-100.
Opaque cursor from a previous response's meta.next_cursor. Omit it to fetch the first page.
Response
Success
The path pattern that was queried
Nested tree structure of assets organized by path segments. Folder nodes are objects keyed by the next path segment; each leaf is an asset object with asset_code, name, category, created_at, and a variants array (file_name, mime_type, updated_at, metadata, tags, default, url, content, data).