Skip to main content
The CDN stores team files and serves them at public addresses. You manage files through API V3 with a key; serving files needs no key.

Access

First bind your key to a team:
The key owner needs a team role with CDN access; membership is checked on every request. Send the key only in the erlcrussia-api-key header.

File addresses

Each file is identified by a namespace and a path. The namespace is the team slug or a verified custom domain.
  • Shared domain: https://cdn.erlcrussia.com/YOUR_TEAM_SLUG/images/logo.png
  • Custom domain: https://files.example.com/images/logo.png
On the shared domain a team can only use /{slug}/.... If path is omitted on upload, it is generated from the file type. If a file with the same path already exists, the response is 409 and the file is not overwritten. Use a new path for new versions.

Folders

Common parameters

Cache

CDN responses include X-Cache (CDN cache) and CF-Cache-Status (Cloudflare). A purge (POST /cdn/assets/purge) is accepted at once and runs in the background. Publishing new versions at new addresses is more reliable than replacing old files. See CI/CD and cache purge.

Common responses

Personal files of website users are covered in Personal files.