Skip to main content
POST
Update monitor folder

Restrictions

Usage

  • Send both id and name. This is a replacement of editable fields: omitting note clears it, and omitting team_id resets it to 0.
  • Use the move operation to change the parent folder.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Monitor folder request.

id
integer<uint64>
required

Folder ID.

Required range: x >= 1
name
string
required

Folder name; cannot contain a period, slash, or comma.

Minimum string length: 1
note
string

Free-form note; omitted or empty clears the note on update.

team_id
integer<uint64>

Team ID; 0 means account-wide. Omitted on update resets to 0.

Required range: x >= 0

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

A monitor folder (监控节点). Folders form a tree; parent_path is the comma-separated ancestor ID list, so the caller can rebuild the tree and search it client-side.