Use Media when you need one of two jobs:

1. Deliver stored images through the Image Proxy CDN.
2. Manage digital assets through DAM, image, file, and video APIs.

Choose the workflow first, then open reference pages for endpoint details.

Start by job

Exact endpoint details stay in reference pages. Public asset-library reads live under Folders, Media, and Shareable Links. Management DAM administration pages live under DAM. Operation pages show the API, method, and path.

Asset terms

These names overlap, but they do not all mean the same thing.

Media is the public product area for image delivery and shared asset concepts. It includes the Image Proxy CDN guide and the media-item reference route.

DAM is the workflow layer for organizing assets after they exist in Enad. Use public asset-library reads for folder trees, folder contents, facets, media search, and shareable-link browsing. Use Management API DAM routes to create folders, update folders, delete folders, assign assets to folders, manage roles, and administer shareable links.

Images, files, and videos are asset-type areas. Use them when you need upload, retrieval, update, delete, or relationship endpoint details for one asset type.

Reference routes provide endpoint details for implementation. Media guides explain how the pieces fit together.

Image Proxy CDN

The Image Proxy CDN is the delivery surface for images that already exist in Enad-managed storage. It returns image bytes suitable for storefronts, CMS previews, and other web surfaces.

Use the proxy when you need to:

• Build responsive image URLs.
• Request modern output formats such as WebP or AVIF.
• Use bounded resize, crop, pad, blur, or fill patterns for layout consistency.
• Build repeatable image URLs for a storefront or content surface.

The default CDN host, app-level allowed-domain configuration, import/upload fallback, delete cleanup path, transformation parameter validation, response classes, and transform limits are defined behavior. Cache-key construction, cache retention, and edge freshness timing are not public contract details; treat image-delete cache purges as cleanup requests rather than a guarantee that every edge stops serving old bytes immediately.

Do not use the CDN route as an upload API. Uploads, metadata updates, and relationships belong to the asset-type references and DAM workflow endpoints.

Image deletion belongs to the asset APIs, not the CDN URL. Successful image deletion removes the stored source object and stored transformed derivatives for that image path, then requests a CDN cache purge by media URL prefix. Do not schedule a second cleanup process for Image Proxy derivatives.

DAM routes and asset reads

DAM workflows span public asset-library reads and Management API administration routes for organizing assets after they exist in the system. Use the public asset-library read API when your application needs to:

• Resolve a folder tree or folder path.
• Retrieve folder-scoped media collections.
• Search across DAM media and inspect attribute facets for picker or library filtering.
• Browse resources exposed through a shareable link.

Use Management API DAM operations when your application needs to create or update folder structures, assign images, files, or videos to folders, manage roles, or build shareable links that reference existing resources.

For exact paths, fields, auth, enums, request bodies, and response schemas, use Folders, Media, and Shareable Links for public reads. Use DAM administration or Management OpenAPI reference for administration.

Reference routes

Media references split work by job.

Use this split to avoid mixing delivery, organization, and record mutation in one integration path. CDN URLs deliver transformed image bytes; DAM organizes existing assets; asset-type APIs change asset records.

Governed media changes

Use MCP media-control or media-delete workflows when an agent needs a governed preview/apply path for media changes. MCP is not a separate media API; it adds validation, preview, approval, drift checks, and audit evidence around the same media jobs.

Current media-control workflows cover:

Preview behavior stays bounded. Folder moves require current asset and target-folder reads, reject no-op moves, and check for drift before writing. Relationship changes require current target membership evidence, reject add/remove no-ops, and include a restore change in the preview. Metadata changes stay field-level and raw-byte-free. Video upload URL generation accepts metadata only; previews and audit evidence exclude raw bytes, and signed upload URLs are redacted from audit records.

Current media-delete workflows cover:

• Single image, video, or file deletion.
• Bulk image or video deletion for 1-25 assets.
• Explicit no-rollback acknowledgement before preview.
• Partial-failure mode capture for bulk delete requests.

Bulk delete previews reject duplicate or unresolved items. Apply checks for drift again, writes through the matching delete operation, and records audit evidence for the applied change.

Delete previews resolve the current asset record before allowing a change. They summarize relationship, translation, and attribute dependencies when those fields are present. They also mark destructive effects such as storage-object deletion, relationship deletion, translation deletion, cache or media-setting deletion, and delete-event publication.

Endpoint details

Use API reference pages for endpoint paths, methods, parameters, schemas, response examples, and contract behavior. Start from the workflow above, then open the matching reference when you need exact request or response shape.

Related docs

Continue with Image Proxy and Media API, Asset library reads and DAM administration, Public asset-library playground, or Build a storefront page.