# Support

Contact Wandura in your team's Wandura Discord channel: each partner team works with Wandura in its own channel. This page explains what to contact Wandura about and what to include so that problems are solved quickly.

## Where to get help

- **Wandura**, in your team's Wandura Discord channel. For onboarding, licence and window changes, suspected outages and anything this documentation does not answer.
- **[partner.wandura.ai](https://partner.wandura.ai).** Members with the Admin or Developer role create, rotate and revoke every key on the **Developers** page, playback keys included, without contacting anyone.

## What to contact us about

| Topic | Examples |
|---|---|
| Licences | A film is missing from your catalog, or `not_entitled` appears for a film you expect to stream. |
| Rate limits | Your normal traffic reaches the ceiling. |
| Incidents | A playback key may have leaked. Revoke it first (any Admin or Developer can), then tell us. |
| Outages | Repeated `502` or `503` responses. |

## What to include

Include as much of this as you can:

- The endpoint and HTTP method.
- The time of the request, in UTC.
- The HTTP status, the `error_code` or `code`, and the `reason` if there was one.
- The `episode_id` (or `film_ref` and `episode_no`) and the `viewer_ref` you sent, for playback problems.
- The key prefix shown on the **Developers** page, for example `wnd_live_ab12cd`.

> **Warning:** Never send a full API key or a `play_auth_token` to anyone, including Wandura. The key prefix is enough to identify a key.