Skip to main content
PUT
Update a secret

Rotation

This is the endpoint to call for credential rotation. The new value takes effect immediately for every function and agent that reads this secret. There’s no staged or per-consumer rollout.
Secrets are looked up by secretName within the account (workspace), the same scoping as Create a secret. A 404 means no secret with this name exists in the account, not that it exists under a different agent.
There is no grace period. As soon as this call succeeds, any function or integration still using the old value will fail until it is updated with the new one.

Authorizations

X-API-KEY
string
header
required

Path Parameters

agentId
string
required
secretName
string
required

Body

application/json
value
string
required

New secret value

Minimum string length: 1
description
string

Description of the secret (unchanged if omitted)

Response

200 - application/json

Updated secret

name
string
required

Display name of the secret

description
string

Description of the secret

createdAt
string

ISO 8601 timestamp of creation

lastUpdated
string

ISO 8601 timestamp of last update

Last modified on September 2, 2026