Everything the Admin Can Do, Your Code Can Do

Every streaming operation has a moment where the manual approach stops working. Three hundred titles arrive from a distributor with metadata in a spreadsheet. A weekly show needs publishing at the same hour every Thursday. A rights window closes at midnight on the thirty first and forty titles have to come down with it. None of that should involve a person clicking through an interface, and none of it needs to. The Vodlix API covers the same ground the admin area does, which means anything your team can do in the back end, a script or another system can do on a schedule.

The surface follows the shape of the platform rather than a separate integration model, so anyone who knows the admin area already knows roughly what is available.

Catalogue. Videos, series, seasons and episodes, with the full lifecycle on each: create, read, update, publish, unpublish, and trash or restore. New video is ingested from a public HTTPS URL rather than uploaded through your own infrastructure.

Artwork. Attach landscape, portrait, square or logo images from a public URL, list the poster frames generated from a video, and choose which one becomes the thumbnail.

Live. Channels behave like videos, with their own create, update, publish and retire operations.

Merchandising. Content lists and content list groups, the items inside them, and their ordering. Lists can be activated and deactivated, so a seasonal row is switched off rather than rebuilt.

Reference and reporting. Category ids for the cloud you are working against, catalogue and subscriber counts, and platform details including the software version you are running.

One thing worth knowing before you write against it: category ids are per cloud rather than global, so read the category list first and use the ids it returns instead of assuming a name maps to the same number everywhere.

Automation is only worth having if a mistake is survivable, so destructive operations are deliberately hard to make permanent. Videos and live channels go to the trash and can be restored. Series, seasons, content lists and groups are deactivated rather than removed, which means a wrong call takes something off the storefront without destroying the record behind it.

Updates are partial as well. Sending one field changes that field and leaves the rest alone, so a script that only touches descriptions cannot quietly wipe the categories on three hundred titles. Where a value does replace rather than merge, such as the category list on a video, that is documented so it is a decision rather than a surprise.

Access is granted per integration, and read access is separate from write access, so a reporting job that only needs to count things never has permission to change them.

The common cases are migration, ingest and reporting. Moving a catalogue from another platform is an API job rather than a manual one, and it is the difference between a launch measured in days and one measured in months. Recurring ingest from a distributor or a production workflow runs unattended once it is written. Reporting pulls figures into whatever your finance team already uses instead of asking somebody to export a screen every Monday.

It also joins your platform to the rest of your business. Push a new title into your CMS and your marketing site the moment it is published, or hand your content lists to a recommendation service and write the results back. Where an integration needs more than the API alone provides, our custom plugin service builds the missing piece against the same platform.

Analytics is available through the API where a stats service is configured on your cloud, which is worth confirming during setup rather than discovering later. The reports and analytics page covers what is measured.