Update issue
Issues
Update issue
Update the status or suspected cause of an issue.
POST
Update issue
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | None — any valid app_key can call this operation |
Usage
statusvalid values:for_review,reviewed,ignored,resolved.suspected_causevalid values:api.failed_request,network.error,code.exception,code.invalid_object_access,code.invalid_argument,unknown.- Setting
statustoresolvedalso stampsresolved_atandresolved_byon 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 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 to update.
New status.
Available options:
for_review, reviewed, ignored, resolved 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.