[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-sentry-openapi-2026-05-28-remove-get-api-0-organizations-org-issues-issue-id-endpoint":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"sentry-openapi","Sentry API","sentry","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fgetsentry\u002Fsentry-api-schema\u002Fmain\u002Fopenapi-derefed.json",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KSQRGF99NSSQCR4CVMSH52TD","2026-05-28-remove-get-api-0-organizations-org-issues-issue-id-endpoint","Breaking","Remove GET \u002Fapi\u002F0\u002Forganizations\u002F{org}\u002Fissues\u002F{issue_id}\u002F endpoint spec","The OpenAPI spec entry for **GET `\u002Fapi\u002F0\u002Forganizations\u002F{organization_id_or_slug}\u002Fissues\u002F{issue_id}\u002F`** (\"Retrieve an Issue\") has been removed entirely. Clients relying on this documented endpoint definition (e.g. SDK generators, documentation, or contract tests) will lose the spec. The tail of the diff shows a new, heavily restructured response schema being added in the components section — suggesting the endpoint schema was likely relocated or rewritten, but the old path entry is gone. This is a **Breaking** change for any tooling or codegen pipeline that depends on the previously documented response shape (which included fields like `activity`, `stats`, `userReportCount`, `pluginActions`, etc. that do not appear in the replacement schema).","2026-05-28T17:01:00.073Z"]