SuperDuperVideos
Start free
Documentation home
Developer guide 10 min

Build a video placement, not a video infrastructure team.

The current developer surface is the public embed contract. Account and media-management APIs are not yet offered as a public integration, but the embed workflow is stable enough to build into a website today.

Reviewed August 17, 2026

Browse documentation
1

Treat the publication ID as the public contract

A published video receives a public ID beginning with `ve_`. Use that value in page markup. Do not expose internal database IDs, private source URLs, API credentials, or authenticated dashboard responses.

2

Load one runtime and render one marker per placement

The preferred integration is deliberately small. One page can contain several markers while loading the shared runtime once.

HTML integration 
<div
  data-sdv-video="ve_replace_me"
  style="display:block;width:100%;aspect-ratio:16/9;background:#020617;"
></div>
<script async src="https://embed.superdupervideos.com/v1/embed.js"></script>
3

Client-side navigation and dynamic content

The runtime discovers markers added after its initial load, which supports route transitions, tabs, modals, filters, and CMS-rendered collections. Preserve a stable marker for each placement and avoid repeatedly inserting duplicate runtime scripts.

  • Load the runtime in a shared layout when video appears throughout the application
  • Reserve aspect ratio before initialization
  • Use a stable publication ID
  • Test navigation without a full page refresh
4

Let the page coordinate many players

Multiple top-level script players share resource scheduling, runtime loading, manifest promises, connection hints, and event batching. Direct play intent takes priority over speculative work for offscreen players.

Prefer the universal script for galleries. Use iframes when isolation or a constrained editor matters more than shared page work.
5

Keep authorization at the publication boundary

Approve exact destination origins in the dashboard. The public player validates the host against the published origin set. A public publication ID is not a replacement for that policy and should never grant authenticated account access.

6

Public management API: coming soon

A documented API for programmatic video, upload, publication, analytics, and webhook workflows is not publicly available yet. When it ships, the API reference will be generated from a versioned OpenAPI contract rather than maintained as a separate set of handwritten endpoint pages.

Still looking for the missing step?

Browse the Help Center for concise answers, or send us the page and result you are trying to produce.

Open Help Center Contact us