Developer guide

Mediaflow CDN

Publish Mediaflow assets to a stable, public CDN URL and embed them anywhere - headless CMS, e-commerce, native apps and newsletters - with on-the-fly image transforms.

How it works

Most Mediaflow CDN integrations follow one canonical pattern:

  1. Assets (images, PDFs, audio, video) live in the Mediaflow DAM.

  2. The integration shows a Mediaflow file picker in the partner's editing UI. The editor browses and selects a file; the picker hands the integration the numeric file id, which the integration resolves to { imageId, filename, filetype } through the file API.

  3. The integration publishes that asset to the Mediaflow CDN by POST-ing the imageId to the management API. This binds the DAM source to a stable public CDN URL.

  4. The partner platform (headless CMS, storefront, app backend, newsletter builder, …) stores that CDN URL alongside its own content.

  5. End-user pages render directly from the CDN URL, with optional transform parameters (resize, format conversion, focus crop, …) appended.

The integration owns steps 1–3 (file picker, resource lifecycle, storing the URL). Step 4 is static URL embedding - no integration code is on the hot path.

The CDN URL is stable for the resource's lifetime. PUT and PATCH bump the version (invalidating cached variants) but the URL doesn't change - no need to re-notify the partner platform.

Environments

Use

URL

Management API

https://api.mediaflow.com

CDN edge

https://eu1.cdn.mediaflow.com

Management endpoints live on the API host and are versioned under /1/. The edge host can change, so the edge URL is always returned by the management API in each resource's url field - treat that as the source of truth and never construct edge URLs in client code.

Authentication

OAuth2 bearer tokens. For the full auth flow, token issuance, and header format, see Mediaflow API – Authentication.

Send the token on every request:

Authorization: Bearer {token}

The token identifies your customer account and file server; every operation is scoped to that customer, and resources of other customers are invisible (404).

Both user tokens and integration tokens are accepted.

Call the management API from your backend, not the browser. The gateway's CORS preflight allows every method the API uses, including PATCH, but a token in browser code is exposed to anyone who opens the page. Keep all lifecycle calls (POST/PUT/PATCH/DELETE) in your integration's backend.

Concepts

Term

Description

Resource

A CDN publication of a single file; binds a DAM source (imageId + serverId) to a stable public URL. Identified by a short lowercase resourceId.

Usage identifier

A short customer-scoped token in the public URL path; allocated automatically on first resource creation.

cdnId

Required when creating a resource. Use 2.

Version

Monotonically increasing counter on a resource. Bumps on PUT (source replace) and PATCH /defaults (defaults change). Appears in the edge ETag value and in versionedUrl.

Mediaflow API

File Selector

Video Player

External