Change history
Every change to this page, newest first. Expand an entry to see what changed.
- 2 Oct 2026 · +37 −51 lines
Show changes
# Before you start - > **TL;DR** — To stream Wandura films your team needs three things ready before coding: an organisation on partner.wandura.ai with licences for your films, a **Player SDK licence** for each app, which your organisation pays for (list price about **US$2,860 per app per year** for iOS + Android), and your final app IDs. Then you build two pieces: a **backend** that syncs the catalog and requests playback tickets, and an **app** that plays episodes through the Player SDK. The full path is in the [integration guide](integration-guide.md). + > **TL;DR** — Before coding, your team needs: an organisation on partner.wandura.ai with licences for your films, a **Player SDK licence** for each app (your organisation pays; list price about **US$2,860 per app per year** for iOS + Android), and your **final** app IDs. Onboarding happens in your team's own Wandura Discord channel. You can make your first API calls before the Player SDK is ready; playing an episode needs it. - > **Note:** Showing only videos with no rights to protect (for example fitness clips)? The [open video](open-video.md) path needs no Player SDK licence. + > **Note:** Showing only videos with no rights to protect (for example fitness clips)? The [open video](concepts/open-video.md) path needs no Player SDK licence. ## 1. Prepare (no code yet) {#prepare} - | Ready? | Item | Why you need it | Details | - |---|---|---|---| - | ☐ | Organisation on partner.wandura.ai + the email of its **Admin** | Every key and licence belongs to it | [Integration guide · Phase 0](integration-guide.md#phase-0) | - | ☐ | Emails of your backend developers | They get the **Developer** role to manage keys | [Roles](../partners/roles.md) | - | ☐ | The list of films and licence dates in your agreement | The catalog shows only films your licence covers | [Catalog](concepts/catalog.md) | - | ☐ | **Final** iOS bundle ID and Android package name | The Player SDK licence is tied to them and cannot be moved to other IDs later | [Player SDK licence](#player-sdk-licence) | - | ☐ | Your environments (for example staging and production) | Each one needs its own playback key, which your developers create themselves | [Authentication](authentication.md) | - | ☐ | Budget for the Player SDK licence: your organisation pays for it | Agree the tier and start date with Wandura | [Player SDK licence](#player-sdk-licence) | - | ☐ | Access to your team's Wandura Discord channel | Onboarding, licences and go-live all happen there | [Get onboarded](#get-onboarded) | + | Ready? | Item | Why | + |---|---|---| + | ☐ | Your organisation name and the email of its **Admin** | Every key and licence belongs to the organisation | + | ☐ | Emails of your backend developers | They get the **Developer** role to manage keys ([Roles](../partners/roles.md)) | + | ☐ | The films and licence dates in your agreement | The catalog shows only films whose licence is active | + | ☐ | **Final** iOS bundle ID and Android package name | The Player SDK licence is bound to them and cannot be moved later | + | ☐ | Budget and start date for the Player SDK licence | See [Player SDK](player-sdk/index.md) | + | ☐ | Your expected peak: plays per minute at launch | Wandura checks your limits against it before go-live | ## 2. Get onboarded {#get-onboarded} - Each partner team works with Wandura in **its own Discord channel**: your team's Wandura Discord channel. Onboarding runs in the six steps below, in this order. Each step starts once Wandura has what it needs from you. + Each partner team works with Wandura in **its own Discord channel**. Your Wandura contact invites your team to it when your agreement is signed; if you have no access yet, ask the person who signed the agreement. Onboarding runs in these steps: | Step | What happens | What you send | |---|---|---| - | 1. Ask | You post in your team's Wandura Discord channel that you are ready to integrate. | Your organisation name and the email of the person who will be its **Admin**. | - | 2. Organisation and members | Wandura creates your organisation on [partner.wandura.ai](https://partner.wandura.ai) and invites your Admin and your developers. Developers get the **Developer** role. | The emails of your backend developers. | - | 3. Test organisation and film licences | Wandura decides whether you test in a separate test organisation, and licenses the films you test with to the organisation you test in. | The films you want to test with, from your agreement. | - | 4. Player SDK trial | Wandura registers your app IDs and issues a trial Player SDK licence. You get access to the Player SDK guide: it is available after onboarding, on the portal, under partner.wandura.ai → **Developers** → **Player SDK** (sign-in required, **Developer** or **Admin** role). | Your final iOS bundle ID and Android package name. | - | 5. Staging keys | Your developers create their staging keys themselves on the **Developers** page, the playback key included (**Stream films in an app**). If a playback key leaks, anyone can stream your licensed films, so revoke it immediately. | Nothing: no request to Wandura is needed. | - | 6. Production key and paid licence | At go-live, your developers create the production playback key the same way, and the paid Player SDK licence replaces the trial. | The result of your [test plan](integration-guide.md#phase-5) and your planned go-live date. | - - ## 3. Player SDK licence and price {#player-sdk-licence} + | 1. Ask | You post in your channel that you are ready to integrate. | Organisation name, Admin email. | + | 2. Organisation and members | Wandura creates your organisation on [partner.wandura.ai](https://partner.wandura.ai) and invites your Admin and developers. | Developer emails. | + | 3. Film licences | Wandura licenses your films to your organisation. | The film list from your agreement. | + | 4. Test organisation | Wandura creates your test organisation next to your real one. | Ask for it in your channel. | + | 5. Player SDK trial | Wandura registers your app IDs and issues a trial licence. You get the step-by-step Player SDK guide on the portal. | Final bundle ID and package name. | + | 6. Your keys | Your developers create their own keys on **Developers**, playback keys included. | Nothing. | + | 7. Go-live | Paid Player SDK licence, limit review, production keys. | See [Go-live checklist](production/go-live.md). | - Episodes are encrypted, so your app must play them with the Player SDK. A standard HLS player cannot decrypt them. Wandura registers your app IDs and issues the Player SDK licence; your organisation pays for it. + Every partner gets a **test organisation** next to its real one: sample films only, plays never counted as views or usage, and errors you can trigger on demand with the `Wandura-Simulate` header. See [Testing](guides/testing.md). - | Licence | Covers | List price | Notes | - |---|---|---|---| - | **Standard** — mobile | iOS **and** Android of **one** app (one bundle ID + one package name) | about **US$2,860 per app per year** | Enough to play Wandura's encrypted films. | - | Premium — mobile | Same, with extra vendor features | about US$32,790 per app per year | Not needed for Wandura films. | - | Web player | Web | no licence fee at list price | Check with Wandura before planning a web app. | - | Trial | One app, for testing | free, about 30 days | Upgrading a trial to a paid licence does **not** require a new app release. | + ## 3. What you can do before the Player SDK is ready {#before-the-sdk} - - **One licence per app.** Two different apps need two licences, even if they come from the same company. - - **IDs are final.** Changing the bundle ID or package name after the licence is issued is not supported: the app loses the right to use the SDK. - - **Prices change.** The figures above are list prices. Your agreement with Wandura sets the real price. + | Possible from day one | Needs the Player SDK on a real device | + |---|---| + | Create keys, read `GET /config` | Request a playable ticket | + | Build and run the catalog sync job | Play an episode | + | Build your paywall and episode screens | Test subtitles, expiry and recovery | + | Sync creatives | | - ## 4. What your backend builds {#backend} + Start with [Quickstart · Part A](quickstart.md#part-a). - | Build | What it does | Details | - |---|---|---| - | ☐ Key storage | Keeps Wandura API keys on your servers only, never in the app | [Authentication](authentication.md) | - | ☐ Catalog sync job | Polls the catalog every 15–60 minutes and stores films and episodes in your database | [Phase 2](integration-guide.md#phase-2) | - | ☐ Films + episodes tables | Your own copy of titles, posters, order, free episodes and availability | [What to store](integration-guide.md#what-to-store) | - | ☐ Ticket endpoint in your API | Checks your viewer and your paywall, then asks Wandura for a ticket for one episode | [Phase 3](integration-guide.md#phase-3) | - | ☐ Prefetch + retry | Requests tickets for the next two episodes; replaces expired tickets | [Prefetch](integration-guide.md#prefetch) | - | ☐ Error mapping + monitoring | Turns API errors into viewer messages; watches error rates | [Errors](concepts/errors.md) | + ## 4. The Player SDK licence {#player-sdk-licence} - ## 5. What your app builds {#app} + Licensed episodes are encrypted and play only through the Player SDK. Wandura registers your app IDs and issues the licence; your organisation pays for it. Price, tiers, versions, platforms and prerequisites: [Player SDK overview and licence](player-sdk/index.md). - | Build | What it does | Details | - |---|---|---| - | ☐ Player SDK integration (per platform) | Plays encrypted episodes; the Player SDK guide on the portal names the calls | [Playback](concepts/playback.md) | - | ☐ Device values | Reads two values from the SDK and sends them with each ticket request | [Device values](concepts/playback.md#send-the-device-values) | - | ☐ Paywall screens | Free episodes, unlock, subscription — your rules | [Paywall first](integration-guide.md#paywall-first) | - | ☐ Subtitles | Loads the WebVTT files listed in each ticket | [Subtitles](integration-guide.md#subtitles) | - | ☐ Viewer messages | What the viewer sees for each error | [Viewer messages](integration-guide.md#viewer-messages) | + ## 5. What you will build {#what-you-build} - ## 6. Before go-live {#go-live} + | Backend | App | + |---|---| + | [Catalog sync job](guides/catalog-sync.md) | Player SDK integration ([iOS](player-sdk/ios.md), [Android](player-sdk/android.md)) | + | [Ticket endpoint with your paywall](guides/playback-flow.md) | Reading device values, calling your backend | + | [Retries that degrade gently](guides/smooth-playback.md) | Spinner, not errors, under load | + | [Safe logging and monitoring](production/observability.md) | [Subtitles](guides/subtitles.md) | - - ☐ Staging passes the [test plan](integration-guide.md#phase-5). - - ☐ Production key and paid Player SDK licence are in place. - - ☐ The [go-live checklist](integration-guide.md#go-live-checklist) is done with Wandura. + The whole path, in order: [Integration roadmap](integration-guide.md).
- 2 Oct 2026 · +1 −1 lines
Show changes
⋯ > **TL;DR** — To stream Wandura films your team needs three things ready before coding: an organisation on partner.wandura.ai with licences for your films, a **Player SDK licence** for each app, which your organisation pays for (list price about **US$2,860 per app per year** for iOS + Android), and your final app IDs. Then you build two pieces: a **backend** that syncs the catalog and requests playback tickets, and an **app** that plays episodes through the Player SDK. The full path is in the [integration guide](integration-guide.md). - > **Note:** Showing only videos with no rights to protect (for example fitness clips)? The [open video](open-video.md) path (coming soon) needs no Player SDK licence. + > **Note:** Showing only videos with no rights to protect (for example fitness clips)? The [open video](open-video.md) path needs no Player SDK licence. ## 1. Prepare (no code yet) {#prepare} ⋯
- 1 Oct 2026 · +4 −4 lines
Show changes
⋯ | ☐ | The list of films and licence dates in your agreement | The catalog shows only films your licence covers | [Catalog](concepts/catalog.md) | | ☐ | **Final** iOS bundle ID and Android package name | The Player SDK licence is tied to them and cannot be moved to other IDs later | [Player SDK licence](#player-sdk-licence) | - | ☐ | Your environments (for example staging and production) | Each one needs its own playback key | [Authentication](authentication.md) | + | ☐ | Your environments (for example staging and production) | Each one needs its own playback key, which your developers create themselves | [Authentication](authentication.md) | | ☐ | Budget for the Player SDK licence: your organisation pays for it | Agree the tier and start date with Wandura | [Player SDK licence](#player-sdk-licence) | - | ☐ | Access to your team's Wandura Discord channel | Onboarding, licences, keys and go-live all happen there | [Get onboarded](#get-onboarded) | + | ☐ | Access to your team's Wandura Discord channel | Onboarding, licences and go-live all happen there | [Get onboarded](#get-onboarded) | ## 2. Get onboarded {#get-onboarded} ⋯ | 3. Test organisation and film licences | Wandura decides whether you test in a separate test organisation, and licenses the films you test with to the organisation you test in. | The films you want to test with, from your agreement. | | 4. Player SDK trial | Wandura registers your app IDs and issues a trial Player SDK licence. You get access to the Player SDK guide: it is available after onboarding, on the portal, under partner.wandura.ai → **Developers** → **Player SDK** (sign-in required, **Developer** or **Admin** role). | Your final iOS bundle ID and Android package name. | - | 5. Staging keys | Your developers create read-only keys themselves on the **Developers** page. Wandura issues a playback key for staging. | Which environments need a playback key, for example staging. | - | 6. Production key and paid licence | At go-live, Wandura issues your production playback key, and the paid Player SDK licence replaces the trial. | The result of your [test plan](integration-guide.md#phase-5) and your planned go-live date. | + | 5. Staging keys | Your developers create their staging keys themselves on the **Developers** page, the playback key included (**Stream films in an app**). If a playback key leaks, anyone can stream your licensed films, so revoke it immediately. | Nothing: no request to Wandura is needed. | + | 6. Production key and paid licence | At go-live, your developers create the production playback key the same way, and the paid Player SDK licence replaces the trial. | The result of your [test plan](integration-guide.md#phase-5) and your planned go-live date. | ## 3. Player SDK licence and price {#player-sdk-licence} ⋯
- 1 Oct 2026 · +21 −8 lines
Show changes
⋯ | ☐ | Your environments (for example staging and production) | Each one needs its own playback key | [Authentication](authentication.md) | | ☐ | Budget for the Player SDK licence: your organisation pays for it | Agree the tier and start date with Wandura | [Player SDK licence](#player-sdk-licence) | - | ☐ | How to reach Wandura (the channel named in your agreement) | For licences, keys and go-live | [Support](help/support.md) | + | ☐ | Access to your team's Wandura Discord channel | Onboarding, licences, keys and go-live all happen there | [Get onboarded](#get-onboarded) | - ## 2. Player SDK licence and price {#player-sdk-licence} + ## 2. Get onboarded {#get-onboarded} - Episodes are encrypted, so your app must play them with the Player SDK that Wandura licenses to you. A standard HLS player cannot decrypt them. + Each partner team works with Wandura in **its own Discord channel**: your team's Wandura Discord channel. Onboarding runs in the six steps below, in this order. Each step starts once Wandura has what it needs from you. + | Step | What happens | What you send | + |---|---|---| + | 1. Ask | You post in your team's Wandura Discord channel that you are ready to integrate. | Your organisation name and the email of the person who will be its **Admin**. | + | 2. Organisation and members | Wandura creates your organisation on [partner.wandura.ai](https://partner.wandura.ai) and invites your Admin and your developers. Developers get the **Developer** role. | The emails of your backend developers. | + | 3. Test organisation and film licences | Wandura decides whether you test in a separate test organisation, and licenses the films you test with to the organisation you test in. | The films you want to test with, from your agreement. | + | 4. Player SDK trial | Wandura registers your app IDs and issues a trial Player SDK licence. You get access to the Player SDK guide: it is available after onboarding, on the portal, under partner.wandura.ai → **Developers** → **Player SDK** (sign-in required, **Developer** or **Admin** role). | Your final iOS bundle ID and Android package name. | + | 5. Staging keys | Your developers create read-only keys themselves on the **Developers** page. Wandura issues a playback key for staging. | Which environments need a playback key, for example staging. | + | 6. Production key and paid licence | At go-live, Wandura issues your production playback key, and the paid Player SDK licence replaces the trial. | The result of your [test plan](integration-guide.md#phase-5) and your planned go-live date. | + + ## 3. Player SDK licence and price {#player-sdk-licence} + + Episodes are encrypted, so your app must play them with the Player SDK. A standard HLS player cannot decrypt them. Wandura registers your app IDs and issues the Player SDK licence; your organisation pays for it. + | Licence | Covers | List price | Notes | |---|---|---|---| ⋯ - **One licence per app.** Two different apps need two licences, even if they come from the same company. - **IDs are final.** Changing the bundle ID or package name after the licence is issued is not supported: the app loses the right to use the SDK. - - **Prices change.** The figures above are list prices. Your organisation pays for the Player SDK licence; your agreement with Wandura sets the real price. + - **Prices change.** The figures above are list prices. Your agreement with Wandura sets the real price. - ## 3. What your backend builds {#backend} + ## 4. What your backend builds {#backend} | Build | What it does | Details | ⋯ | ☐ Error mapping + monitoring | Turns API errors into viewer messages; watches error rates | [Errors](concepts/errors.md) | - ## 4. What your app builds {#app} + ## 5. What your app builds {#app} | Build | What it does | Details | |---|---|---| - | ☐ Player SDK integration (per platform) | Plays encrypted episodes; the onboarding pack names the calls | [Playback](concepts/playback.md) | + | ☐ Player SDK integration (per platform) | Plays encrypted episodes; the Player SDK guide on the portal names the calls | [Playback](concepts/playback.md) | | ☐ Device values | Reads two values from the SDK and sends them with each ticket request | [Device values](concepts/playback.md#send-the-device-values) | | ☐ Paywall screens | Free episodes, unlock, subscription — your rules | [Paywall first](integration-guide.md#paywall-first) | ⋯ | ☐ Viewer messages | What the viewer sees for each error | [Viewer messages](integration-guide.md#viewer-messages) | - ## 5. Before go-live {#go-live} + ## 6. Before go-live {#go-live} - ☐ Staging passes the [test plan](integration-guide.md#phase-5). ⋯
- 1 Oct 2026 · +6 −6 lines
Show changes
# Before you start - > **TL;DR** — To stream Wandura films your team needs three things ready before coding: an organisation on partner.wandura.ai with licences for your films, a **Player SDK licence** for each app (list price about **US$2,860 per app per year** for iOS + Android), and your final app IDs. Then you build two pieces: a **backend** that syncs the catalog and requests playback tickets, and an **app** that plays episodes through the Player SDK. The full path is in the [integration guide](integration-guide.md). + > **TL;DR** — To stream Wandura films your team needs three things ready before coding: an organisation on partner.wandura.ai with licences for your films, a **Player SDK licence** for each app, which your organisation pays for (list price about **US$2,860 per app per year** for iOS + Android), and your final app IDs. Then you build two pieces: a **backend** that syncs the catalog and requests playback tickets, and an **app** that plays episodes through the Player SDK. The full path is in the [integration guide](integration-guide.md). > **Note:** Showing only videos with no rights to protect (for example fitness clips)? The [open video](open-video.md) path (coming soon) needs no Player SDK licence. ⋯ | ☐ | **Final** iOS bundle ID and Android package name | The Player SDK licence is tied to them and cannot be moved to other IDs later | [Player SDK licence](#player-sdk-licence) | | ☐ | Your environments (for example staging and production) | Each one needs its own playback key | [Authentication](authentication.md) | - | ☐ | Who pays for the Player SDK licence, and from when | Settled in your agreement with Wandura | [Player SDK licence](#player-sdk-licence) | - | ☐ | A named contact at Wandura | For licences, keys and go-live | [Support](help/support.md) | + | ☐ | Budget for the Player SDK licence: your organisation pays for it | Agree the tier and start date with Wandura | [Player SDK licence](#player-sdk-licence) | + | ☐ | How to reach Wandura (the channel named in your agreement) | For licences, keys and go-live | [Support](help/support.md) | ## 2. Player SDK licence and price {#player-sdk-licence} ⋯ | **Standard** — mobile | iOS **and** Android of **one** app (one bundle ID + one package name) | about **US$2,860 per app per year** | Enough to play Wandura's encrypted films. | | Premium — mobile | Same, with extra vendor features | about US$32,790 per app per year | Not needed for Wandura films. | - | Web player | Web | no licence fee at list price | Check with your contact before planning a web app. | + | Web player | Web | no licence fee at list price | Check with Wandura before planning a web app. | | Trial | One app, for testing | free, about 30 days | Upgrading a trial to a paid licence does **not** require a new app release. | - **One licence per app.** Two different apps need two licences, even if they come from the same company. - **IDs are final.** Changing the bundle ID or package name after the licence is issued is not supported: the app loses the right to use the SDK. - - **Prices change.** The figures above are list prices. Your agreement with Wandura sets the real price and who pays it. + - **Prices change.** The figures above are list prices. Your organisation pays for the Player SDK licence; your agreement with Wandura sets the real price. ## 3. What your backend builds {#backend} ⋯ - ☐ Staging passes the [test plan](integration-guide.md#phase-5). - ☐ Production key and paid Player SDK licence are in place. - - ☐ The [go-live checklist](integration-guide.md#go-live-checklist) is done with your Wandura contact. + - ☐ The [go-live checklist](integration-guide.md#go-live-checklist) is done with Wandura.
- 1 Oct 2026 · +2 −0 lines
Show changes
⋯ > **TL;DR** — To stream Wandura films your team needs three things ready before coding: an organisation on partner.wandura.ai with licences for your films, a **Player SDK licence** for each app (list price about **US$2,860 per app per year** for iOS + Android), and your final app IDs. Then you build two pieces: a **backend** that syncs the catalog and requests playback tickets, and an **app** that plays episodes through the Player SDK. The full path is in the [integration guide](integration-guide.md). + > **Note:** Showing only videos with no rights to protect (for example fitness clips)? The [open video](open-video.md) path (coming soon) needs no Player SDK licence. + ## 1. Prepare (no code yet) {#prepare} ⋯
- 30 Sept 2026 · Page created