# Before you start

> **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](https://docs.wandura.ai/v1/developers/concepts/open-video) path needs no Player SDK licence.

## 1. Prepare (no code yet)
| 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](https://docs.wandura.ai/partners/roles)) |
| ☐ | 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](https://docs.wandura.ai/v1/developers/player-sdk) |
| ☐ | Your expected peak: plays per minute at launch | Wandura checks your limits against it before go-live |

## 2. Get onboarded
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 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](https://docs.wandura.ai/v1/developers/production/go-live). |

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](https://docs.wandura.ai/v1/developers/guides/testing).

## 3. What you can do before the Player SDK is ready
| 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 |  |

Start with [Quickstart · Part A](https://docs.wandura.ai/v1/developers/quickstart#part-a).

## 4. The Player SDK licence
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](https://docs.wandura.ai/v1/developers/player-sdk).

## 5. What you will build
| Backend | App |
|---|---|
| [Catalog sync job](https://docs.wandura.ai/v1/developers/guides/catalog-sync) | Player SDK integration ([iOS](https://docs.wandura.ai/v1/developers/player-sdk/ios), [Android](https://docs.wandura.ai/v1/developers/player-sdk/android)) |
| [Ticket endpoint with your paywall](https://docs.wandura.ai/v1/developers/guides/playback-flow) | Reading device values, calling your backend |
| [Retries that degrade gently](https://docs.wandura.ai/v1/developers/guides/smooth-playback) | Spinner, not errors, under load |
| [Safe logging and monitoring](https://docs.wandura.ai/v1/developers/production/observability) | [Subtitles](https://docs.wandura.ai/v1/developers/guides/subtitles) |

The whole path, in order: [Integration roadmap](https://docs.wandura.ai/v1/developers/integration-guide).