Update Credential
Rotate a credential’s secret and/or rename it, in place, keeping the
same id so every referencing config picks up the change with no
re-wiring. Because the vault is write-only, rotation is the only way
to change a stored secret. The kind is immutable: a rotated config
must populate the same block as the credential’s existing kind.
Authentication
Enter your API key with the Bearer prefix, e.g. ‘Bearer sk_…’.
Path parameters
Credential id (prefixed external id, cred_...).
Headers
Request
New human-readable label, unique per workspace.
Kind-specific credential payload, used on WRITES only (create and
rotate). Exactly one block is populated — the one named by the
credential’s kind. The secret fields are write-only: they are
accepted here but are NEVER returned on reads — a read returns the
masked CredentialConfigView instead.
Response
Workspace-scoped credential identifier (prefixed external id).
Human-readable label, unique per workspace among active credentials.
Discriminates the auth flow a credential carries. The matching
config.<kind> block is the one that must be populated.
The masked, read-safe projection of a credential’s config. Returned
on every read (list / get / create / rotate response). Non-secret
fields (token URLs, client ids, issuer, header names) pass through;
each secret is replaced by a *_set boolean. Secret values are never
returned — to change one, rotate it via PATCH /v1/credentials/{id}.
Exactly one block is populated, matching the credential’s kind.