History: Rate limits

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

← Rate limits

1. 1 Oct 2026 · +7 −4 lines
   Show changes

   ⋯
     
     - **Per organisation.** Requests are counted for your organisation as a whole, not per key. Creating more keys does not raise your ceiling.
   - - **Per endpoint group.** Playback has its own counter. The catalog and creatives endpoints share a second counter.
   + - **Per endpoint group.** Playback, the catalog and the creatives endpoints each have their own counter, so a runaway creatives sync cannot block your catalog.
     - **Fixed windows.** Counts reset at the start of each window.
     - **Authenticated requests only.** A request with a missing or invalid key is rejected before it is counted, so nobody else can use up your ceiling.
   ⋯
     | Endpoint group | Limit per organisation | Window |
     |---|---|---|
   - | Playback: `POST /api/delivery/v1/playback` | 30,000 requests | 60 seconds |
   - | Catalog and creatives, one shared counter: `GET /api/delivery/v1/catalog`, `GET /api/delivery/v1/creatives`, `GET /api/delivery/v1/creatives/{id}` | 3,000 requests | 60 seconds |
   + | Playback: `POST /api/delivery/v1/playback` | 10,800 requests (about 180 tickets per second) | 60 seconds |
   + | Catalog: `GET /api/delivery/v1/catalog` | 3,000 requests | 60 seconds |
   + | Creatives: `GET /api/delivery/v1/creatives`, `GET /api/delivery/v1/creatives/{id}` (one counter for both) | 3,000 requests | 60 seconds |
     
   - Each window is one clock minute (UTC), so a count starts again at every whole minute. Wandura can raise a limit for your organisation on request: ask in your team's Wandura Discord channel. On a `429`, the `X-RateLimit-Limit` header shows the limit that applies to you.
   + Each window is one clock minute (UTC), so a count starts again at every whole minute. One viewer starting an episode usually costs about three playback tickets (the episode itself plus prefetches), so the playback limit is roughly 60 viewers starting an episode every second.
     
   + Wandura can raise any of these limits for your organisation alone: ask in your team's Wandura Discord channel. A raised limit takes effect within about a minute, with no change on your side. Wandura is also alerted when an organisation reaches its playback limit. On a `429`, the `X-RateLimit-Limit` header shows the limit that applies to you.
   + 
     ## When you reach the ceiling
     
   ⋯

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

   ⋯
     Every ticket request counts toward the playback ceiling, including requests with `"intent": "prefetch"`.
     
   + ## Current limits {#limits}
   + 
   + | Endpoint group | Limit per organisation | Window |
   + |---|---|---|
   + | Playback: `POST /api/delivery/v1/playback` | 30,000 requests | 60 seconds |
   + | Catalog and creatives, one shared counter: `GET /api/delivery/v1/catalog`, `GET /api/delivery/v1/creatives`, `GET /api/delivery/v1/creatives/{id}` | 3,000 requests | 60 seconds |
   + 
   + Each window is one clock minute (UTC), so a count starts again at every whole minute. Wandura can raise a limit for your organisation on request: ask in your team's Wandura Discord channel. On a `429`, the `X-RateLimit-Limit` header shows the limit that applies to you.
   + 
     ## When you reach the ceiling
     
   ⋯
     1. Stop sending requests to that endpoint group until `Retry-After` has passed. Retrying earlier only returns more `429`s.
     2. Look for the cause: a retry loop without backoff, a job that requests tickets for a whole catalog, or catalog calls made on every app launch instead of from a server-side cache.
   - 3. If your normal traffic reaches the ceiling, contact Wandura to have it raised.
   + 3. If your normal traffic reaches the ceiling, ask in your team's Wandura Discord channel to have it raised.
     
     ## Good habits
   ⋯

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

   ⋯
     1. Stop sending requests to that endpoint group until `Retry-After` has passed. Retrying earlier only returns more `429`s.
     2. Look for the cause: a retry loop without backoff, a job that requests tickets for a whole catalog, or catalog calls made on every app launch instead of from a server-side cache.
   - 3. If your normal traffic reaches the ceiling, contact your Wandura partner contact to have it raised.
   + 3. If your normal traffic reaches the ceiling, contact Wandura to have it raised.
     
     ## Good habits
   ⋯

4. 29 Sept 2026 · Page created