[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$faS6TXirpV_2hCCXt0Prh7GAvvFV4Y3w_KiovXkqZ3T8":3,"$fudzufCbwPdAsmkkhWDxFRLRSh89sdtA6UqSXNjQvcow":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"sentry-openapi","Sentry API","sentry","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fgetsentry\u002Fsentry-api-schema\u002Fmain\u002Fopenapi-derefed.json",{"id":13,"contentHash":14,"fetchedAt":15},"01KX40KTMSM32EWK2JWCNGWVJC","974b203a22e3e04d3abfb159ff65d801933c9db035214350b4187e683eaa3857","2026-07-09T18:00:36.526Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KX4EB2VA5JQXMF3KW5RXVSQR","7c6c97f994f285e5947e7b3697a3c5217b7fd2ce0cfe636c3328a2094f759d48","2026-07-09T22:00:30.154Z",null,{"alerts":22},[23,30,37,45,52,59,66,73,80,87,94,101,108,115,122,129,136,143,150,157,164,171,178,185,192,199,206,213,220,227,234,241,248,255,262,269,277,284,291,298,305,312,319,326,333,340,347,354,361,368],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KX4EBHPS745XQWMCKR90BZAB","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","2026-07-09-remove-segment-names-field-from-replay-responses-add",{"id":31,"severity":32,"title":33,"summary":34,"contentHash":14,"detectedAt":35,"slug":36},"01KX40M1C2Z73AN5TVPMP0HCQ1","Additive","Add segment_names field to session response","A new optional response field `segment_names` (array of strings, nullable) has been added to session objects across multiple API responses. This field can now be marshaled in output by including it in field query parameters, and clients can optionally consume it without breaking existing integrations.","2026-07-09T18:00:44.162Z","2026-07-09-add-segment-names-field-to-session-response",{"id":38,"severity":39,"title":40,"summary":41,"contentHash":42,"detectedAt":43,"slug":44},"01KWZ2PJSFT8AHFRFM7ZQN4CH5","Informational","Remove alerts aspect info text from PagerDuty and Slack integration examples","The `aspects.alerts` array (containing informational `type: info` text blurbs) has been removed from the PagerDuty and Slack integration metadata examples in the OpenAPI spec, replaced with an empty `aspects: {}` object. These are example\u002Fdocumentation values in the spec rather than a schema change, so existing integrations are unlikely to break — but clients that parse or display `aspects.alerts` from the API response may now receive an empty object instead of the info alert array.","6e18541624cc1f0fccfede5971f21f153730938f2de4859cb259952d8282c8cc","2026-07-07T20:00:52.527Z","2026-07-07-remove-alerts-aspect-info-text-from-pagerduty-and-slack",{"id":46,"severity":32,"title":47,"summary":48,"contentHash":49,"detectedAt":50,"slug":51},"01KWYMYX1ET46H01GB7094V86Z","Add outOfDate field to integration responses","A new optional boolean field `outOfDate` has been added to integration response schemas across multiple endpoints. The field is nullable and included in example responses with a `false` value, allowing API clients to determine if an integration configuration is outdated. This is a purely additive change that does not affect existing integrations.","cc1c300c9b5816ec46cb3c819ad55c5407d7889e99f913e22485131360a0715f","2026-07-07T16:00:45.102Z","2026-07-07-add-outofdate-field-to-integration-responses",{"id":53,"severity":32,"title":54,"summary":55,"contentHash":56,"detectedAt":57,"slug":58},"01KWYHGVECGSM6PR2FZ085DTQ6","Add optional download parameter to get attachment endpoint","The `GET \u002Fapi\u002F0\u002Fprojects\u002F{organization_id_or_slug}\u002F{project_id_or_slug}\u002Fevents\u002F{event_id}\u002Fattachments\u002F{attachment_id}\u002F` endpoint now supports an optional `download` query parameter that triggers binary file download instead of returning JSON metadata. This is purely additive—existing callers without the parameter continue to work unchanged.","c0f28e453ed539825e5d49ae7e9bd1019da5cae525fb96e6a7fe429b1e267ad4","2026-07-07T15:00:38.988Z","2026-07-07-add-optional-download-parameter-to-get-attachment-endpoint",{"id":60,"severity":39,"title":61,"summary":62,"contentHash":63,"detectedAt":64,"slug":65},"01KWWTJZ3V6D4NY91KR18MEYKQ","Remove availability disclaimer from alert trigger descriptions","The phrase \"Note: `seer_activity_trigger` may not be available to all organizations.\" was removed from three identical alert trigger description fields in the OpenAPI schema. This is a documentation clarification that does not change the actual API behavior, endpoints, or response\u002Frequest shapes.","f723bb405ab39498eb18df5cd31246b6c9a1d26f08b32d544edb2eea2b4a9b6f","2026-07-06T23:00:36.603Z","2026-07-06-remove-availability-disclaimer-from-alert-trigger",{"id":67,"severity":32,"title":68,"summary":69,"contentHash":70,"detectedAt":71,"slug":72},"01KWJH08KADW21R1VKEPHZMYBA","Add enum constraints to level field in event responses","The `level` field in multiple event response schemas now includes explicit enum constraints listing valid values: `\"sample\"`, `\"debug\"`, `\"info\"`, `\"warning\"`, `\"error\"`, `\"fatal\"`, and `\"unknown\"`. This change documents previously implicit constraints without removing any existing values, making the API contract more explicit and enabling better client validation.","a1ceefc2e35e0313838f1bd6994db87248834b01c54fd5ab3f9e71f46f79e210","2026-07-02T23:00:42.218Z","2026-07-02-add-enum-constraints-to-level-field-in-event-responses",{"id":74,"severity":32,"title":75,"summary":76,"contentHash":77,"detectedAt":78,"slug":79},"01KWJDJGDQ0DJ5VC8S62WT797Y","Expand occurrence object schema with detailed field definitions","The `occurrence` field in multiple event response schemas is now fully documented with explicit property types, replacing an empty object definition. Previously defined as `{}` (any type), it now specifies a detailed structure including `id`, `projectId`, `eventId`, `fingerprint`, `issueTitle`, `subtitle`, `resourceId`, `evidenceData`, `evidenceDisplay`, `type`, `detectionTime`, `level`, `culprit`, `assignee`, and `priority` fields. This is a documentation enhancement that does not break existing clients since the field was already present; it simply makes the structure more explicitly defined in the OpenAPI schema.","1a24596e721d1a98f4d2c3a6dc9947972a82feebf322fb3d1ba5f93a64c57b88","2026-07-02T22:00:45.751Z","2026-07-02-expand-occurrence-object-schema-with-detailed-field",{"id":81,"severity":32,"title":82,"summary":83,"contentHash":84,"detectedAt":85,"slug":86},"01KWFM9TVKY8SAFRJ315PE8DCW","Add canvas_theme field to image objects, rename content_hash to key","The Sentry API adds an optional `canvas_theme` field (enum: \"light\", \"dark\", null) to multiple image object schemas across replay and network monitoring endpoints. Additionally, the `content_hash` field is renamed to `key` in `head_image` and `base_image` objects. These are additive changes to response schemas that enable clients to specify or receive canvas theme information for replay images.","17b28aa7e7635101cb33ab9cd1f60bfc16cb15b7d8d9e02060dee57a206c70a4","2026-07-01T20:00:38.259Z","2026-07-01-add-canvas-theme-field-to-image-objects-rename-content-hash",{"id":88,"severity":32,"title":89,"summary":90,"contentHash":91,"detectedAt":92,"slug":93},"01KWDFMEWKK4AJTBM41NXYQNVP","Document groupingConfig object schema in event responses","The `groupingConfig` field in event response schemas is now documented with explicit type information and required properties (`id` and `enhancements`). Previously it was defined as an empty object schema. This change clarifies the structure of event responses and helps clients understand what data they can expect, with no breaking changes to existing integrations.","74a916b2b93369c65c66d9848a121649a07b46b376ae8bacd377e8f1268a8cf2","2026-07-01T00:00:34.707Z","2026-07-01-document-groupingconfig-object-schema-in-event-responses",{"id":95,"severity":32,"title":96,"summary":97,"contentHash":98,"detectedAt":99,"slug":100},"01KWD1XDR03PVMTYGTR6EXA767","Add integration issue config and linking endpoints","Added three new endpoints for managing integration-linked issues: a GET endpoint to retrieve issue configuration forms for creating or linking external issues, a POST endpoint to create or link external issues, and a DELETE endpoint to unlink external issues. These are purely additive and fully backward-compatible; existing integrations continue to work unchanged.","4848351480e7496a66f33686f8aa78aa8e2449ced0a358c8dd492ba1e88a0c98","2026-06-30T20:00:48.384Z","2026-06-30-add-integration-issue-config-and-linking-endpoints",{"id":102,"severity":32,"title":103,"summary":104,"contentHash":105,"detectedAt":106,"slug":107},"01KWCV1M75K4K7PXZ6ERMPW32P","Add seer_activity_trigger option to alert conditions","The Sentry API now documents a new `seer_activity_trigger` condition type for alert triggers, which accepts comparison values for RCA (root cause analysis) workflow events (`rca_started`, `rca_completed`, etc.). This is an additive change that extends the available trigger conditions; a note clarifies the feature may not be available to all organizations yet.","090836f25c7e22664604052186f1b2c196854a1c5e4184effbc8124fd2cf3d69","2026-06-30T18:00:46.053Z","2026-06-30-add-seer-activity-trigger-option-to-alert-conditions",{"id":109,"severity":32,"title":110,"summary":111,"contentHash":112,"detectedAt":113,"slug":114},"01KWCQKJR8TY79QR61S4KYZFG9","Add enum constraints to issue and chart fields","The API schema adds `enum` constraints to response fields `status`, `substatus`, `priority`, `confidence`, and `legendType` across multiple endpoints and schemas. These fields were previously typed as plain strings but are now restricted to specific valid values. Since these changes add documentation of already-constrained values in responses (not modifying request contracts or narrowing accepted inputs), existing integrations reading responses with these values will continue to work.","c3cee1411d57271ec34ce52e40e49b460f02ceb73f025b713605dc7ce85ccad7","2026-06-30T17:00:40.072Z","2026-06-30-add-enum-constraints-to-issue-and-chart-fields",{"id":116,"severity":32,"title":117,"summary":118,"contentHash":119,"detectedAt":120,"slug":121},"01KWC307KA9D6H2WBF51PRX0KP","Add relayDsnEndpoint field to organization response","The Sentry API adds a new optional nullable `relayDsnEndpoint` field to organization response schemas, allowing clients to retrieve the Relay base URL used for displaying Client Key DSNs. This is a purely additive change that does not affect existing integrations.","3738d29fc98d47ad5dc5d41d5094393054341583497626c563730a94935c2634","2026-06-30T11:00:34.538Z","2026-06-30-add-relaydsnendpoint-field-to-organization-response",{"id":123,"severity":39,"title":124,"summary":125,"contentHash":126,"detectedAt":127,"slug":128},"01KWB0NJRCESJPQD4JJWA54HYD","Update example measurements in transaction schema","The OpenAPI schema example for the `measurements` field in transaction objects has been expanded to include concrete measurement examples (`measurements.frames_slow_rate` and `measurements.frames_frozen_rate`). This is a documentation-only change that illustrates additional measurement types supported by the API without altering any actual endpoints or breaking existing integrations.","b81a7a57b28d36453e109e3fc77559184a183fe89fef72222f7c9b5719f35466","2026-06-30T01:00:33.932Z","2026-06-30-update-example-measurements-in-transaction-schema",{"id":130,"severity":32,"title":131,"summary":132,"contentHash":133,"detectedAt":134,"slug":135},"01KW9TY4NVJ14A41CZWDS9CZ7K","Add listOrganizationReleases endpoint and release schemas","A new endpoint `GET \u002Fapi\u002F0\u002Forganizations\u002F{organization_id_or_slug}\u002Freleases\u002F` has been added to list organization releases with filtering by project, environment, and query parameters. Several new schema definitions have also been added to support this endpoint, including `ReleaseFile`, `ReleaseFileUpload`, `ReleaseHeadCommitSerializerDeprecated`, and `ReleaseSerializerWithProjects`. These are purely additive changes that do not affect existing integrations.","9a6546b5d44271b4cbb60ed60d77139da7a11a1fdb4486357bb001aae1461cba","2026-06-29T14:01:08.539Z","2026-06-29-add-listorganizationreleases-endpoint-and-release-schemas",{"id":137,"severity":32,"title":138,"summary":139,"contentHash":140,"detectedAt":141,"slug":142},"01KW2AJQ802XPTAJBJ8WD2DJAN","Add isConvention field to attribute context metadata","The Sentry API now includes a new optional `isConvention` boolean field in the `context` object for attributes, along with updated documentation clarifying how attribute metadata is sourced from Sentry conventions by name and type. This is a backward-compatible addition that provides clients with information about whether an attribute matches a known convention.","0fac48504a644717397ab70595c9c9733db999e372376db0adf006298a7d6dcc","2026-06-26T16:00:36.096Z","2026-06-26-add-isconvention-field-to-attribute-context-metadata",{"id":144,"severity":32,"title":145,"summary":146,"contentHash":147,"detectedAt":148,"slug":149},"01KW2751VRNBF2BWW7QKW89488","Add optional webhookHeaders field to Sentry integrations","Added a new optional `webhookHeaders` field (array of strings) to custom integration response schemas and request schemas across multiple integration endpoints. This allows integration webhooks to include custom headers without breaking existing integrations that don't use this field.","0c84deacd472359c2666378aaf332feaf3a7f9606229c94e15e7b3f5662fa311","2026-06-26T15:00:42.488Z","2026-06-26-add-optional-webhookheaders-field-to-sentry-integrations",{"id":151,"severity":39,"title":152,"summary":153,"contentHash":154,"detectedAt":155,"slug":156},"01KVXCN4QM6XJV6EZ68VQ7X0P8","Clarify data-browsing-attribute-context feature gate documentation","The `context` field description in the API schema has been updated to clarify when the `data-browsing-attribute-context` feature gate applies. The change restructures the documentation text but does not alter the actual API behavior, endpoints, or response structure — it is purely a documentation improvement for clarity.","b96ee040865ba711aab8e29839c371a64f79f61277f8d8a50ad928c901173c13","2026-06-24T18:00:40.436Z","2026-06-24-clarify-data-browsing-attribute-context-feature-gate",{"id":158,"severity":25,"title":159,"summary":160,"contentHash":161,"detectedAt":162,"slug":163},"01KVVBE2642PQCGQ1GKPSCM7G8","Remove plugin-related fields from issue and project API responses","The fields **`pluginActions`**, **`pluginIssues`**, **`pluginContexts`**, and **`plugins`** have been removed from multiple response schemas. These were previously required\u002Fdocumented fields on issue detail and project detail responses — clients that read or depend on any of these fields will encounter missing data. The `pluginActions` and `pluginIssues` enum values have also been removed from the `expand` query parameter on issue endpoints.","5be41cc323c2af172a7facf4eb3949b716ac3417da1f98c64eafa3de02e0c33e","2026-06-23T23:00:51.012Z","2026-06-23-remove-plugin-related-fields-from-issue-and-project-api",{"id":165,"severity":32,"title":166,"summary":167,"contentHash":168,"detectedAt":169,"slug":170},"01KVTPTPRD39YM15VN1EP0V905","Add mobile_app_vital field to transaction objects","A new optional `mobile_app_vital` field has been added to transaction response objects in the Sentry API. This field mirrors the existing `browser_web_vital` structure, allowing clients to capture mobile application performance metrics like cold start, warm start, time to interactive, and time to fully drawable. Existing integrations are unaffected as this is a purely additive change.","75191d8a28f41a6c73eae0d3c949e39b7c6ad014684a6217217d96068acbfed3","2026-06-23T17:00:45.197Z","2026-06-23-add-mobile-app-vital-field-to-transaction-objects",{"id":172,"severity":39,"title":173,"summary":174,"contentHash":175,"detectedAt":176,"slug":177},"01KVRNK2SV1VPP6429M3Q4GWP6","Clarify snapshot image categorization behavior in docs","The `getOrganizationPreprodArtifactSnapshot` endpoint description was updated to clarify how images are organized based on `comparison_type`. The documentation now explicitly states that when a comparison exists (`comparison_type` is `diff`), the top-level `images` array is empty and images appear in categorized lists (`changed`, `added`, `removed`, etc.), while for `solo` and `waiting_for_base` snapshots the categorized lists are empty and only the `images` array is populated. The example response was also updated to reflect this with an empty `images` array.","d35a03ee4b9d53c744028f20756b1670cd46f5fe23b02c381263556f086f2ded","2026-06-22T22:00:37.947Z","2026-06-22-clarify-snapshot-image-categorization-behavior-in-docs",{"id":179,"severity":25,"title":180,"summary":181,"contentHash":182,"detectedAt":183,"slug":184},"01KVRB9QM6PRGKXR286J3KXYS8","Remove required fields 'brief' and 'isDeprecated' from context object","The `required` constraint on the `context` response object has been removed, meaning `brief` and `isDeprecated` are no longer guaranteed to be present. Clients that assumed these fields were always present (e.g. accessing them without null-checks) may encounter runtime errors. The description update clarifies that custom attributes now receive an empty `context`, which explains why these fields can no longer be required.","f9355f36b19852e5adf7cfcd8ff59999cf6071f7ca0354a1c4113e574a003347","2026-06-22T19:00:45.830Z","2026-06-22-remove-required-fields-brief-and-isdeprecated-from-context",{"id":186,"severity":25,"title":187,"summary":188,"contentHash":189,"detectedAt":190,"slug":191},"01KVFEB2SHJKD6TW8VZPPV5N77","project query param type changed from integer to string","The `project` query parameter type was changed from `integer` to `string`, and its description updated to accept either an ID or a slug. Clients that validate or serialize this parameter as a strictly numeric\u002Finteger type may break, though passing an integer as a string is typically backwards-compatible in practice. The broader concern is any strict-typed SDK or client that enforces the `integer` schema.","580e5f7ad7f7f69c011f30def2c3b77e929314d9b33bb348fd3d7bc2729b188b","2026-06-19T08:00:45.873Z","2026-06-19-project-query-param-type-changed-from-integer-to-string",{"id":193,"severity":32,"title":194,"summary":195,"contentHash":196,"detectedAt":197,"slug":198},"01KVEFDZ9ARGJ602FC2B5WX94Z","Add seerMatchDistance field to group hash response","The API now includes a new **seerMatchDistance** field (nullable double) in group hash responses. This field indicates the match distance score when hashes are merged by Seer. The field is required in the schema but nullable in value, allowing clients to handle cases where a match distance is not available.","a99a29f84a269426066e77762b0cf53182c64b068b9e82c71202e847917e6334","2026-06-18T23:00:34.730Z","2026-06-18-add-seermatchdistance-field-to-group-hash-response",{"id":200,"severity":32,"title":201,"summary":202,"contentHash":203,"detectedAt":204,"slug":205},"01KVDQDGHACP6395QYVNP1B9NE","Add optional context field to attribute metadata endpoints","A new optional `context` field has been added to attribute response objects in two endpoints, providing additional metadata about Sentry conventions when the `expand=context` parameter is passed and the `data-browsing-attribute-context` feature is enabled. This field includes `brief`, `isDeprecated`, `details`, `examples`, and `replacementAttribute` properties, none of which break existing integrations since the field is optional and only populated under specific conditions.","61b346c8f685f041a1d260c5213bf9ba737cde0c7ceb971f0e7019e8e3c87dac","2026-06-18T16:00:53.802Z","2026-06-18-add-optional-context-field-to-attribute-metadata-endpoints",{"id":207,"severity":32,"title":208,"summary":209,"contentHash":210,"detectedAt":211,"slug":212},"01KVDGHVXEMG7B3JX7RQA6RSGE","New required field `browser_web_vital` added to span response objects","A new `browser_web_vital` field (type `object`) has been added to span response objects in two schema locations. It is listed as **required** in the response schema, meaning the API will always return it — this is additive for consumers reading the field, but clients doing strict schema validation against the old spec (which lacked this field) may need to update their models. The field contains browser Core Web Vitals metrics such as `browser.web_vital.lcp.value`, `browser.web_vital.cls.value`, `browser.web_vital.inp.value`, `browser.web_vital.ttfb.value`, and `browser.web_vital.fcp.value`.","20a633f9b258c05cc5fb182b4d2281e2acbeeb285c4085c519cb893e82c80f59","2026-06-18T14:00:56.494Z","2026-06-18-new-required-field-browser-web-vital-added-to-span-response",{"id":214,"severity":39,"title":215,"summary":216,"contentHash":217,"detectedAt":218,"slug":219},"01KVAQ8RGF84KTK5QFJX6WZPYT","operationId refactoring: camelCase IDs and added summary fields","All `operationId` values have been converted to camelCase (e.g. `listOrganizations`, `getOrganization`) and matching `summary` fields have been added to preserve the original human-readable titles. This is a purely internal documentation reorganization — `operationId` is not a versioned API contract and does not affect request\u002Fresponse behavior.","c09bd8eb0dfd222a33bdf06225e279b2aee7b7216e11dcdb57da6efb43f62280","2026-06-17T12:00:34.831Z","2026-06-17-operationid-refactoring-camelcase-ids-and-added-summary",{"id":221,"severity":25,"title":222,"summary":223,"contentHash":224,"detectedAt":225,"slug":226},"01KV9HGCXMEGXTW9MT45DFK7MF","Filter rule `id` field type changed from string to integer","The **`id`** field on filter\u002Frule group objects has been retyped from `\"type\": \"string\"` to `\"type\": \"integer\"` in 7 places across the spec. Clients that treat this field as a string (e.g. storing it as `\"123\"`, comparing with `===`, or passing it in a string-typed variable) will break when the API returns or requires a numeric value instead.","0f1d4687cc0e41519a2a215780b05b255d925cfb0ac99382b0b02f70f4e141ed","2026-06-17T01:00:39.220Z","2026-06-17-filter-rule-id-field-type-changed-from-string-to-integer",{"id":228,"severity":32,"title":229,"summary":230,"contentHash":231,"detectedAt":232,"slug":233},"01KV9E2FEQ8M7X0YWFMAYQ0A34","Add optional team name field and query parameters","Added optional `name` field to team objects (max 64 chars), marked two endpoints as deprecated (`Submit User Feedback` and `List a Project's Issues`), and added new optional query parameters `sort` and `limit` to the issues endpoint plus `project` and `per_page` to an unspecified releases\u002Fprojects endpoint. These changes are additive; deprecation markers inform clients of planned removals without breaking existing functionality.","53d7ee41c892558674d4b3cb85092d8476c62c042c0c48dff3e24dd09c6bd9a7","2026-06-17T00:00:37.335Z","2026-06-17-add-optional-team-name-field-and-query-parameters",{"id":235,"severity":32,"title":236,"summary":237,"contentHash":238,"detectedAt":239,"slug":240},"01KV976QMQSR8D6YYDT2KVC7XD","Add optional per_page query parameter to listing endpoints","Two listing endpoints now accept an optional `per_page` query parameter to control pagination result size. The parameter accepts integer values with a default and maximum of 100. This is a purely additive change that allows clients more control over pagination without affecting existing code.","7a9f3b38b31d4fdb65c86ed9179ecc629e25b6ff753842112ddf19b0167477a0","2026-06-16T22:00:36.759Z","2026-06-16-add-optional-per-page-query-parameter-to-listing-endpoints",{"id":242,"severity":32,"title":243,"summary":244,"contentHash":245,"detectedAt":246,"slug":247},"01KV8JMDAWSDR360F3FFG902XE","Add pr_iteration to autofix step enum","A new enum value `pr_iteration` has been added to the autofix step parameter in two Sentry API endpoints. This is an additive change that allows clients to use a new optional step type without breaking existing integrations that use the previous enum values.","9fc2ba7168d770709980498ed982be180b23f87b91e952a491744682faa3a97c","2026-06-16T16:01:04.860Z","2026-06-16-add-pr-iteration-to-autofix-step-enum",{"id":249,"severity":32,"title":250,"summary":251,"contentHash":252,"detectedAt":253,"slug":254},"01KV6AGM3TZ59V99VAC8AEVAA5","Monitor and Notification Action endpoints now accept project IDs","The Sentry API now accepts project IDs in addition to project slugs for monitor and notification action endpoints. The `project` parameter schema for monitors is expanded to accept both `integer` (ID) and `string` (slug) types, and documentation is updated across multiple endpoints to reflect this new capability. This is backward compatible and enables additional flexible project identification.","1686f95d23c3a888c1a5729007b85cca61b9bcca85461a1cc4850fe9a6a5204d","2026-06-15T19:00:43.258Z","2026-06-15-monitor-and-notification-action-endpoints-now-accept",{"id":256,"severity":32,"title":257,"summary":258,"contentHash":259,"detectedAt":260,"slug":261},"01KV63MY703D40CVJESAN7C5C6","Allow project slugs in addition to IDs in query filters","The `project` query parameter on three endpoints now accepts both integer project IDs and string project slugs (via `anyOf` schema union), whereas it previously accepted only integers. This is backward-compatible because existing integer-based code will continue to work. Additionally, documentation for the `yAxis` parameter on the timeseries endpoint was expanded with detailed examples of available aggregation functions, and a note about accuracy limitations for certain query patterns was added to the endpoint description.","07c372da80dac77d93626faa46cfa3d99d4a8a52bf7a80010776b4f7d54ab8c4","2026-06-15T17:00:44.640Z","2026-06-15-allow-project-slugs-in-addition-to-ids-in-query-filters",{"id":263,"severity":32,"title":264,"summary":265,"contentHash":266,"detectedAt":267,"slug":268},"01KV606T1FA7CYECXHJCKSYYS4","Add heatmap visualization type option","A new enum value `heatmap` has been added to visualization type fields across multiple dashboard\u002Fwidget endpoints in the Sentry API. This is a purely additive change that expands the available visualization options without breaking existing integrations that use other visualization types.","471fc2362bae81056f86f35ad2145cc7fd74665a5e46a7637e7d16234890c64c","2026-06-15T16:00:35.887Z","2026-06-15-add-heatmap-visualization-type-option",{"id":270,"severity":271,"title":272,"summary":273,"contentHash":274,"detectedAt":275,"slug":276},"01KTZ11JVE5D66F3BQ1EEBFVT6","Deprecation","Deprecate project_id query param; add project param","The `project_id` query parameter is now deprecated on release endpoints in favor of a new `project` parameter that accepts both integer IDs and string slugs. The new `project` parameter overrides `project_id` when both are provided, allowing more flexible project filtering.","d2493e91566c3e7b914cd61e87d2d5e877b8731f19f02075420349d81a778d4e","2026-06-12T23:00:32.238Z","2026-06-12-deprecate-project-id-query-param-add-project-param",{"id":278,"severity":32,"title":279,"summary":280,"contentHash":281,"detectedAt":282,"slug":283},"01KTYKAPPWNDB3ZW7CZHBHNZER","Accept project slugs in project filter parameter","The `project` query parameter now accepts both integer project IDs and string project slugs (e.g., `android` or `javascript-react`), expanding the ways to filter events and issues. Additionally, the Autofix API now includes a new `sentry_run_id` (UUID) field while retaining the legacy `run_id` (integer) field for backward compatibility.","6fb2b934b3bd983e9d06460538798d4411b1151e3262d540b90d41b09562082f","2026-06-12T19:00:51.036Z","2026-06-12-accept-project-slugs-in-project-filter-parameter",{"id":285,"severity":25,"title":286,"summary":287,"contentHash":288,"detectedAt":289,"slug":290},"01KTW7SC6AMMZBDKA5148C5T9R","GET endpoint for downloading snapshot images as ZIP removed","The `GET \u002Fapi\u002F0\u002Forganizations\u002F{organization_id_or_slug}\u002Fpreprodartifacts\u002Fsnapshots\u002F{snapshot_id}\u002Fdownload\u002F` endpoint has been removed from the API spec. Any clients calling this endpoint to download snapshot images as a ZIP archive will receive a 404 or routing error, breaking their integration.","a74eb496afb18b2cf0de93577ff4bd3c28871d9422ef3f52d790756d31c3035d","2026-06-11T21:00:40.010Z","2026-06-11-get-endpoint-for-downloading-snapshot-images-as-zip-removed",{"id":292,"severity":25,"title":293,"summary":294,"contentHash":295,"detectedAt":296,"slug":297},"01KTVXFVEXA13PFVBYPDCV2Q3M","Remove `setupDialog` field from integration provider response schema","The **`setupDialog`** field has been removed from the integration provider object schema in the response for listing available integrations. It was previously a required field (`object` type with `additionalProperties`) containing `url`, `width`, and `height` for the setup dialog. Any client code reading `setupDialog` from integration provider responses will now receive `undefined`\u002Fmissing and may break if it doesn't guard against absence.","2dda1d9fc9bc744a29a04392e28fd583d193bb5e7814c2462a2c1cc481456a1b","2026-06-11T18:00:42.205Z","2026-06-11-remove-setupdialog-field-from-integration-provider-response",{"id":299,"severity":25,"title":300,"summary":301,"contentHash":302,"detectedAt":303,"slug":304},"01KTQGQG29XB5H32W9600N4Y95","GetReplayRecordingSegment response changed from array to typed object","The `200` response schema for the \"Retrieve a Replay Segment\" endpoint has changed from an **array of arbitrary objects** (`array` of `object` with `additionalProperties`) to a **typed object** with a required `data` property containing `replayId`, `segmentId`, `projectId`, and `dateAdded` fields. This is a breaking change: any client code iterating over the response as an array, or accessing raw segment event data (e.g. `type`, `timestamp`, `data.tag`), will break. The new shape wraps metadata in `data` and no longer returns the raw recording segment events.","ccf640e500fc02a428e33df9bf749e6b8b52df4f9c5398c75f2ccd319fa3c2f9","2026-06-10T01:00:43.465Z","2026-06-10-getreplayrecordingsegment-response-changed-from-array-to",{"id":306,"severity":32,"title":307,"summary":308,"contentHash":309,"detectedAt":310,"slug":311},"01KTQD9CE5MEBF6WQ2KMCT59WG","Allow null values in debug configuration fields","Three debug configuration schema objects now allow `null` values by adding `\"nullable\": true` to their definitions. This is backward compatible — existing code sending non-null values will continue to work, and clients can now optionally handle null values for these fields.","e55a2b43001790d36189547e51658bf265c72207022ccadb1c2b7b674fa56687","2026-06-10T00:00:35.269Z","2026-06-10-allow-null-values-in-debug-configuration-fields",{"id":313,"severity":39,"title":314,"summary":315,"contentHash":316,"detectedAt":317,"slug":318},"01KTQ9VRGCX86V62GT3DDFEH7A","OutgoingNotificationAction schema fully defined, replacing additionalProperties","The `OutgoingNotificationAction` schema (and corresponding inline response schemas for spike-protection notification action endpoints) was previously defined as `\"additionalProperties\": {}` (i.e. an opaque object). It now has explicit properties: `id`, `organizationId`, `integrationId`, `sentryAppId`, `projects`, `serviceType`, `triggerType`, `targetType`, `targetIdentifier`, and `targetDisplay`, all marked as required. Additionally, example values for `id` and `organizationId` were corrected from strings (`\"836501735\"`) to integers (`836501735`), aligning with the new `integer` type declarations. This is a documentation\u002Fschema clarification — the underlying API behaviour has not changed, but client code generated from the old schema (which accepted any shape) may now be validated against a stricter schema.","10b07617746bf1f47d339d29151c0f9ff9cb648defe1b854d037cb0ce8dd97b8","2026-06-09T23:00:43.148Z","2026-06-09-outgoingnotificationaction-schema-fully-defined-replacing",{"id":320,"severity":32,"title":321,"summary":322,"contentHash":323,"detectedAt":324,"slug":325},"01KTQ6DR6FWNKK2GAZ6A1AKS79","Add avatarUrl field to avatar objects across team endpoints","The `avatarUrl` field is being added to `avatar` objects in multiple team-related API responses (create team, retrieve team, update team, list teams, remove member, add member). This is a purely additive change that provides an additional optional field in the response without removing or modifying existing fields, so existing clients will continue to work unaffected.","1bfd0d0c9bdf33136b30f88ac08559cd6750fab69583c2e0054ef8eaf779fe9e","2026-06-09T22:00:38.351Z","2026-06-09-add-avatarurl-field-to-avatar-objects-across-team-endpoints",{"id":327,"severity":25,"title":328,"summary":329,"contentHash":330,"detectedAt":331,"slug":332},"01KTPRPJBK068DH3R8XX399XZF","Replays list response wrapped in a `data` envelope object","The 200 response schema for the replays list endpoint changed from a **top-level array** to an **object with a required `data` property** containing that array. Clients that currently index directly into the response array (e.g. `response[0]`) will break and must be updated to `response.data[0]`. A second, similar wrapping change is visible for the individual replay response schema as well.","9b1f4396c18f581d4aa5d6573ca2781807212b08d30a550f72bb565edbfbb42b","2026-06-09T18:00:47.219Z","2026-06-09-replays-list-response-wrapped-in-a-data-envelope-object",{"id":334,"severity":32,"title":335,"summary":336,"contentHash":337,"detectedAt":338,"slug":339},"01KTPN8JJRC5Z2ZVZVPJ7V6FS0","Add PUT endpoint for bulk updating project environments","A new `PUT` endpoint was added to bulk update the visibility (hidden\u002Fshown) of multiple project environments at once. This is a purely additive change that allows clients to show or hide up to 1000 environments in a single request, requiring `project:admin` or `project:write` scopes.","60e0341bdb106d5be78485f755d1760b2e3b4a3bc08bd6565a9e52cf93dd6b9d","2026-06-09T17:00:42.968Z","2026-06-09-add-put-endpoint-for-bulk-updating-project-environments",{"id":341,"severity":32,"title":342,"summary":343,"contentHash":344,"detectedAt":345,"slug":346},"01KTMH58ZGWM60T2HCV8EDQKPN","Add new fields to issue schema and structure object fields","Two sets of additive changes to issue schemas: (1) new nullable fields `matchingEventId` and `matchingEventEnvironment` added to issue objects, now marked as required in the schema; (2) the `inbox`, `owners`, and `sentryAppIssues` object fields previously defined as open objects (additionalProperties: {}) are now explicitly structured with defined properties and required fields, improving schema specificity without breaking existing integrations.","2c321b4836881f6d9b281ad077f9915f066c8f2ea4f1dded8d1459d75f722fbc","2026-06-08T21:10:31.664Z","2026-06-08-add-new-fields-to-issue-schema-and-structure-object-fields",{"id":348,"severity":32,"title":349,"summary":350,"contentHash":351,"detectedAt":352,"slug":353},"01KTMD5N40ZFKSA20Z0QXG8YRT","Add format constraints and nullable to DSN key fields","The Sentry API schema now marks the `publicKey` field as `nullable: true` and adds `format: date-time` constraints to `firstSeen` and `lastSeen` fields in DSN key response schemas. These changes clarify the API contract without removing or breaking existing functionality — clients already handling these fields will continue to work.","e96f13edc61988cbf0462336a0597b134a2743492b81e25f2a1fb90657591462","2026-06-08T20:00:49.792Z","2026-06-08-add-format-constraints-and-nullable-to-dsn-key-fields",{"id":355,"severity":32,"title":356,"summary":357,"contentHash":358,"detectedAt":359,"slug":360},"01KTC888J8WV05FRSX2F6522EF","Add optional project query parameter","A new optional `project` query parameter has been added to filter results by project IDs (as an array of integers). This is purely additive and provides an alternative way to filter by projects; existing integrations using the existing `project_id_or_slug` parameter continue to work unchanged.","b3117ebe2ce985d2bd907a27ef8582514558de68926efde8bb762cdc92b772c1","2026-06-05T16:00:56.904Z","2026-06-05-add-optional-project-query-parameter",{"id":362,"severity":39,"title":363,"summary":364,"contentHash":365,"detectedAt":366,"slug":367},"01KTC4SY2N1WRYGS4ZR43PZE15","Add pagination documentation links to cursor parameter","Added `x-learn-more` metadata field pointing to pagination documentation (`https:\u002F\u002Fdocs.sentry.io\u002Fapi\u002Fpagination\u002F`) to the `cursor` query parameter across 30 endpoints. This is a documentation enhancement that does not alter the API's functional behavior or response schemas.","faaf0d5f88d007f6f3c194a6a0b989c7a12bcb7e400233290d7f6183d4ea76f5","2026-06-05T15:00:41.685Z","2026-06-05-add-pagination-documentation-links-to-cursor-parameter",{"id":369,"severity":25,"title":370,"summary":371,"contentHash":372,"detectedAt":373,"slug":374},"01KTAHA3TSQZ3HX2GQD9VPE4D6","GET \u002Fapi\u002F0\u002Fprojects\u002F...\u002Fusers\u002F response schema expanded with required fields","The `GET \u002Fapi\u002F0\u002Fprojects\u002F{organization_id_or_slug}\u002F{project_id_or_slug}\u002Fusers\u002F` endpoint's response schema was replaced with a much richer object. The old schema only required `username` (nullable) and `email` (nullable); the new schema requires **8 additional non-nullable fields**: `avatarUrl`, `dateCreated`, `hash`, `id`, `identifier`, `ipAddress`, `name`, and `tagValue`. Additionally, the required OAuth scope changed from `project:read` alone to `project:admin`, `project:read`, or `project:write`, and the `cursor` parameter now has `minLength: 1`. Clients that previously received only `username`\u002F`email` may need to handle the new shape, and tooling that validated the old minimal schema will now see unexpected required fields.","73431dc4c32fe23478721a0617b67abdf3fe5dff152797cf2031275df9c3f2aa","2026-06-05T00:00:45.913Z","2026-06-05-get-api-0-projects-users-response-schema-expanded-with"]