[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-sentry-openapi-2026-05-18-replay-response-wrapped-in-top-level-data-envelope":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},"01KRYE8CZ22471EB9M4XKXQDCK","2026-05-18-replay-response-wrapped-in-top-level-data-envelope","Breaking","Replay response wrapped in top-level `data` envelope","The response schema for the Replay detail endpoint has been restructured: all previously top-level fields (`id`, `project_id`, `trace_ids`, `user`, `sdk`, `os`, `browser`, `device`, etc.) are now nested under a required `data` property. Any client code that reads replay fields directly from the response root (e.g. `response.id`, `response.user`) will break — it must now access `response.data.id`, `response.data.user`, etc.","2026-05-18T21:00:48.994Z"]