> ## Documentation Index > Fetch the complete documentation index at: https://test-8ad8522e-feat-ai-sre.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Get issue detail > Retrieve full details of a single issue by `issue_id`. ## Restrictions | Aspect | Value | | ----------- | ------------------------------------------------------------- | | Rate limits | **1,000 requests/minute**; **50 requests/second** per account | | Permissions | None — any valid `app_key` can call this operation | ## OpenAPI ````yaml /api-reference/rum.openapi.en.json post /rum/issue/info openapi: 3.1.0 info: description: >- Public HTTP API for the Flashduty incident management platform — incidents, notification templates, channels, schedules, monitors, RUM, and platform administration. Every operation is authenticated with an `app_key` query parameter issued from the Flashduty console under Account → APP Keys. Responses follow a uniform envelope: `{ request_id, data }` on success, `{ request_id, error }` on failure. title: Flashduty Open API version: 1.0.0 servers: - description: Flashduty Open API url: https://api.flashcat.cloud security: - AppKeyAuth: [] tags: - description: Manage Real User Monitoring (RUM) applications. name: RUM/Applications - description: Run RUM analytics queries over event data. name: RUM/Data query - description: Query and manage RUM error tracking issues and preset severity rules. name: RUM/Issues - description: >- Query RUM facet fields and their value distributions for building analytics filters. name: RUM/Facets - description: >- Manage and query RUM sourcemap files for browser, Android, and iOS error symbolication. name: RUM/Sourcemaps - description: Retrieve session replay metadata and recorded segments for RUM sessions. name: RUM/Session replay - description: >- Configure and inspect the rules that decide which RUM errors get ingested and stored for an application, including their edit history. name: RUM/Error ingestion rules - description: >- Manage per-application rules that assign a severity to matching front-end errors, plus their evaluation order and change history. name: RUM/Issue preset severity rules - description: Query the RUM resource record and current usage for the account. name: RUM/Resources paths: /rum/issue/info: post: tags: - RUM/Issues summary: Get issue detail description: Retrieve full details of a single issue by `issue_id`. operationId: rum-issue-read-info requestBody: content: application/json: example: issue_id: NHEacQHi2DhXqobr9qPQz9 schema: $ref: '#/components/schemas/RumIssueIDRequest' required: true responses: '200': content: application/json: example: data: age: 5078684 application_id: eWbr4xk3ZRnLabRa6unqwD application_name: Flashduty DEV created_at: 1770883154944 error: message: Script error. type: Error error_count: 752 first_seen: timestamp: 1770883154944 version: 1.0.0 is_crash: false issue_id: NHEacQHi2DhXqobr9qPQz9 last_seen: timestamp: 1775961839090 version: 1.0.0 resolved_at: 0 resolved_by: 0 service: fd-console session_count: 381 severity: Info status: for_review suspected_cause: person_id: 0 reason: >- The error message 'Script error.' typically indicates an unhandled exception in JavaScript. source: auto value: code.exception team_id: 2477033058131 updated_at: 1775961914595 versions: - 1.0.0 request_id: 01HK8XQE3Z7JM2NTFQ5YJ8P9R4 schema: allOf: - $ref: '#/components/schemas/SuccessEnvelope' - properties: data: $ref: '#/components/schemas/RumIssueItem' type: object description: Success '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '429': $ref: '#/components/responses/TooManyRequests' '500': $ref: '#/components/responses/ServerError' components: schemas: RumIssueIDRequest: properties: issue_id: description: Issue ID. Get issue IDs via `POST /rum/issue/list`. type: string required: - issue_id type: object SuccessEnvelope: description: >- 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`. properties: data: description: Endpoint-specific payload. See each operation's 200 response schema. request_id: description: >- Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues. example: 01HK8XQE3Z7JM2NTFQ5YJ8P9R4 type: string required: - request_id - data type: object RumIssueItem: description: A RUM error tracking issue. properties: age: description: Time span between the first and most recent occurrence, in seconds. format: int64 type: integer application_id: description: ID of the RUM application this issue belongs to. type: string application_name: description: >- Name of the owning application, resolved by `application_id` at query time (reflects the application's current name). type: string created_at: description: >- Issue creation time (client time of the first error event), Unix timestamp in milliseconds. format: int64 type: integer error: description: >- Representative error of this issue, taken from the error event that created it. properties: message: description: Normalized error message, truncated to at most 512 characters. type: string type: description: >- Error type, from the error event's `error_type` field as reported by the SDK. type: string type: object error_count: description: Total error occurrences. format: int64 type: integer first_seen: description: >- Information about the issue's first occurrence (time and application version). properties: timestamp: description: >- Client time of the first error event, Unix timestamp in milliseconds. format: int64 type: integer version: description: >- Application version at first occurrence; empty string when the event carries no version. type: string type: object is_crash: description: Whether the error caused an app crash. type: boolean issue_id: description: Unique issue ID. type: string last_seen: description: >- Information about the issue's most recent occurrence (time and application version). properties: timestamp: description: >- Client time of the most recent error event, Unix timestamp in milliseconds. format: int64 type: integer version: description: >- Application version at the most recent occurrence; empty string when the event carries no version. type: string type: object regression: description: >- Regression metadata. Present only when a previously resolved issue re-occurred. properties: regressed_at: description: >- Time the regression was detected, Unix timestamp in milliseconds. format: int64 type: integer regressed_at_version: description: Application version in which the regression was observed. type: string resolved_at: description: >- When the issue was resolved before this regression, as a Unix timestamp in milliseconds. format: int64 type: integer type: object resolved_at: description: >- Time the issue was marked resolved, Unix timestamp in milliseconds; 0 while unresolved. format: int64 type: integer resolved_by: description: >- Person ID of the user who marked the issue resolved; 0 while unresolved. format: int64 type: integer service: description: >- Name of the service that produced this issue, taken from the error event's `service` field. type: string session_count: description: Affected user sessions. format: int64 type: integer severity: description: >- Issue severity: `Critical`, `Warning`, or `Info`. Empty string on legacy issues created before severity existed. enum: - Critical - Warning - Info type: string status: description: >- Triage status of the issue; soft-deleted (`deleted`) issues are never returned. | Value | Meaning | |---|---| | `for_review` | Pending triage | | `reviewed` | Reviewed | | `ignored` | Ignored | | `resolved` | Resolved | enum: - for_review - reviewed - ignored - resolved type: string suspected_cause: description: >- Suspected root cause analysis, determined automatically (rules or AI) or set manually by a user. properties: person_id: description: >- Person ID of the user who manually set the cause; 0 when `source` is `auto`. format: int64 type: integer reason: description: >- Explanation for the cause determination, generated only by AI analysis; empty string when AI is disabled or analysis has not run. type: string source: description: >- Origin of the cause: `auto` for system-determined, `user` for manually set. enum: - auto - user type: string value: description: >- Suspected cause category. One of: | Value | Meaning | |---|---| | `api.failed_request` | API request failure (e.g. HTTP 4xx/5xx responses) | | `network.error` | Network connectivity error (offline, aborted requests, etc.) | | `code.exception` | Code exception (Syntax/Reference/Range and similar runtime errors) | | `code.invalid_object_access` | Invalid object access (e.g. reading a property of `undefined`/`null`) | | `code.invalid_argument` | Invalid argument passed to a function | | `unknown` | Cause could not be determined | enum: - api.failed_request - network.error - code.exception - code.invalid_object_access - code.invalid_argument - unknown type: string type: object team_id: description: >- ID of the team owning this issue, copied from the owning application's `team_id` at issue creation. format: int64 type: integer updated_at: description: Time the issue was last updated, Unix timestamp in milliseconds. format: int64 type: integer versions: description: >- Deduplicated list of application versions in which this issue has occurred; may contain an empty string for events without version info. items: type: string type: array type: object ErrorResponse: description: Response envelope for errors. `error` is required; `data` is absent. properties: error: $ref: '#/components/schemas/DutyError' request_id: description: >- Unique trace ID of this request; include it when reporting issues so logs can be located. example: 01HK8XQE3Z7JM2NTFQ5YJ8P9R4 type: string required: - request_id - error type: object DutyError: description: >- Error payload inside the response envelope. Present only on non-2xx responses. properties: code: $ref: '#/components/schemas/ErrorCode' message: description: >- Human-readable error message, localized by the caller's Accept-Language. May contain field names, IDs, or other context from the failing request. example: The specified parameter template_id is not valid. type: string required: - code - message type: object ErrorCode: description: >- Flashduty error code enum. Every failed API response sets `error.code` to one of these stable wire strings. HTTP status is informational — the authoritative signal is the enum value. | Code | HTTP | Meaning | |---|---|---| | `OK` | 200 | Reserved — not returned on real errors. | | `InvalidParameter` | 400 | A required parameter is missing or failed validation. | | `BadRequest` | 400 | Generic 400 used when no more specific code fits. | | `InvalidContentType` | 400 | The `Content-Type` header is not `application/json`. | | `ResourceNotFound` | 400 | The referenced resource does not exist. Note: returned as HTTP 400, not 404 (historical choice). | | `NoLicense` | 400 | The feature is license-gated and no active license was found. | | `ReferenceExist` | 400 | Deletion blocked — other entities still reference this resource. | | `Unauthorized` | 401 | `app_key` is missing, invalid, or expired. | | `BalanceNotEnough` | 402 | Billing-gated operation with insufficient account balance. | | `AccessDenied` | 403 | Authenticated but lacking the permission required for this operation. | | `RouteNotFound` | 404 | The request URL path is not a known route. | | `MethodNotAllowed` | 405 | The HTTP method is not allowed on this otherwise-known path. | | `UndonedOrderExist` | 409 | An outstanding billing order blocks this new one. Wait and retry. | | `RequestLocked` | 423 | Operation temporarily locked due to repeated failures. | | `EntityTooLarge` | 413 | Request body exceeds the configured max size. | | `RequestTooFrequently` | 429 | Rate limit hit — API-global, per-account, or per-integration. | | `RequestVerifyRequired` | 428 | Second-factor verification required but not supplied. | | `DangerousOperation` | 428 | High-risk operation requires MFA verification. | | `InternalError` | 500 | Unhandled server-side error. Include `request_id` in the bug report. | | `ServiceUnavailable` | 503 | A backend dependency is unavailable. Try again later. | enum: - OK - InvalidParameter - BadRequest - InvalidContentType - ResourceNotFound - NoLicense - ReferenceExist - Unauthorized - BalanceNotEnough - AccessDenied - RouteNotFound - MethodNotAllowed - UndonedOrderExist - RequestLocked - EntityTooLarge - RequestTooFrequently - RequestVerifyRequired - DangerousOperation - InternalError - ServiceUnavailable example: InvalidParameter type: string x-enumDescriptions: AccessDenied: Authenticated but lacking the permission required for this operation. BadRequest: Generic 400 used when no more specific code fits. BalanceNotEnough: Billing-gated operation with insufficient account balance. DangerousOperation: High-risk operation requires MFA verification. EntityTooLarge: Request body exceeds the configured max size. InternalError: Unhandled server-side error. Include `request_id` in the bug report. InvalidContentType: The `Content-Type` header is not `application/json`. InvalidParameter: A required parameter is missing or failed validation. MethodNotAllowed: The HTTP method is not allowed on this otherwise-known path. NoLicense: The feature is license-gated and no active license was found. OK: Reserved — not returned on real errors. ReferenceExist: Deletion blocked — other entities still reference this resource. RequestLocked: Operation temporarily locked due to repeated failures. RequestTooFrequently: Rate limit hit — API-global, per-account, or per-integration. RequestVerifyRequired: Second-factor verification required but not supplied. ResourceNotFound: >- The referenced resource does not exist. Note: returned as HTTP 400, not 404 (historical choice). RouteNotFound: The request URL path is not a known route. ServiceUnavailable: A backend dependency is unavailable. Try again later. Unauthorized: '`app_key` is missing, invalid, or expired.' UndonedOrderExist: An outstanding billing order blocks this new one. Wait and retry. responses: BadRequest: content: application/json: examples: missingParameter: value: error: code: InvalidParameter message: The specified parameter is not valid. request_id: 01HK8XQE3Z7JM2NTFQ5YJ8P9R4 schema: $ref: '#/components/schemas/ErrorResponse' description: Invalid request — usually a missing or malformed parameter. Unauthorized: content: application/json: examples: missingAppKey: value: error: code: Unauthorized message: You are unauthorized. request_id: 01HK8XQE3Z7JM2NTFQ5YJ8P9R4 schema: $ref: '#/components/schemas/ErrorResponse' description: Missing or invalid app_key. TooManyRequests: content: application/json: examples: rateLimited: value: error: code: RequestTooFrequently message: Request too frequently. request_id: 01HK8XQE3Z7JM2NTFQ5YJ8P9R4 schema: $ref: '#/components/schemas/ErrorResponse' description: >- Rate limit hit. Either the global API limit, a per-account limit, or a per-integration limit. ServerError: content: application/json: examples: internal: value: error: code: InternalError message: >- We encountered an internal error, and it has been reported. Please try again later. request_id: 01HK8XQE3Z7JM2NTFQ5YJ8P9R4 schema: $ref: '#/components/schemas/ErrorResponse' description: Unexpected server-side error. Include the request_id when reporting. securitySchemes: AppKeyAuth: description: >- 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. in: query name: app_key type: apiKey ````