Vault
Encrypt and decrypt your customers' sensitive data with named per-organization keys, and store versioned encrypted objects.
Vault is an encryption service for data you keep about your customers: API tokens, personal data, documents. Each organization gets its own named keys, rotation keeps old data readable, and when the organization (or your environment) has a customer-managed key, Vault keys are protected by it too.
POST /v1/vault/keyscreates a named key for an organization (scopevault:write).GET /lists them with their current version (v1/ vault/ keys? organization=… vault:read) and theirusageover the last 30 days:encrypts,decryptsandlast_used_at. Usage is counted on a best-effort basis and is not a billing record.POST /adds a new version. New data uses it; older ciphertexts still decrypt.v1/ vault/ keys/ {key}/ rotate
Encrypt and decrypt
Section titled “Encrypt and decrypt”POST /v1/vault/encrypt with organization, the key name, the plaintext and an optional context returns a ciphertext, the key ID and its version. POST /v1/vault/decrypt with the organization, the ciphertext and the same context returns the plaintext. Both need vault:use. A ciphertext from another organization, a different context or a revoked customer key fails with vault_decrypt_failed; Vault never falls back to a weaker key.
From the CLI: ohauthcat vault encrypt --organization org_123 --key payroll --plaintext-file secret. and ohauthcat vault decrypt --organization org_123 --ciphertext ….
Objects
Section titled “Objects”For values you would rather not store yourself, Vault keeps versioned encrypted objects:
PUT /stores a new version under an organization’s key.v1/ vault/ objects/ {name} GET /reads the latest version, or one you name.v1/ vault/ objects/ {name} GET /lists versions (metadata only).v1/ vault/ objects/ {name}/ versions DELETE /deletes every version.v1/ vault/ objects/ {name}
Vault routes have their own rate limit, lower than the general API key limit.