This project is not covered by Drupal’s security advisory policy.

The api.video module integrates api.video with Drupal Media. It turns your api.video account into a read-only video library (DAM): editors browse and pick existing videos and live streams from the Media Library, and Drupal displays them with the official api.video Player SDK. Uploading and editing videos stays in api.video.

This project is under active development. Features below describe the planned 1.0 scope.

Features

  • Media sources for api.video videos and live streams, created from an ID or an embed URL.
  • Media Library browser: search your api.video library by title and tag, with pagination and preview.
  • Remote metadata (title, description, tags, thumbnail, duration, status) mapped to Drupal fields, with local override fields that are never overwritten by synchronization.
  • Player SDK field formatter with a privacy-friendly facade mode (local thumbnail, player loaded on click) and DOM events for analytics or consent management.
  • Signed webhooks (HMAC SHA256) to keep metadata and cache in sync, with cron and Drush fallback.
  • Private videos: one-time tokens and private sessions generated server side, never stored in page cache.
  • Display of existing captions, transcripts, chapters and AI summaries generated in api.video.
  • Basic viewing analytics per media.

Use cases: centralized video library shared by several Drupal sites, live events with automatic replay, accessible video (captions and transcripts), member-only video content.

Post-Installation

  1. Create a key holding your api.video API key with the Key module.
  2. Go to Configuration > Media > api.video, select the environment (sandbox or production) and the key, then test the connection.
  3. Create a media type using the "api.video video" or "api.video live stream" source and configure field mapping.
  4. Optionally register the webhook from the settings page (requires a publicly reachable site).

Additional Requirements

Recommended modules/libraries

  • The api.video Player SDK can be served from a local copy in /libraries instead of the CDN, for strict Content Security Policy or privacy requirements.

Similar projects

No other module integrates api.video. Core oEmbed cannot be used because api.video does not provide an official oEmbed endpoint. Cloudflare Stream and Brightcove integrate other video platforms.

Community Documentation

Project information

Releases