Change history
Every change to this page, newest first. Expand an entry to see what changed.
- 1 Oct 2026 · +7 −5 lines
Show changes
⋯ | `creatives:export` | Receive exported creatives | `GET /api/delivery/v1/creatives` and `GET /api/delivery/v1/creatives/{id}` | You, on the **Developers** page | | `webhooks:manage` | Manage webhooks | No endpoint uses this scope yet | You, on the **Developers** page | - | `playback` | Play films (granted by Wandura) | `POST /api/delivery/v1/playback` | Wandura only | + | `playback` | Play films | `POST /api/delivery/v1/playback` | You, on the **Developers** page | - You cannot create a key with the `playback` scope yourself. A leaked playback key would let anyone stream your licensed films, so Wandura issues these keys directly. Ask Wandura for one when you are ready to integrate playback. + You create keys with the `playback` scope yourself, like any other key: on **Developers**, pick **Stream films in an app**. The key gets `metadata:read` and `playback`, so the same server can list your films and request tickets. + > **Warning:** If a playback key leaks, anyone can stream your licensed films. Keep it on your server only, and revoke it immediately if you think it has leaked. Every new playback key, and every rotation of one, also sends an alert to Wandura with your organisation, who created it and its prefix (never the key itself). + Give each key only the scopes it needs. A marketing sync job needs `creatives:export`, not `playback`. ⋯ 1. Open **Developers** and find **Create a key**. 2. Enter a **Label** (up to 80 characters) that says where the key runs, for example `catalog-sync-prod`. - 3. Pick at least one scope. + 3. Pick what the key is for, for example **Stream films in an app** for a playback key, or choose the scopes yourself under **Advanced: choose scopes**. 4. Select **Create key**, then copy the key before you close the notice. ⋯ > **Warning:** The old key stops working the moment you confirm. To rotate without downtime, create a second key with the same scopes, deploy it, and then revoke the old one. - A revoked key cannot be rotated; create a new key instead. Keys with the `playback` scope are rotated by Wandura: the portal marks them **Managed by Wandura** and does not offer **Rotate**. Ask in your team's Wandura Discord channel. To switch without downtime, Wandura creates a new playback key next to the old one, you deploy it, and then Wandura revokes the old key; both keys work in between. + A revoked key cannot be rotated; create a new key instead. Keys with the `playback` scope are rotated the same way, by any **Admin** or **Developer** of your organisation. For a playback key, the zero-downtime switch matters most: create a second playback key, deploy it, then revoke the old one. ## Revoke a key ⋯ Select **Revoke** next to the key and confirm. Anything using the key stops working immediately, and a revoked key cannot be restored. - Developers can revoke the keys created in the portal. Only an organisation **Admin** can revoke a key with the `playback` scope. Use this as an emergency switch if you suspect a playback key has leaked, then ask Wandura for a replacement. + Any **Admin** or **Developer** of your organisation can revoke any of its keys, including keys with the `playback` scope and keys Wandura created for you. If you suspect a playback key has leaked, revoke it immediately: that is your emergency switch. Then create a new playback key for your servers. ## Related ⋯
- 1 Oct 2026 · +1 −1 lines
Show changes
⋯ > **Warning:** The old key stops working the moment you confirm. To rotate without downtime, create a second key with the same scopes, deploy it, and then revoke the old one. - A revoked key cannot be rotated; create a new key instead. Keys with the `playback` scope are rotated by Wandura: the portal marks them **Managed by Wandura** and does not offer **Rotate**. Ask Wandura to rotate one. + A revoked key cannot be rotated; create a new key instead. Keys with the `playback` scope are rotated by Wandura: the portal marks them **Managed by Wandura** and does not offer **Rotate**. Ask in your team's Wandura Discord channel. To switch without downtime, Wandura creates a new playback key next to the old one, you deploy it, and then Wandura revokes the old key; both keys work in between. ## Revoke a key ⋯
- 1 Oct 2026 · +2 −2 lines
Show changes
⋯ | `playback` | Play films (granted by Wandura) | `POST /api/delivery/v1/playback` | Wandura only | - You cannot create a key with the `playback` scope yourself. A leaked playback key would let anyone stream your licensed films, so Wandura issues these keys directly. Ask your Wandura partner contact for one when you are ready to integrate playback. + You cannot create a key with the `playback` scope yourself. A leaked playback key would let anyone stream your licensed films, so Wandura issues these keys directly. Ask Wandura for one when you are ready to integrate playback. Give each key only the scopes it needs. A marketing sync job needs `creatives:export`, not `playback`. ⋯ > **Warning:** The old key stops working the moment you confirm. To rotate without downtime, create a second key with the same scopes, deploy it, and then revoke the old one. - A revoked key cannot be rotated; create a new key instead. Keys with the `playback` scope are rotated by Wandura: the portal marks them **Managed by Wandura** and does not offer **Rotate**. Ask your Wandura partner contact to rotate one. + A revoked key cannot be rotated; create a new key instead. Keys with the `playback` scope are rotated by Wandura: the portal marks them **Managed by Wandura** and does not offer **Rotate**. Ask Wandura to rotate one. ## Revoke a key ⋯
- 30 Sept 2026 · +2 −1 lines
Show changes
⋯ The word `Bearer`, one space, then the key. Keys start with `wnd_live_`, which helps secret scanners find a key that was committed by mistake. - A missing header, a header in another format, or a revoked or unknown key returns `401`. The API does not use cookies, and there is no per-user identity on it: a key acts for its whole organisation. + A missing header, a header in another format, or a revoked or unknown key returns `401`. If Wandura cannot check the key in time, you get `503` with `error_code` `service_unavailable` (creatives: `code` `5031`) and a `Retry-After` header: the key is fine, so retry instead of rotating it. + The API does not use cookies, and there is no per-user identity on it: a key acts for its whole organisation. ## Scopes ⋯
- 29 Sept 2026 · Page created