API keys
Your plan, this month's calls, and the keys on your Decryptr account.
Every key belongs to one Decryptr account and its plan. Each account may have two active live keys and two active test keys at once, so you can rotate without downtime. A live key starts with dcr_live_ and reads real data; a test key starts with dcr_test_ and reads a fixed sample that never counts against your calls.
What happens when you create a key
- You name it, choose live or test, pick its scopes and accept the API Terms. Give it only the scopes it needs.
- The whole key is shown once. Copy it into your secret store straight away; we keep only a hash and cannot show it again.
- The list shows the first characters and last four of each key, when it was made and when it was last used.
- Revoking a key stops it within 5 seconds, everywhere.
Read Authentication for how to send a key, rotate it and keep it secret.
Authentication
How Decryptr API keys work. Live and test keys, sending the key, scopes, rotation, revocation and keeping keys secret.
Rate limits and quotas
How the Decryptr API counts calls (one per item, weighted by endpoint), the limits per plan, the headers on every response, 429 and Retry-After, and a backoff example.