[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-sentry-openapi-2026-07-09-remove-segment-names-field-from-replay-responses-add":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},"01KX4EBHPS745XQWMCKR90BZAB","2026-07-09-remove-segment-names-field-from-replay-responses-add","Breaking","Remove segment_names field from Replay responses; add webhookEvents to SentryApp","This diff makes two distinct changes:\n\n- **`segment_names` removed**: The `segment_names` field (`nullable` array of strings) is removed from Replay response schemas across multiple endpoints, and `segment_names` is also removed from the valid enum values for the `field` query parameter. Clients requesting `segment_names` as a field or reading it from replay responses will break.\n- **`webhookEvents` added**: A new `webhookEvents` field (array of strings, e.g. `issue.assigned`, `issue.created`, etc.) is added to SentryApp response schemas and marked as required in the `required` array. This is a new response field that existing integrations can now read, but its addition to `required` means schema validators may flag existing responses that omit it.","2026-07-09T22:00:46.041Z"]