Skip to main content
POST
Move monitor folder

Restrictions

Usage

  • You must have access to both the source and destination folders.
  • dest_parent_id is required; send 0 explicitly to move to the root. Moving under the folder itself or a descendant is rejected.
  • Descendant paths are updated in the same transaction.
  • 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
dest_parent_id
integer<uint64>
required

Destination parent folder ID; required even when 0 to move to the root.

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

Empty object.