Skip to main content
POST
Get issue detail

Restrictions

Usage

  • team_id is the owning application’s current team; POST /rum/issue/list and POST /rum/issue/export report the team recorded when the issue was first seen, which differs once the application moves to another team.
  • An unknown or deleted issue_id returns InvalidParameter (“The specified issue does not exist”), not ResourceNotFound.
  • An issue of a private application the caller cannot access returns AccessDenied (“You do not have permission to access this application”).

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
issue_id
string
required

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

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

A RUM error tracking issue.