Create a test key and your production keys, deactivate them in one click, track their use. The full key is shown only once; only its SHA-256 fingerprint is stored, and each key has its own per-minute and per-day limits.
For your technical teams: keys that are easy to rotate. For your managers: visible usage and access you can cut off in one click.
32 random characters, shown only once, then stored as an irreversible SHA-256 fingerprint.
Recognise each key by its prefix (cbrd_live_ or cbrd_test_ followed by two characters). The rest is never stored in clear.
Deactivate a key without deleting it: it is refused from the next request. Reactivate it whenever you want.
Each production key gets your plan's per-minute and per-day limits when it is created. The test key is limited to 20 requests per minute and 100 per day.
Number of requests and date of last use for each key. Batches launched through the API appear in your history with the key prefix.
Create the new key, switch your systems over, then deactivate the old one. Your integrations keep working during the transition.
A simple life cycle for each of your keys.
Name it, choose test or production. The full key is shown only once.
Copy it in one click and store it in an environment variable of your application.
Each request is authenticated by the key and counted within its limits.
See the number of requests and the last use; deactivate or replace a key at any time.