Skip to main content
POST
Update issue

Restrictions

Usage

  • status valid values: for_review, reviewed, ignored, resolved.
  • suspected_cause valid values: api.failed_request, network.error, code.exception, code.invalid_object_access, code.invalid_argument, unknown.
  • Setting status to resolved also stamps resolved_at and resolved_by on the issue; moving a resolved issue back to another status clears them.
  • 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

Parameters for updating an issue.

issue_id
string
required

Issue ID to update.

status
enum<string>

New status.

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

Suspected cause.

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
required

Empty response body. The server returns data: null on success.