Update an existing secret in organization vault.
Security:
Use Cases:
REQUIRED: Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.
Request to update an existing secret in the organization vault.
Updates the encrypted value of an existing secret. The old value is permanently overwritten with no history or rollback capability.
Use Cases:
Security:
Requirements:
Permissions: Requires ADMIN permission to update secrets.
REQUIRED. New plaintext value for the secret. This will replace the existing encrypted value. The old value is permanently overwritten with no history. The new value will be encrypted at rest using Fernet encryption. Use this to rotate keys, update expired tokens, or change credentials. Format: any string (will be encrypted as-is).
1Successful Response
Response for secret operations (NEVER includes actual decrypted value).
This response is returned after creating, updating, or deleting a secret. For security, the actual secret value is NEVER included in API responses. Only the secret name and operation status are returned.
Security:
Fields:
Name of the secret that was operated on. This is the same name provided in the request. Use this name to reference the secret in api_call stage configuration.
True if this secret was created, null otherwise. Only set for POST /secrets operations.
True if this secret was updated, null otherwise. Only set for PUT /secrets/{name} operations.
True if this secret was deleted, null otherwise. Only set for DELETE /secrets/{name} operations.