canonical: https://jentic.com/apis/mediasilo.com/mediasilo

# MediaSilo API

Jentic publishes the only available OpenAPI specification for MediaSilo API, keeping it validated and agent-ready. MediaSilo is a cloud media asset management platform built for video production teams to organise, review, and distribute video content. The API exposes 84 endpoints covering projects, folders, assets, versions, review links, spotlights, distribution lists, playlists, metadata, webhooks, and link analytics. It is well-suited to integrating MediaSilo with editorial systems, automating asset ingest, and triggering review workflows from external tools.

## For AI agents

Manage MediaSilo projects, folders, video assets, and review links so an agent can ingest, organise, share, and track media collateral.

## Scope

Does not handle video transcoding for end-user delivery, public streaming playback, or rights and licensing management - use for production-side video asset management and review only.

## Capabilities

- Upload video and image assets into a project folder and track their encoding progress
- Create review links with expiration dates and inspect per-link analytics for stakeholder feedback
- Move and copy assets between folders to mirror an editorial taxonomy
- Attach custom metadata keys and values to assets for downstream search and filtering
- Manage distribution lists and trigger spotlight presentations for client review
- Subscribe webhooks to asset, link, and project events to drive downstream automation
- Roll back to a previous asset version by activating an earlier version on a master asset

## Use cases

### Editorial Review Distribution

Send video cuts to internal and external reviewers via shareable links with expiration controls, password gating, and per-link viewing analytics. Producers can track who has watched a cut, how far they got, and whether they downloaded the file. The MediaSilo API exposes link creation, expiration, and analytics in a way that lets an automation generate one personalised link per stakeholder and revoke them once feedback is collected.

Example prompt: Create a review link for folder ID abc123 with a 14-day expiration, attach the latest version of asset xyz, and return the public link plus its analytics endpoint.

### Automated Master Asset Ingest

When a finished master lands in a delivery dropbox, push it into MediaSilo with the right project, folder, and metadata so the asset is immediately discoverable. The API supports asset upload, metadata key-value tagging, and folder placement, and emits webhook events when encoding finishes. This eliminates the manual drag-and-drop step that production assistants would otherwise repeat dozens of times per shoot.

Example prompt: Upload the file final_master_v3.mov into project Brand Q4 inside folder Approved Masters, set metadata client to Acme and shoot_date to 2026-05-12, and wait for the encoding-progress endpoint to return complete.

### Cross-Tool Asset Federation

Use MediaSilo as the source of record for video assets and surface them in editorial CMS, marketing portals, or DAM front-ends without duplicating storage. Link analytics, version history, and distribution lists stay anchored in MediaSilo while external systems pull metadata and previews on demand. The API supports listing assets, retrieving versions, and inspecting link stats so a federated front-end stays accurate without nightly syncs.

Example prompt: List all assets in project Brand Q4 modified in the last seven days and return their IDs, current version, and most recent review-link view counts.

### Agent-Driven Stakeholder Updates

An AI agent watches MediaSilo for new versions, generates expiring review links, and notifies the right stakeholders in Slack or email with a one-line summary of what changed. By calling MediaSilo through Jentic, the agent searches by intent, loads the link-creation schema, and executes the call without an engineer wiring up the SDK. This compresses a 10-step review hand-off into a single agent run.

Example prompt: Find the latest version of asset xyz in MediaSilo, create a 7-day review link, and post a message to the editorial Slack channel with the link and version notes.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/folders/{folderId}/assets` | Upload an asset into a folder |
| GET | `/assets/{assetId}/encoding-progress` | Check encoding status of an asset |
| POST | `/links` | Create a review link |
| GET | `/links/{linkId}/analytics` | Retrieve viewing analytics for a review link |
| POST | `/links/{linkId}/expire` | Expire a review link |
| POST | `/folders/{folderId}/assets/move` | Move assets between folders |
| GET | `/assets/{assetId}/versions` | List versions for an asset |
| POST | `/assets/{assetId}/metadata` | Attach metadata key-value pairs to an asset |

## Key resources

- **Assets** — Upload, retrieve, version, and tag video and image assets, including encoding-progress checks
- **Folders** — Organise assets into nested folders with copy and move operations
- **Links** — Create shareable review links with expiration and per-link viewing analytics
- **Projects** — Top-level containers grouping folders, assets, and roles
- **Spotlights** — Curated presentation views for client review
- **Distribution Lists** — Manage groups of recipients for asset and link delivery
- **Webhooks** — Subscribe to asset, version, and link events for downstream automation

## Why Jentic

- **Setup:** Wiring the MediaSilo API by hand means encoding your username and password as Basic auth, pointing at the api.mediasilo.com/v3 host, and mapping its asset and review-link operations yourself. Through Jentic you install once, import the MediaSilo API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** MediaSilo puts the resource id in the URL path (`/folders/{folderId}/assets`, `/assets/{assetId}/...`, `/links/{linkId}/...`), so a rule can pin your agent to one folder, asset, or link. You choose the operations it may call, so destructive ones like expiring a link or moving assets are not included unless you add them.
- **Credential handling:** Your MediaSilo username and password are stored once, encrypted, by your own Jentic One instance and encoded into a Basic auth header at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a video review link', and Jentic returns the matching MediaSilo operation with its input schema so the agent calls the right endpoint without browsing MediaSilo's docs.

## Related APIs

- **Vimeo API** — Vimeo offers video hosting and review tools as a more consumer-facing alternative to MediaSilo's production-focused MAM.
- **Mux API** — Mux handles transcoding and adaptive streaming for assets that originate in MediaSilo.
- **Cloudinary Upload API** — Cloudinary handles image and video transformations downstream of MediaSilo's source-of-truth assets.
- **Brandfolder API** — Brandfolder is a brand-asset DAM with a wider remit across documents and images, where MediaSilo is video-first.

## FAQ

### Why is there no official OpenAPI spec for MediaSilo API?

MediaSilo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MediaSilo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the MediaSilo API use?

The MediaSilo API uses HTTP Basic authentication with your MediaSilo account credentials. When you call it through Jentic, those credentials are stored encrypted in your Jentic One instance and never enter the agent's context - the agent receives a scoped session for the specific operation.

### Can I create review links programmatically with the MediaSilo API?

Yes. The /links endpoint lets you create review links pointing to assets or folders, set an expiration via `/links/{linkId}/expire`, and read viewing telemetry from `/links/{linkId}/analytics` and `/links/{linkId}/stats` so a workflow can revoke the link once everyone has watched.

### What are the rate limits for the MediaSilo API?

MediaSilo does not publish hard numerical rate limits in its documentation; bulk asset uploads should be paced and review-link creation throttled per account. If you hit a 429, back off exponentially before retrying through Jentic.

### How do I upload a video asset into a folder through Jentic?

Search Jentic for upload a video asset to MediaSilo, load the schema for the upload operation under `/folders/{folderId}/assets`, and execute with the folder ID and binary payload. Jentic returns the new asset ID, which you can poll via `/assets/{assetId}/encoding-progress` to confirm encoding finished.

### Can I track who viewed a review link?

Yes. Each review link exposes `/links/{linkId}/analytics` and `/links/{linkId}/stats` which return per-viewer events including timestamp and engagement, so an agent can summarise who watched what without opening the MediaSilo UI.

### Can I limit what my agent is allowed to do with the MediaSilo API?

Yes. Because MediaSilo puts the resource id in the URL path (`/folders/{folderId}/assets`, `/assets/{assetId}/...`, `/links/{linkId}/...`), a rule in your self-hosted Jentic One can pin the agent to a single folder, asset, or review link. You choose which operations the agent may call, so destructive ones like expiring a link via `/links/{linkId}/expire` or moving assets via `/folders/{folderId}/assets/move` stay out of reach unless you add them. The stored MediaSilo credentials and the exact operation list are governed by your own rules, not the agent.