API CHANGE TRACKER / Sentry

Sentry breaking change: GET /api/0/organizations/{organization_id_or_slug}/replays/

removed the enum value `warning_ids` from the property `items/` of the `query` request parameter `field`

Specification capture: . Published evidence last updated . This is captured contract evidence, not an observed outage or a result from scanning your code.

Which field and classification rule changed?

Changed field
items/
Rule ID
request.enum_removed
Classifier version
2026-10-15.2
Direction
request
Finding ID
chg_7bbb35ef814d3f1426e4fd9a70023d6884dec123f4f6e4981754775570da14a3

What is the recorded before and after evidence?

Previous specification SHA-256: a110089f41075cbee59114611b4d1385c8b1a95fd9b65465c8d5ed8d3e490518

Revised specification SHA-256: 0689f5be1685af4feae84005801b76f26e5ff34f6f7b13178e76891caeaa2a98

Publisher version: v0 to v0.

  ...
              * `has_viewed`
              * `id`
-             * `info_ids`
              * `is_archived`
              * `os`
  ...
              * `urls`
              * `user`
-             * `warning_ids`
            enum:
              - activity
  ...
              - has_viewed
              - id
-             - info_ids
              - is_archived
              - os
  ...
              - urls
              - user
-             - warning_ids
            type: string
          type: array
  ...

Inspect the complete release · Public source findings · Publisher specification source

How do I check whether this affects my code?

Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.

Check an authorized repository · Review coverage · Inspect classification rules