Skip to main content
PUT
Update

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
name
string
required

Human-readable name, unique within the organisation amongst unarchived secrets

Example:

"PagerDuty webhook token"

description
string

Optional description of what this secret is for

Example:

"Auth token for the PagerDuty outgoing webhook"

owning_team_ids
string[]

IDs of the teams that own this secret. When omitted, the existing owning teams are left unchanged.

Example:

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.