OMR Reviews
find out more"I have finally found a tool that allows me to embed videos on my website in compliance with GDPR and without additional cookies."
The REST API for video.
Upload, encode, manage, deliver, and secure video through one API. Bearer token authentication, scoped permissions, webhook events, full documentation. Build your integration in a days, not a quarter.
REST API
Webhooks
Token security
Hosted in Europe
With us, you're in good company. Brands and companies that already trust us:
One API for the full video lifecycle.From upload to delivery, with events and access control built in.
The Ignite REST API covers every step: create and upload videos, manage metadata, categories, and tags, control encoding, configure the player, and query analytics. Webhooks notify your system when something changes. Scoped tokens control who can do what. With good documentation that you can drop in the AI-tool you use.
Upload and encode via API
Multipart upload
Uppy support
Replace without breaking embedsUpload videos via multipart upload for large files, or use the Uppy integration for browser-based uploads with progress tracking. The encoding pipeline runs automatically: adaptive bitrate streams, multiple resolutions, thumbnails.
Need to update an existing video? Replace the file, and every embed stays intact, same URL, same player, same page.Webhooks for real-time events
HMAC-SHA256
Delivery IDs
RetriesSubscribe to three lifecycle events: video.created, video.updated, and video.deleted. Each webhook delivers the complete video object as JSON. Payloads are signed with HMAC-SHA256. Every delivery carries a unique ID for idempotency, and failed deliveries are retried.
Player API for JavaScript control
Subscribe to playback events and control the player programmatically. The Ignite player uses the player.js standard: play, pause, seek, volume, mute. Listen for timeupdate, progress, ended, and error events. Query state with getPaused, getDuration, getCurrentTime. Works with any iframe embed. If you prefer your own player, the API delivers HLS stream URLs.
Token-based access control and CDN Security
Scoped API tokens
CDN Security
Time-limited accessTwo layers of security. API tokens: configurable permissions (read, create, update, delete), scoped to specific categories. No OAuth, Bearer token in the header. CDN Security (Enterprise): your backend calls the Ignite API to generate time-limited signed cookies that protect every file on your CDN, including video streams, manifests, thumbnails, and player assets. Configurable expiry from one minute to 24 hours. Infrastructure-level protection that prevents hotlinking, URL sharing, and content scraping.
CMS plugins and oEmbed
WordPress
Webflow
PayloadoEmbedNative plugins for WordPress, Webflow, and Payload handle embedding in the CMS editor. For every other CMS or tool that supports oEmbed, paste an Ignite video URL and it expands into the player. Standard iframe embeds work everywhere else.
AI features also available through the API
Transcribe, translate, generate descriptions, create chapters. All on European infrastructure, no training on your (customers) data.
Start building.
Create a free account, upload a video, and start using the API. Full access for 30 days, no payment details required. The docs cover every endpoint with example requests.
30 days full access
No credit card required
Full API access
With us, you're in good company. Brands and companies that already trust us:
We speak code.
Here some common questions. A lot more stuff gets answered within the API docs. But hey, feel free to ask if something is open or an API call doesn´t work.
