Use case

Import / migrate from a URL

Already have video sitting in S3, R2, Bunny, or any object store? rehelios imports each file by its public URL, fetches it server-side, stores it durably, and runs the full transcode pipeline. A video.ready webhook fires per file when encoding completes — the recommended path for bulk migrations with no client-side re-upload.

Start free Read the docs

When to use rehelios for this

Choose URL import when you're migrating an existing catalog or ingesting third-party video, and you want the source fetched and transcoded server-side rather than streamed through a client.

  • Server-side fetch — no re-upload from a client
  • Per-file video.ready webhooks for bulk jobs
  • Works from S3, R2, Bunny or any public URL

How it works

  1. 1

    List your sources

    Collect the public URL of each existing video file you want to migrate.

  2. 2

    Import each

    Call POST /v1/videos/import (or rehelios import ) per file; rehelios fetches it server-side.

  3. 3

    Listen for ready

    Each file fires a video.ready webhook when its transcode completes.

  4. 4

    Cut over

    Swap your player to the returned playbackUrl once the library is ready.

Fastest path

One command (or one MCP tool call) gets you started:

shell 
# migrate one file; loop this over your catalog
npx @rehelios/cli import https://old-cdn/video-001.mp4 --json

Agents: see /agents and /mcp.