History: Developer keys

Every change to this page, newest first. Expand an entry to see what changed.

← Developer keys

1. 1 Oct 2026 · +8 −6 lines
   Show changes

   ⋯
     | `creatives:export` | Receive exported creatives | You, in the portal |
     | `webhooks:manage` | Manage webhooks | You, in the portal |
   - | `playback` | Play films (granted by Wandura) | Wandura only |
   + | `playback` | Play films | You, in the portal |
     
   + To stream films in your app, pick **Stream films in an app** when you create the key. It gets `metadata:read` and `playback`.
   + 
   + > **Warning:** If a playback key leaks, anyone can stream your licensed films. Revoke it immediately. The portal shows this warning on the card and again next to the new key. 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).
   + 
     The [API reference](../developers/reference/overview.md) lists which endpoint needs which scope.
     
   ⋯
     - Its scopes.
     - Its status: **Never used**, **Last used** *date and time*, or **Revoked**.
   - - **Managed by Wandura** on playback keys.
     
     ## Rotate a key
   ⋯
     3. Copy the new key from the box that appears. As with a new key, it is shown only once.
     
   - Update your servers right after rotating, because requests made with the old key fail from that moment. You cannot rotate a revoked key or a playback key. For a playback key, ask in your team's Wandura Discord channel: Wandura creates a new playback key next to the old one, you deploy it, and then Wandura revokes the old key, so both work during the switch.
   + Update your servers right after rotating, because requests made with the old key fail from that moment. You cannot rotate a revoked key. Playback keys rotate like any other key; to switch without downtime, create a second playback key, deploy it, then revoke the old one.
     
     ## Revoke a key
   ⋯
     | Key type | Developer | Admin |
     |---|---|---|
   - | Keys you created in the portal | Rotate, revoke | Rotate, revoke |
   - | Playback keys issued by Wandura | Neither | Revoke only |
   + | Any key of your organisation, playback keys included | Rotate, revoke | Rotate, revoke |
     
   - > **Warning:** Revoking a playback key stops film playback in your apps immediately. Only do this in an emergency, then ask for a replacement in your team's Wandura Discord channel.
   + > **Warning:** Revoking a playback key stops film playback in your apps immediately. If you think the key has leaked, revoke it anyway, then create a new playback key for your servers.
     
     ## Next steps
   ⋯

2. 1 Oct 2026 · +2 −2 lines
   Show changes

   ⋯
     3. Copy the new key from the box that appears. As with a new key, it is shown only once.
     
   - Update your servers right after rotating, because requests made with the old key fail from that moment. You cannot rotate a revoked key or a playback key; for a playback key, contact Wandura.
   + Update your servers right after rotating, because requests made with the old key fail from that moment. You cannot rotate a revoked key or a playback key. For a playback key, ask in your team's Wandura Discord channel: Wandura creates a new playback key next to the old one, you deploy it, and then Wandura revokes the old key, so both work during the switch.
     
     ## Revoke a key
   ⋯
     | Playback keys issued by Wandura | Neither | Revoke only |
     
   - > **Warning:** Revoking a playback key stops film playback in your apps immediately. Only do this in an emergency, then contact Wandura for a replacement.
   + > **Warning:** Revoking a playback key stops film playback in your apps immediately. Only do this in an emergency, then ask for a replacement in your team's Wandura Discord channel.
     
     ## Next steps
   ⋯

3. 29 Sept 2026 · Page created