Frequently Asked Questions

New video is ingested through the Vodlix API by providing a public HTTPS URL. Vodlix fetches and transcodes the file, so you do not stream binary uploads through your own infrastructure.

Yes. The Vodlix REST API mirrors the admin area, with familiar REST conventions and predictable responses, so anyone who knows the UI knows roughly what the API can do.

Yes. Vodlix content lists, list groups, their items and ordering can all be created, updated, activated and deactivated through the API, so merchandising can be automated.

The Vodlix API provides catalogue and user counts, a sales summary for a date range, category IDs and platform details such as the software version, so integrations always know what they are working against.

No, and this is the most common thing to get wrong. Categories are per cloud, so read the category list for the platform you are working against and use the ids it returns rather than assuming a name maps to the same number everywhere.

Where a stats service is configured on your cloud, yes, covering headline figures, realtime activity and top performing content. It is worth confirming that during setup, because it is provisioned separately from the catalogue operations.

It is one of the most common reasons operators use it. Bringing a catalogue across programmatically turns a migration into a repeatable job rather than months of manual entry, and it can be run again to catch anything that changed while you were moving.

With an API key created under Apps & APIs in the admin and sent in the X-Api-Key header. A server key acts with the permissions of the user it belongs to and can reach admin routes, so it belongs on a back end. A client key is safe for browser code and is blocked from every admin route. Keys can carry an expiry date, and deleting a key revokes it at once.

Yes. The Vodlix API lists shorts series, their volumes and each short with its title, length, portrait thumbnail and watch link, so a mobile app or a custom front end can show them.

Yes. Vodlix has built-in SSAI integrations for Publica and Aniview. You switch each one on in your settings; Publica needs your network and stream IDs, and Aniview needs your publisher ID.

Vodlix has 39 built-in macros in five groups: session and network, device and app, privacy and consent, content, and geo and URL. You pick which ones to add to video addresses and can rename each one to match your ad server.

The list includes Stripe, PayPal, Authorize.net, PayStack, Square, Flutterwave, iPay88, CCBill, Rapyd, Tingg, Segpay, Magna, PayGate, PayPlus, Pay.nl and Emis, plus Apple, Google Pay and Roku Pay for purchases made inside the apps. You switch on the ones your market uses, and you can allow a different set for rentals than for subscriptions.

Yes, for the cases the controls do not reach. Most services never need it, and the ones that do usually need it for something specific rather than for wholesale changes, so it exists as a route rather than as the main path.

Vodlix TMDB integration connects your platform to The Movie Database so you can fetch cast, crew, production details, artwork, trailers and synopses into your catalogue automatically.

Vodlix pulls cast and crew, production year, synopsis, genres, posters and backdrops, trailers and other title details from TMDB, and creates artist records for cast members.

No. With Vodlix TMDB integration you search for a title, confirm the match and the metadata, artwork and cast records populate automatically, with no manual typing.

Yes. Vodlix syncs vital information from TMDB automatically, so metadata and artwork stay up to date without someone updating each title by hand.

You can. The same accounts are available through the Vodlix REST API, so an existing customer relationship tool, help desk or internal dashboard can create users, read their subscriptions and act on them without anybody opening the admin area. The admin area and the API work on one set of records, so the two never drift apart.

Yes. The Import User Accounts screen takes a CSV file and creates or updates accounts in bulk, and the member list exports all, active, inactive or banned users, so accounts you already hold are brought in rather than rebuilt one at a time. Anything the importer does not cover can be handled through the API, which is usually the better route when the migration also has to carry subscriptions or purchase history with it.

Programmatically. Bulk delivery for the files and the API for the metadata turns a migration into a repeatable job that can be run again to catch anything that changed while you were moving, which is what keeps a platform switch to days rather than months.