Media

# Media Enad's media docs cover two different jobs: 1. **Delivering optimized images** through the Image Proxy CDN. 2. **Managing digital assets** through DAM, image, file, and video APIs. Use the guide pages for workflow guidance and the generated reference pages for exact endpoint details. ## Choose the right route | If you need to… | Use this route | What it owns | |---|---|---| | Transform and deliver an already-stored image from a URL | [Image Proxy and Media API](/media/latest) | CDN usage patterns, transformation guidance, cache-friendly URL construction | | Understand DAM workflows such as folders, folder assignment, and shareable links | [DAM API guide](/media/dam/latest) | Public workflow guidance and boundaries for DAM-managed assets | | Try DAM endpoints in a browser | [DAM API Playground](/media/dam/playground) | Interactive OpenAPI client backed by `/swagger/dam-api.json` | | Look up exact DAM endpoint paths, request bodies, and responses | [DAM API reference](/reference/dam) | Generated endpoint truth for folders, folder assignment, and shareable links | | Look up image upload and image metadata endpoints | [Images API reference](/reference/images) | Generated endpoint truth for images and image relationships | | Look up file upload and file metadata endpoints | [Files API reference](/reference/files) | Generated endpoint truth for files and file relationships | | Look up video upload and video metadata endpoints | [Videos API reference](/reference/videos) | Generated endpoint truth for videos and video relationships | | Look up the current general media-item reference surface | [Media API reference](/reference/media) | Generated endpoint truth for media-item lookup coverage currently present in docs | ## Media, DAM, images, files, and videos These names overlap, but they do not all mean the same thing in the docs. - **Media** is the public product area for image delivery and shared asset concepts. In these docs it includes the Image Proxy CDN guide and the current generated media-item reference route. - **DAM** is the digital asset management workflow layer. Use it for folders, folder trees, assigning assets to folders, and shareable links. - **Images**, **files**, and **videos** are asset-type reference areas. Use them when you need upload, retrieval, update, delete, or relationship endpoint details for a specific asset type. - **Reference routes** are generated from source artifacts and own copy-paste endpoint truth. - **Guide routes** explain how the pieces fit together and intentionally avoid restating every generated schema. ## Image Proxy CDN The Image Proxy CDN is the delivery surface for processed images. It is for reading and transforming images that already exist in Enad-managed storage, then returning image bytes suitable for storefronts, CMS previews, and other web surfaces. Use the proxy when you need to: - Resize images for responsive breakpoints. - Request modern formats such as WebP or AVIF. - Crop, pad, blur, or fill images for layout consistency. - Build stable, cacheable image URLs for a storefront or content surface. Do not use the CDN route as an upload API. Upload and metadata operations belong to the generated [Images API reference](/reference/images), [Files API reference](/reference/files), [Videos API reference](/reference/videos), and DAM workflow endpoints. ## DAM API The DAM API is the workflow surface for organizing assets after they exist in the system. Use DAM when your application needs to: - Create and update folder structures. - Resolve a folder tree or folder path. - Assign images, files, or videos to folders. - Build shareable links that reference existing resources. - Retrieve folder-scoped media collections. For exact paths, fields, auth, enums, request bodies, and response schemas, use the generated [DAM API reference](/reference/dam) or the [DAM API Playground](/media/dam/playground). ## Copy-paste-safe boundary This section is guidance-only. The generated reference pages own endpoint paths, methods, parameters, schemas, response examples, and source-derived behavior: - [Media API reference](/reference/media) - [DAM API reference](/reference/dam) - [Images API reference](/reference/images) - [Files API reference](/reference/files) - [Videos API reference](/reference/videos) ## Related docs - [Image Proxy and Media API](/media/latest) - [DAM API guide](/media/dam/latest) - [DAM API Playground](/media/dam/playground) - [Build a storefront page](/react-sdk/latest/guides/storefront-page)