Dacast API

Name: Dacast API API
Brand: Dacast API
Availability: InStock

✓ Official Vendor SpecMediaVideo ProcessingapiKey14 EndpointsREST

For Agents

Manage Dacast live streams, video on demand assets, and channels for end-to-end video publishing workflows.

Quickstart

Get started with Dacast API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a Dacast live stream"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Dacast API API.

Create a live stream and configure ingest settings via POST /live

Upload a video on demand asset and store its metadata via POST /vod

Update VOD or live stream details such as title, description, and access settings

Create a 24/7 channel for scheduled looping or simulated-live programming

GET STARTED

Start building with Dacast API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Dacast API API for, with concrete tasks.

★ Live Event Provisioning

Production teams running a series of live events use POST /live to provision a fresh stream for each event, capturing the stream key and ingest URL for the encoder. The agent pre-creates streams the night before, attaches the right access settings, and writes the credentials into the production runbook so the broadcast team can connect directly.

POST to /live with title 'Q3 Earnings Call' and the desired access settings, then return the ingest URL and stream key.

VOD Catalogue Management

Content teams managing a library of recorded videos use POST /vod to add new assets and PUT /vod/{contentId} to keep titles, descriptions, and pricing settings consistent. Periodically the agent calls GET /vod to audit the catalogue, identify orphaned or expired assets, and call DELETE /vod/{contentId} to remove them.

Call GET /vod, filter for assets last updated more than 18 months ago, and DELETE /vod/{contentId} for each match.

24/7 Channel Programming

Broadcasters running always-on channels for highlights, training content, or marketing loops use POST /channel to create the channel and PUT to update its programming. The API surfaces the playlist and access settings so an agent can rotate content through a virtual channel without manual editing in the dashboard.

POST to /channel with title 'Customer Stories Loop' and a playlist of contentIds, then return the new channel ID.

Agent-Driven Content Cleanup

An AI agent running a weekly housekeeping job lists every live stream and VOD asset, cross-references them with an internal rights database, and removes content that has aged out. The combination of GET /live, GET /vod, and the matching DELETE endpoints lets the agent enforce retention policy without a human reviewing every asset.

For each contentId in the rights database with status='expired', call DELETE /vod/{contentId} or DELETE /live/{contentId} and log the outcome.

Key Endpoints

14 endpoints — dacast is a video streaming platform aimed at broadcasters, sports rights holders, and businesses that need monetised live and on-demand video.

METHOD

PATH

DESCRIPTION

POST

/live

Create a live stream

GET

/live

List live streams

POST

/vod

Create VOD content

GET

/vod

List VOD content

PUT

/vod/{contentId}

Update VOD content

DELETE

/vod/{contentId}

Delete VOD content

POST

/channel

Create a channel

GET

/channel

List channels

POST

/live

Create a live stream

GET

/live

List live streams

POST

/vod

Create VOD content

GET

/vod

List VOD content

PUT

/vod/{contentId}

Update VOD content

DELETE

/vod/{contentId}

Delete VOD content

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Dacast X-API-Key is stored encrypted in the Jentic vault. Agents receive a scoped runtime credential when they call /vod, /live, or /channel endpoints, so the raw key never lands in prompts, logs, or chat history.

Intent-based discovery

Agents search Jentic for 'create a Dacast live stream' or 'upload a video to Dacast' and Jentic returns the matching operation with its input schema, so the agent can call POST /live or POST /vod directly without reading the developer.dacast.com docs.

Time to first call

Direct Dacast integration: 1-2 days for auth, ingest setup, and content lifecycle handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Vimeo API

Video hosting platform with stronger creator-tooling and richer player customisation than Dacast.

Choose Vimeo when creator-friendly editing and embedded player branding matter; choose Dacast when monetisation, geo-restrictions, and broadcaster-grade live are the priority.

Alternative

Mux Video API

Developer-first video infrastructure with API-driven live and on-demand workflows.

Choose Mux when the team is engineering-led and wants per-asset analytics through a clean API; choose Dacast when the workflow includes paywalls and monetisation tooling out of the box.

Complementary

Cloudflare API

Cloudflare Stream and CDN sit alongside Dacast for delivery and edge caching.

Use Cloudflare for DNS, security, and edge caching of player pages while Dacast hosts and ingests the streams themselves.

FAQs

Specific to using Dacast API API through Jentic.

What authentication does the Dacast API use?

The Dacast API uses an API key passed in the X-API-Key header. You generate the key in the Dacast account settings and include it on every request to developer.dacast.com/v2. Through Jentic the key is stored encrypted in the vault and the agent receives a scoped runtime credential, so the raw key never enters the model context.

Can I create a live stream with the Dacast API?

Yes. POST /live creates a new live stream and returns the ingest URL and stream key needed by the encoder. You can then GET /live/{contentId} to fetch the stream's playback details and PUT /live/{contentId} to update settings such as title or access controls.

What are the rate limits for the Dacast API?

The OpenAPI spec does not document explicit rate limits. Dacast's developer guidance recommends keeping API traffic below a few requests per second per key for management workflows; bulk operations such as catalogue audits should be paced rather than fired in parallel.

How do I upload a VOD asset through Jentic?

Install pip install jentic and run an agent with the search query 'upload a video to Dacast'. Jentic returns the POST /vod operation with its input schema; the agent provides the asset metadata and follows up with the upload step described in the spec.

Can I delete expired VOD content through the API?

Yes. DELETE /vod/{contentId} removes a VOD asset by ID. A typical pattern is to call GET /vod, filter for assets that have aged out, and loop the matching contentIds through DELETE /vod/{contentId} as part of a housekeeping job.

Does the Dacast API expose viewer analytics?

The 14 endpoints in this spec cover content management for live streams, VOD, and channels. Detailed viewer analytics are surfaced in the Dacast dashboard rather than through these REST endpoints; use the platform's analytics view or contact Dacast for analytics data export options.