DynTube API

Name: DynTube API API
Brand: DynTube API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaVideo Processingbearer39 EndpointsREST

For Agents

Upload, organise, and stream video content; manage projects, channels, live streams, member access plans, and pull analytics for any video in the DynTube account.

Quickstart

Get started with DynTube 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:
"upload a video to DynTube"

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

Capabilities

What an agent can do with DynTube API API.

Upload a video by URL and track its processing status until ready for delivery

Organise videos into projects and channels with templated channel layouts

Schedule, list, and update live streams with per-account stream limits

Create paid or free member plans and manage members enrolled in those plans

GET STARTED

Start building with DynTube API API

Explore with Jentic

View OpenAPI Document

Use for: I want to upload a new video to DynTube from a public URL, Create a private channel for paid course videos, Schedule a live stream and get the stream key, List all members enrolled on a specific plan

Not supported: Does not transcode arbitrary user uploads on the management host, run real-time meetings, or host non-video assets - use for video hosting, live streams, and gated video membership only.

Jentic publishes the only available OpenAPI document for DynTube API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the DynTube API, keeping it validated and agent-ready. DynTube is a video hosting and delivery platform that lets developers programmatically upload videos by URL, organise them into projects and channels, run live streams, manage member access plans, and pull video analytics. The API spans three hosts (api.dyntube.com for management, upload.dyntube.com for upload, stats.dyntube.com for analytics) and is aimed at apps that embed gated or paid video alongside their own product.

Use Cases

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

★ Course Platform Video Hosting

An online course platform uploads each lesson video by URL via POST /videos, organises them under a project per course and a channel per module, and delivers them to enrolled members through DynTube's playback layer. Because uploads are URL-based, the platform can re-encode original masters in storage and let DynTube fetch them directly.

POST /videos with the master video URL and project ID for a new lesson, then poll GET /videos/{id}/status until processing completes

Live Stream Scheduling for Webinars

A webinar tool creates a live stream with POST /live-streams, returns the stream key to the host, and tracks active streams against the per-account limit via GET /live-streams/limit. The same API surface lets the tool update or cancel the stream and then read the resulting recording back as a regular video.

POST /live-streams with title and start time to create a new stream, then GET /live-streams/{id} to retrieve the stream key for the broadcaster

Membership-Gated Video Access

A subscription product creates plans via POST /plans, enrols users with POST /members, and grants access to a channel of paid videos. When a member churns, POST /member-plans/{id}/cancel-now revokes access immediately; for end-of-period cancellation, POST /member-plans/{id}/cancel-at-period-end keeps access until renewal would have happened.

POST /plans for a new monthly tier, POST /members to enrol the user, then POST /member-plans/{id}/cancel-at-period-end if the user requests cancellation

Agent-Driven Video Management via Jentic

An AI assistant helping a creator publish a new lesson asks Jentic to 'upload a video to DynTube'. Jentic returns the POST /videos operation, the agent supplies the master URL and project ID, and DynTube ingests and processes the video - the bearer token is never exposed to the agent.

Use Jentic to search 'upload a video to DynTube', load the POST /videos operation, and execute it with the source URL and target project ID

Key Endpoints

39 endpoints — jentic publishes the only available openapi specification for the dyntube api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/videos

Upload a video by URL

GET

/videos/{id}/status

Get a video's processing status

POST

/live-streams

Create a live stream

POST

/channels

Create a channel

POST

/plans

Create a plan

POST

/members

Create a member

POST

/member-plans/{id}/cancel-now

Cancel a member plan immediately

POST

/logs/data

Get video analytics

POST

/videos

Upload a video by URL

GET

/videos/{id}/status

Get a video's processing status

POST

/live-streams

Create a live stream

POST

/channels

Create a channel

POST

/plans

Create a plan

POST

/members

Why though Jentic?

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

Credential isolation

The DynTube bearer token is stored encrypted in the Jentic vault. Agents receive a scoped execution token; the raw token never appears in agent context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'upload a video' or 'create a live stream') and Jentic returns the matching DynTube operation with its input schema and host context.

Time to first call

Direct integration: 2-3 days to wire up auth across three hosts, polling on processing status, and member-plan lifecycle. Through Jentic: under 1 hour - search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Dyte REST APIs

Live video meetings, recording, and livestreaming - real-time-first compared to DynTube's hosting-first scope

Choose Dyte for interactive meetings and real-time streaming; choose DynTube for hosted on-demand video and gated playback

Complementary

DynaPictures API

Generate video thumbnails and personalised cover images for DynTube videos

Pick DynaPictures to render a personalised thumbnail before publishing a DynTube video

Complementary

Dynosend API

Email new video releases or live stream invites to subscribers via Dynosend

Use Dynosend to notify subscribers of new DynTube uploads or live streams

FAQs

Specific to using DynTube API API through Jentic.

Why is there no official OpenAPI spec for the DynTube API?

DynTube does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the DynTube API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the DynTube API use?

The API uses bearer token authentication - pass your DynTube API key in the 'Authorization: Bearer <token>' header. The same token works across the api, upload, and stats hosts. Through Jentic, the token is held in the vault and the agent receives a scoped execution token instead.

Can I upload a video file directly with the DynTube API?

POST /videos accepts an upload via URL - DynTube fetches from the URL you provide. For binary uploads use the upload.dyntube.com host as documented in the spec; the management host (api.dyntube.com) only handles URL-based uploads and metadata.

What are the rate limits for the DynTube API?

The OpenAPI spec does not declare a numeric rate limit. DynTube applies plan-based caps on storage, bandwidth, and concurrent live streams - check GET /live-streams/limit and GET /account/plans before ramping up usage.

How do I publish a new video through Jentic?

Run pip install jentic, search for 'upload a video to DynTube', load the operation for POST /videos, then execute it with the source URL and the project ID. Poll GET /videos/{id}/status until the processing state reaches ready.

Can I cancel a member's plan at the end of the billing period?

Yes. POST /member-plans/{id}/cancel-at-period-end schedules cancellation so the member keeps access until renewal would have happened. POST /member-plans/{id}/cancel-now revokes access immediately, and POST /member-plans/{id}/resume reverses a scheduled cancellation.