API for programmatic video

SDKs, Skills & Video API

Connect with an official SDK, give your AI agent a video skill, or call the API directly with your own API key.

SDKs

Install the SDK for your language and authenticate with your own API key to manage your videos, previews, files, and credits.

Get API key

AI Skills

Choose public, temporary previews or authenticated workflows for resources in your account.

Your API key required

Video API

rv-api

Use your own API key to create videos, render them, manage your files, and check your credits. The agent has the same access as your API key.

git clone https://github.com/renderingvideo/rv-api.git rv-api

Clone the skill repository into your agent’s skills directory, then load SKILL.md. Follow your agent’s instructions for its supported skill location. Keep API keys in environment variables.

Create an API key
Generate a scoped key from settings and send it as a Bearer token.
Send a schema
Use the RenderingVideo JSON shape with meta, assets, tracks, and clips.
Preview or render
Start with temporary previews, then convert to permanent render jobs when ready.

Code examples

The same API works from cURL, Node.js, Python, and any HTTP client.

curl -X POST https://renderingvideo.com/api/v1/video \
  -H "Authorization: Bearer sk-your-api-key" \
  -H "Content-Type: application/json" \
  -d '{"config":{"meta":{"version":"2.0.0","width":1280,"height":720,"fps":30},"tracks":[{"clips":[{"type":"text","start":0,"duration":3,"text":"Hello RenderingVideo"}]}]}}'

Core endpoints

Thin product APIs backed by the migrated RenderingVideo render service.

POST/api/v1/preview
Create temporary preview
Returns a playback URL for fast schema validation and review.
POST/api/v1/video
Create video task
Stores a permanent task and returns preview/config URLs.
POST/api/v1/video/:taskId/render
Trigger render
Consumes credits, starts the remote render pipeline, and tracks status.
GET/api/v1/files
List uploaded files
Use uploaded assets in schemas and keep media organized by user.
Authentication
Public API endpoints require an API key in the Authorization header. Dashboard pages continue to use the signed-in session.