Skip to main content
Every request carries an API key as a bearer token:
A request without a valid key gets 401 UNAUTHORIZED.

Making a key

Open Reedapt and choose Developers in the account menu. Name the key, pick live or test, and copy it. A key is shown once, when you make it. If you lose it, revoke it and make another.

Live and test keys

Everything else works the same way, so code you write against a test key works unchanged with a live one. A test dub has "test": true and preview_seconds set, and its files are only the watermarked dub.

Keeping keys safe

Use keys only from your server. Never put a key in a web page, a mobile app, or anything people can download. Anyone with the key can spend your minutes.
  • Keep keys in environment variables or a secrets manager, not in your code or repository.
  • Make one key per system, so you can revoke one without touching the others.
  • Revoke a key in Developers if it may have leaked. It stops working within a minute.

Checking a key

GET /usage tells you which plan and kind of key you’re using and how many minutes are left:
Response