Create a credential vault
Creates an empty credential vault and returns it with its generated vault_id. Vaults are the unit a session or agent is granted, so create one per trust boundary and add credential references to it afterwards.
Authorizations
A Recursion API key, created in the console under API keys.
Body
Request body for creating a vault: the container that credentials are added to and that sessions are granted. Creating a vault stores no secret material of its own.
Operator-facing label for the vault, shown wherever grants are reviewed. Required.
Optional retry key scoped to the authenticated organization. Reusing it with different creation details is a conflict.
128Free-form caller-owned JSON stored with the vault and returned on reads. Not interpreted by the service; never put secret material here.
Response
A named group of credentials an agent session may be granted. A session references vaults by id; the credential values inside are resolved at execution time and are never returned over the API.
A named group of credentials an agent session may be granted. A session references vaults by id; the credential values inside are resolved at execution time and are never returned over the API.
RFC 3339 timestamp of when this record was created. Server-assigned.
How many credentials this vault currently holds, so a list view need not fetch each vault's credentials.
Operator-facing label for the vault, shown wherever vaults are listed.
Organization that owns this record. Resolved from the API key; never accepted from the caller.
RFC 3339 timestamp of the last change to this record. Server-assigned.
Identifier for this vault (UUID). Server-assigned.
Free-form caller-supplied key/value labels. Stored verbatim and never interpreted by the service.