Skip to main content
POST
Reorder comment types

Restrictions

Usage

  • Full-set reorder — comment_type_ids must contain every comment type of the account, each exactly once, in the desired order.
  • Positions are reassigned starting from 1: the first ID in the array becomes position 1.
  • This permission is admin-only by default; custom roles must be granted it explicitly.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Parameters for reordering comment types.

comment_type_ids
string[]
required

IDs of every comment type of the account in the desired order (24-character hex ObjectIDs).

Minimum array length: 1
Pattern: ^[0-9a-fA-F]{24}$

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

No payload. Depending on the operation, data is {} or omitted from the envelope; rely only on the HTTP 200 status and the absence of error.