
Name and identifiers
Key generation defaults
These apply when akeys.createKey request leaves out prefix or byteLength.
Up to 16 characters. New keys without their own
prefix look like <prefix>_<random>. Rerolling a key with no prefix also uses it.Random bytes in a new key when the request leaves out
byteLength. The API accepts 16 to 255. Rerolled keys always use this value (or 16 if unset), not the original key’s length.Store encrypted keys
When on, you can create recoverable keys and read them back with
decrypt: true. When off, keys.createKey with recoverable: true fails with HTTP 412 “This API does not support key encryption.” There’s no dashboard toggle. Contact support to turn it on. See Recoverable keys.Delete protection
When on, Delete Keyspace in the dashboard and
apis.deleteApi both fail with HTTP 412 err:unkey:application:protected_resource. Switch it on the Delete Protection card and type the keyspace name to confirm. The change shows in the audit log as api.update.Delete keyspace
The Delete Keyspace card in the danger zone deletes the keyspace after you type its name and the confirmation word. Every key in it then verifies asNOT_FOUND. You can’t undo this from the dashboard.