# Reedapt API Keys, Minutes and Limits, Explained

Test keys, live keys, minutes, concurrent dub limits per plan, language refusals and usage reports: what to know before you build on the Reedapt API.

By Owoade Apotierioluwa · Published 2026-11-15 · Reedapt Dubbing

Source: https://reedapt.com/blog/reedapt-api-keys-minutes-and-limits-explained

Before you wire the Reedapt API into a product, it helps to know what limits apply and what they mean for how you build.

## Test keys and live keys

Test keys are free and need a confirmed email address. They dub the first 60 seconds of a file, add a watermark and use no minutes. Live keys come with every paid plan, and their dubs use your plan's minutes. Test keys are video-only, while live keys also work with audio.

## How minutes work

Dubs are counted in minutes of source media, once per language, the same way as in the Reedapt app. Each dub reserves its minutes when it starts. If a dub fails or you cancel it, the minutes are returned. Check what is left with GET /usage.

## How many dubs can run at once

Your plan sets how many dubs can be unfinished at the same time: 3 on Creator, 10 on Professional studio and 25 on Ministry and Platform. Past that, new dubs get a 429 TOO\_MANY\_DUBS\_RUNNING error until some finish. The limit is per account, across all keys and the Reedapt app. If you queue a large back catalogue, start in batches that fit under your limit.

## More than one language

Asking for more than one target language needs a plan with bulk dubbing. If a language is not in your plan, it comes back in the refused list with a reason, and the other languages still start. Call GET /languages to see what your plan covers.

## Safe retries and usage reports

Send an Idempotency-Key on uploads and dubs so a retry after a timeout does not create a second dub. For billing and monitoring, GET /usage/report gives a month of minutes and dubs from the API, per key and per language. Dubs started in the Reedapt app are not included in that report.