Skip to main content
POST
Update issue

Restrictions

Usage

  • Only the fields you send are applied; sending a status equal to the current one changes nothing.
  • Setting status to resolved on an unresolved issue stamps resolved_at and resolved_by and clears regression; moving a resolved issue to another status clears resolved_at and resolved_by.
  • resolve_mode is applied only together with status: resolved, and defaults to any when omitted there; send it with status: resolved on an already resolved issue to change only the mode.
  • When the application’s alerting is enabled, resolving an issue sends its recovery alert right away.
  • Setting suspected_cause marks the cause as user-set (suspected_cause.source = user, person_id = caller), and automatic analysis no longer overwrites it.
  • An unknown issue_id returns InvalidParameter (“The specified issue does not exist”).
  • An issue of a private application the caller cannot access returns AccessDenied (“You do not have permission to access this application”).
  • 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 updating an issue.

issue_id
string
required

Issue ID to update. Get issue IDs via POST /rum/issue/list.

status
enum<string>

New status. Setting resolved on an unresolved issue records the resolution time and operator and clears regression; switching away from resolved clears the resolution time and operator. Omit to keep the current status.

Available options:
for_review,
reviewed,
ignored,
resolved
resolve_mode
enum<string>

How the issue reacts when its error recurs after being resolved. Applied only together with status: resolved; defaults to any there when omitted, and is ignored with any other status.

Available options:
any,
version
suspected_cause
enum<string>

New suspected cause; setting it marks the cause source as user, overriding the automatic classification. One of:

Available options:
api.failed_request,
network.error,
code.exception,
code.invalid_object_access,
code.invalid_argument,
unknown

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.