Bản lưu ngày / Snapshot of 2026-10-02 · Xem bản mới nhất / See the latest version
WanduraDocsBeta
BetaThese docs are in beta and change often. Something wrong, unclear or missing? Tell us.
Get started

Architecture

Markdown
On this page

TL;DR — Your server syncs Wandura's catalog into your own database, applies your own paywall, and asks Wandura for a short-lived ticket each time a viewer starts an episode. The app plays that ticket with the licensed Player SDK. Wandura checks your licence on every ticket; you decide which viewer may watch what. Content with nothing to protect can use the lighter open video path instead.

The pieces

WanduraYour systemsGET /catalog, every 15-60minplay request + devicevaluesPOST /playbackticketticketencrypted stream + keysYour appPlayer SDKYour backendAPI keys, paywallYour databasecatalog copyDelivery APIStreaming network
Piece Runs Talks to Holds
Catalog sync job Your backend, on a schedule GET /catalog A metadata:read key; writes your film tables
Ticket endpoint Your backend, per play POST /playback A playback key; your paywall
App Viewer's phone Your backend only One ticket per episode, in memory
Player SDK Inside your app Wandura's streaming network Its licence file; the device key, which never leaves the device
Creatives sync (optional) Your backend GET /creatives A creatives:export key

One play, step by step:

Wandura streaming networkWandura Delivery APIYour backendViewer device (Player SDK)Episode + device ID + device public keyYour paywall: may this viewer watch?POST /api/delivery/v1/playback (Bearer key)Check key scope and licence for this filmvid, play_auth_token, expires_at, protection, subtitlesvid, play_auth_token, subtitlesPlayer SDK loads the encrypted stream and keysVideo plays

The key that decrypts the video is bound to the viewer's device: it never passes through your backend or the API response.

Who does what

Area Wandura Your team
Films Produces, encodes and protects every film; keeps titles, posters, order and subtitles up to date. Shows them in your app, in the order and with the text you receive.
Rights Grants your organisation a licence per film, with an optional window, and checks it on every ticket. Follows any other limits of your contract (for example countries).
Viewers and money Nothing: the API has no viewer identity. Accounts, sign-in, paywall, free episodes, coins, subscriptions, refunds, viewer support.
Keys Nothing to issue: your Admins and Developers create, rotate and revoke every key themselves, playback keys included. Keeps keys on your servers; revokes a key that may have leaked, then tells Wandura.
Player Registers your app IDs and issues the Player SDK licence (your organisation pays for it). Integrates the Player SDK in each app.
Playback Signs a ticket for one episode on one device and records it. Asks for a ticket only for episodes the viewer may watch.
Usage Counts views from play tickets. Sends "intent": "play" when a viewer starts an episode and "prefetch" when preloading.

Choose a model

Standard (licensed films) Managed Open video
For Every partner app showing Wandura films Only apps operated by the Wandura group, by separate agreement Content with no rights to protect, for example fitness clips
Film list Your server polls GET /catalog Agreed with Wandura's content team GET /videos
Playback A ticket per episode from POST /playback Set up with Wandura Plain signed MP4 links, valid 1 hour
Player The Player SDK (licensed) The Player SDK (licensed) Any standard player
Licence check On every ticket By contract Per organisation and per app key
Start with Integration roadmap Contact Wandura Open video

If you are not sure, you are on the standard model. The managed model is not offered to external partners.

Updated 2 Oct 2026 · Change history (1)

↑↓ selectEnter openEsc close

Send feedback

Your message goes straight to the Wandura team. It includes the address of this page.

0 / 4000