Asset library reads and DAM administration

Public asset library reads, shareable-link browsing, and authenticated DAM administration routes.

API
DAM
Schema
dam-api

Enad has two DAM-facing workflows. Public asset-library reads use dam.enad.io app_id routes for browsing existing folders, media, facets, and shareable links. Authenticated DAM administration uses Management API routes under the team/app /dam/... path.

Administration routes are for operators who need to create folders, assign media, manage roles, or change shareable links. Public asset-library reads are for clients that only need to browse existing public folders and media.

Open the matching reference and OpenAPI spec for methods, paths, parameters, request bodies, auth details, and response schemas. Public asset-library reads use DAM OpenAPI. Administration uses Management OpenAPI.

JobRoute shapeReference
Public asset-library browsingdam.enad.io/api/v1/\{app_id\}/folders..., dam.enad.io/api/v1/\{app_id\}/media/search, or dam.enad.io/api/v1/\{app_id\}/shareable-links...Folders, Media, and Shareable Links
Authenticated DAM administrationapi.enad.io/api/v1/\{team_slug\}/\{app_slug\}/dam/...DAM administration and Management OpenAPI

Choose the right DAM workflow

DAM is the digital asset management layer for assets that already exist in Enad. Choose public asset-library reads when your product needs to browse folders, find assets by folder context, search existing media, or read resources exposed through a shareable link.

Choose authenticated DAM administration when the workflow changes the folder and sharing model: folder creation, assignments, role changes, operator search, and shareable-link updates.

DAM handles public hierarchy reads, folder contents, facets, folder-path resolution, media search across existing public library assets, shareable-link browsing, and Management API folder administration.

Asset-type APIs handle upload, metadata updates, relationship changes, and deletion for images, files, or videos.

What DAM does not own

DAM is not the same route as every media-adjacent API. Route image transformation and CDN delivery to Image Proxy and Media API.

Asset-type upload, retrieval, update, delete, and relationship work belongs to Images API reference, Files API reference, and Videos API reference. Public folder reads live in Folders API reference, public media lookup and search live in Media API reference, and public shareable-link reads live in Shareable Links API reference. Authenticated folder, assignment, role, operator media search, and shareable-link administration lives in DAM administration reference.

Routes

Public asset-library operations are GET reads under a dam.enad.io app_id route.

Management DAM administration runs under /api/v1/\{team_slug\}/\{app_slug\}/dam/.... It covers folder create/update/delete, folder tree reads, media search for operators, folder placement for images/videos/files, folder role membership, shareable-link lifecycle, and shareable-link resource membership.

Use the public operation pages for browsing and lookup. Use Management API pages for changing folders, assignments, roles, and links.

Public reads validate the app context before returning folder or media data. Folder and folder-media routes only expose public folders; non-public folders are treated as not found. Media search also searches only media attached to public folders. Shareable-link reads are different: they resolve an app-scoped token, then read the folders or resources attached to that link.

Use the public asset-library API as a read surface. It does not create folders, move media, assign roles, attach resources to links, upload files, update metadata, or delete assets.

Common DAM workflows

Read a folder tree

Use public asset-library reads when users need a browsable library structure. These operations retrieve one folder, list contents, inspect facets, list public roots, and resolve hierarchy trees.

Start with these operation pages:

Retrieve media in a folder

Folder-scoped retrieval is useful for asset libraries, CMS pickers, and media browsers. Ask which resources are in a folder, then use asset-type references for exact image, file, or video metadata operations.

Use Get Folder Contents for public folder media reads. The current public route is /folders/\{id\}/media. Use Get Folder Media only when the integration is a Management API DAM administration workflow.

Search and filter DAM media

Use DAM media search when an asset library, picker, or content workflow needs to find assets across resource types instead of browsing one folder at a time.

The references expose three related patterns:

The public media search and folder-facet routes also document attribute-facet behavior for read-only browsing. Facet counts use per-template exclusion: filters on the same attribute template are ignored while computing that template's counts, and filters on other templates still apply. In practice, that means multi-select filters behave as OR within one template and AND across different templates.

Attribute filters use repeated attributes=template_key/attribute_key query parameters. Duplicate filters are ignored, surrounding whitespace is trimmed, empty filters are rejected, and comma-separated values are not split into separate filters.

Search requires a non-empty text query and can sort by full-text relevance when the operation page exposes the rank sort. Folder media and shareable-link media can filter by media type: image, video, file, or all.

Use reference pages for the exact query parameter names on each route. The rule is simple: search across a library, list media inside one folder, and use facets when the UI needs filter counts before or alongside a listing.

Read a shared set of resources

Shareable links expose a selected set of existing resources. Use public asset-library read operations when a client needs to browse folders or media through an existing shareable link.

Shareable-link media reads combine direct image, video, and file resources with media contained inside linked folders, then de-duplicate media items in the response. Folder-scoped share reads first verify that the requested folder is part of the link; otherwise the folder is treated as not found. Shareable-link folder reads return only folders attached to that token.

Use Management API operations to create, update, delete, or change the resources attached to a shareable link. Start with these public read pages:

Playground and references

Use Public asset-library playground when you want to try public read operations interactively. For implementation details, open the operation reference pages: public read pages use the DAM OpenAPI contract, while authenticated administration pages use the Management API contract under the DAM reference bucket.

DAM and Media naming

Media is the broader docs area for asset delivery, transforms, uploads, records, and DAM workflows. Public asset-library reads cover folder browsing, media search, and shareable-link browsing; Management API owns the private DAM administration routes for changing those resources.

Asset library reads and DAM administration

# Asset library reads and DAM administration Enad has two DAM-facing workflows. Public asset-library reads use `dam.enad.io` `app_id` routes for browsing existing folders, media, facets, and shareable links. Authenticated DAM administration uses Management API routes under the team/app `/dam/...` path. Administration routes are for operators who need to create folders, assign media, manage roles, or change shareable links. Public asset-library reads are for clients that only need to browse existing public folders and media. Open the matching reference and OpenAPI spec for methods, paths, parameters, request bodies, auth details, and response schemas. Public asset-library reads use DAM OpenAPI. Administration uses Management OpenAPI. | Job | Route shape | Reference | | --- | --- | --- | | Public asset-library browsing | `dam.enad.io/api/v1/{app_id}/folders...`, `dam.enad.io/api/v1/{app_id}/media/search`, or `dam.enad.io/api/v1/{app_id}/shareable-links...` | [Folders](/reference/folders), [Media](/reference/media), and [Shareable Links](/reference/shareable-links) | | Authenticated DAM administration | `api.enad.io/api/v1/{team_slug}/{app_slug}/dam/...` | [DAM administration](/reference/dam) and [Management OpenAPI](/reference/openapi/management-api) | ## Choose the right DAM workflow DAM is the digital asset management layer for assets that already exist in Enad. Choose public asset-library reads when your product needs to browse folders, find assets by folder context, search existing media, or read resources exposed through a shareable link. Choose authenticated DAM administration when the workflow changes the folder and sharing model: folder creation, assignments, role changes, operator search, and shareable-link updates. DAM handles public hierarchy reads, folder contents, facets, folder-path resolution, media search across existing public library assets, shareable-link browsing, and Management API folder administration. Asset-type APIs handle upload, metadata updates, relationship changes, and deletion for images, files, or videos. ## What DAM does not own DAM is not the same route as every media-adjacent API. Route image transformation and CDN delivery to [Image Proxy and Media API](/media/latest). Asset-type upload, retrieval, update, delete, and relationship work belongs to [Images API reference](/reference/images), [Files API reference](/reference/files), and [Videos API reference](/reference/videos). Public folder reads live in [Folders API reference](/reference/folders), public media lookup and search live in [Media API reference](/reference/media), and public shareable-link reads live in [Shareable Links API reference](/reference/shareable-links). Authenticated folder, assignment, role, operator media search, and shareable-link administration lives in [DAM administration reference](/reference/dam). ## Routes Public asset-library operations are `GET` reads under a `dam.enad.io` `app_id` route. Management DAM administration runs under `/api/v1/{team_slug}/{app_slug}/dam/...`. It covers folder create/update/delete, folder tree reads, media search for operators, folder placement for images/videos/files, folder role membership, shareable-link lifecycle, and shareable-link resource membership. Use the public operation pages for browsing and lookup. Use Management API pages for changing folders, assignments, roles, and links. Public reads validate the app context before returning folder or media data. Folder and folder-media routes only expose public folders; non-public folders are treated as not found. Media search also searches only media attached to public folders. Shareable-link reads are different: they resolve an app-scoped token, then read the folders or resources attached to that link. Use the public asset-library API as a read surface. It does not create folders, move media, assign roles, attach resources to links, upload files, update metadata, or delete assets. ## Common DAM workflows ### Read a folder tree Use public asset-library reads when users need a browsable library structure. These operations retrieve one folder, list contents, inspect facets, list public roots, and resolve hierarchy trees. Start with these operation pages: - [Get Folder by ID](/reference/folders/get-folder-by-id) - [Get Full Folder Tree](/reference/folders/get-full-folder-tree) - [Get Folder Tree from Path](/reference/folders/get-folder-tree-from-path) - [Get Public Folders](/reference/folders/get-public-folders) ### Retrieve media in a folder Folder-scoped retrieval is useful for asset libraries, CMS pickers, and media browsers. Ask which resources are in a folder, then use asset-type references for exact image, file, or video metadata operations. Use [Get Folder Contents](/reference/folders/get-folder-contents) for public folder media reads. The current public route is `/folders/{id}/media`. Use [Get Folder Media](/reference/dam/get-folder-media) only when the integration is a Management API DAM administration workflow. ### Search and filter DAM media Use DAM media search when an asset library, picker, or content workflow needs to find assets across resource types instead of browsing one folder at a time. The references expose three related patterns: - [Search Media](/reference/media/search-media) searches across the public asset library. - [Get Folder Contents](/reference/folders/get-folder-contents) retrieves media inside one folder with filtering and sorting. - [Search DAM Media](/reference/dam/search-dam-media) is the Management API version for authenticated administration workflows. The public media search and folder-facet routes also document attribute-facet behavior for read-only browsing. Facet counts use per-template exclusion: filters on the same attribute template are ignored while computing that template's counts, and filters on other templates still apply. In practice, that means multi-select filters behave as OR within one template and AND across different templates. Attribute filters use repeated `attributes=template_key/attribute_key` query parameters. Duplicate filters are ignored, surrounding whitespace is trimmed, empty filters are rejected, and comma-separated values are not split into separate filters. Search requires a non-empty text query and can sort by full-text relevance when the operation page exposes the `rank` sort. Folder media and shareable-link media can filter by media type: image, video, file, or all. Use reference pages for the exact query parameter names on each route. The rule is simple: search across a library, list media inside one folder, and use facets when the UI needs filter counts before or alongside a listing. ### Read a shared set of resources Shareable links expose a selected set of existing resources. Use public asset-library read operations when a client needs to browse folders or media through an existing shareable link. Shareable-link media reads combine direct image, video, and file resources with media contained inside linked folders, then de-duplicate media items in the response. Folder-scoped share reads first verify that the requested folder is part of the link; otherwise the folder is treated as not found. Shareable-link folder reads return only folders attached to that token. Use Management API operations to create, update, delete, or change the resources attached to a shareable link. Start with these public read pages: - [Get Shareable Link Folders](/reference/shareable-links/get-shareable-link-folders) - [Get Shareable Link Folder Media](/reference/shareable-links/get-shareable-link-folder-media) - [Get Shareable Link Media](/reference/shareable-links/get-shareable-link-media) ## Playground and references Use [Public asset-library playground](/media/dam/playground) when you want to try public read operations interactively. For implementation details, open the operation reference pages: public read pages use the DAM OpenAPI contract, while authenticated administration pages use the Management API contract under the DAM reference bucket. ## DAM and Media naming Media is the broader docs area for asset delivery, transforms, uploads, records, and DAM workflows. Public asset-library reads cover folder browsing, media search, and shareable-link browsing; Management API owns the private DAM administration routes for changing those resources. ## Related docs - [Media overview](/media) - [Image Proxy and Media API](/media/latest) - [Public asset-library playground](/media/dam/playground) - [DAM administration reference](/reference/dam) - [Images API reference](/reference/images) - [Files API reference](/reference/files) - [Videos API reference](/reference/videos)