API & player.js
Livid embeds fully support the player.js spec, letting you control playback and track viewer events directly from your page while our API and SDK are in development.
We're currently working on our API and SDK offerings- In the meantime, Livid embeds have full support for the player.js spec, which lets your page send messages to and from the Livid iframe. You can control playback, read the current position, and listen for events as the viewer watches.
If you have any questions about player.js, or you're building something with player.js and hit a wall, get in touch - we'd like to hear what you're trying to do, especially while the API and SDK are still taking shape!
A couple of notes for specific player.js use cases:
Autoplay and iOS: Browsers require an explicit user interaction before a video can start playing with sound. This isn't a Livid restriction - it's enforced by the browser.
If you're calling play() before the viewer has interacted with the page, the video needs to be muted for the call to succeed. This matters most on iOS, which is the strictest about it. There are workarounds that function in some browsers, but they behave inconsistently across devices, so muted autoplay is currently the most reliable approach.
Analytics data: Each video's page in your Livid dashboard shows watch time and completion data. That data is anonymised for privacy reasons, so it can't be tied back to an individual viewer.
If you need per-viewer insight - for example, tracking whether a specific student finished a lesson - you'll need to capture it on your own side using the player.js events and associate it with your own user records.
If you're interested in being notified when our API and SDK go live, let us know and we'll add you to the list- and as always feel free to reach out with any questions.