Documentation

MediaEdge nodes front media asset catalogs with a regional cache. Client applications poll the node over HTTPS and stream objects in bounded chunks.

Getting started

• Obtain an access token in the client area.
• Send the token as the X-Auth-Token request header on every call.
• Tag each request with a unique X-Request-Id header — it is used for delivery accounting and retries.

Caching behavior

Static pages, images and stylesheets are cached at the edge. Dynamic API responses are marked no-store and are never cached; do not rely on If-Modified-Since for API calls.

Sections

• Asset API reference — request format, pagination, retry policy.
• Node status — live component view.