Skip to main content
POST
Rotate
πŸ”‘ Requires the secrets.update scope.

Authorizations

Authorization
string
header
required

API key from your incident.io dashboard (Settings β†’ API keys)

Path Parameters

id
string
required

The secret's ID

Example:

"01FCNDV6P870EA6S7TK1DSYDG0"

Body

application/json
value
string
required

The secret's new plaintext value. It's stored encrypted and never returned by the API.

Example:

"sk_live_def456"

Response

200 - application/json

OK response.

secret
object
required

A secret is a named credential that workflows can reference, for example an auth token for an outgoing webhook.

Its value can be set and rotated but never read back: the API stores it encrypted and only ever returns masked metadata (the last four characters of the current value). Update the value with the rotate action, which appends a new version and retires the previous one.