Skip to main content
PUT
/
v1
/
organizations
/
secrets
/
{secret_name}
Update Secret
curl --request PUT \
  --url https://api.mixpeek.com/v1/organizations/secrets/{secret_name} \
  --header 'Content-Type: application/json' \
  --data '
{
  "secret_value": "<string>"
}
'
{
  "secret_name": "<string>",
  "created": true,
  "updated": true,
  "deleted": true
}

Documentation Index

Fetch the complete documentation index at: https://docs.mixpeek.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Headers

​
Authorization
string

Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.

Example:

"Bearer YOUR_MIXPEEK_API_KEY"

Path Parameters

​
secret_name
string
required

Body

application/json

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:

  • Rotate API keys periodically for security
  • Update expired tokens
  • Change credentials after security incident
  • Switch from test to production keys

Security:

  • Old value is permanently overwritten (no history)
  • New value is encrypted before storage
  • No rollback or undo capability
  • Update is logged for audit trail

Requirements:

  • secret_value: REQUIRED, new plaintext value
  • Secret must already exist (use POST to create)

Permissions: Requires ADMIN permission to update secrets.

​
secret_value
string
required

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).

Minimum string length: 1
Examples:

"YOUR_STRIPE_API_KEY"

"ghp_rotated_token_def456"

"new_api_key_ghi789"

Response

Successful 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:

  • Decrypted secret values are NEVER included
  • Only secret name and operation status returned
  • Actual value only accessible by internal services

Fields:

  • secret_name: Name of the secret that was operated on
  • created: True if secret was created (null for other operations)
  • updated: True if secret was updated (null for other operations)
  • deleted: True if secret was deleted (null for other operations)
​
secret_name
string
required

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.

Examples:

"stripe_api_key"

"github_token"

"openai_api_key"

​
created
boolean | null

True if this secret was created, null otherwise. Only set for POST /secrets operations.

​
updated
boolean | null

True if this secret was updated, null otherwise. Only set for PUT /secrets/{name} operations.

​
deleted
boolean | null

True if this secret was deleted, null otherwise. Only set for DELETE /secrets/{name} operations.