Predictable
JSON in, JSON out. Versioned at the URL. No surprise field renames, no breaking changes inside a major version.
Developers
Build on top of your asset library
A REST API, outbound webhooks, an MCP server for AI agents, embeddable players, and a typed TypeScript SDK. Everything you need to wire Freedam into the rest of your stack, from your CMS to your automation runner to your in-house tools.
Four ways to integrate
Pick the surface that fits the job. Most integrations end up using two or three of these together.
REST API
A versioned, JSON-only HTTP API for assets, collections, uploads, shares, metadata, and operations. Token-based auth with granular scopes.
Read moreWebhooks
Subscribe to fourteen real-time events. Signed payloads, automatic retries, delivery history, and a key-rotation flow with a grace period.
Read moreMCP server
Plug Freedam directly into MCP-aware AI clients. Eleven first-class tools for agents to search, organize, upload, and share assets safely.
Read moreVideo embeds
A single iframe snippet to embed any video asset. Restrict playback to your own domains, control autoplay, loop, captions, and start time.
Read moreWhat it's like to integrate
Six things we care about so your integration doesn't become a maintenance burden later.
Scoped by default
API tokens carry granular abilities. A token meant to upload cannot delete. A token meant to read cannot share. Least privilege is the default, not the upgrade.
Typed where it counts
A first-party TypeScript SDK ships full coverage of the API. Autocomplete on every endpoint, every parameter, every response.
Event-driven
Anything you can do through the UI fires an event you can subscribe to. Build automations without polling the API on a timer.
AI-friendly
A native MCP server lets language-model agents call into Freedam through the same scoped tokens. Same boundaries, same audit trail.
No vendor magic
Everything is a documented HTTP call against the OpenAPI spec. No hidden endpoints, no proprietary protocol, no client lock-in.
Always up to date
A live reference that always matches the running API
The OpenAPI 3 reference at /docs/api stays in lockstep with what production is serving. No hand-written drift, no out-of-date examples. Try requests right from the page, or download /docs/api.json to use with the OpenAPI tooling of your choice.
Quick start
Pick the integration path that matches your team.
Developers · Get going
Ready to wire Freedam into your stack?
Start in the live API reference, or take the demo for a spin and create your first token.