DOCUMENTATION / API COMPATIBILITY

Sentry OpenAPI breaking changes: removed replay query values.

By Soumik Ghosh · Published 3 November 2026

This report examines one captured Sentry specification finding, not a live service incident or a scan of your application. The finding is classified as breaking by request.enum_removed.

What changed in the captured specification?

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

Operation

GET /api/0/organizations/{organization_id_or_slug}/replays/

Field

items/

Capture date (UTC)

2026-10-23

Publisher version

v0 to v0. An unchanged publisher version can still contain a changed contract.

Classifier version

2026-10-15.2

Which exact revisions were compared?

Previous specification SHA-256: a110089f41075cbee59114611b4d1385c8b1a95fd9b65465c8d5ed8d3e490518

Revised specification SHA-256: 0689f5be1685af4feae84005801b76f26e5ff34f6f7b13178e76891caeaa2a98

Inspect the recorded release or read the public source finding. Capture dates identify evidence collection; they do not establish when a provider deployed behavior.

How could this affect an existing caller?

A caller sending field=info_ids no longer fits the captured enum. Inspect where the query value is selected and what the application needs from it. The diff does not identify a replacement value.

GET /api/0/organizations/example/replays/?field=info_ids

This is an illustrative request, not a request sent by this page.

How do I check my TypeScript or Python integration?

1. Confirm the operation and field used by your code against the captured revisions.
2. Authorize the repositories you want analyzed and inspect supported SDK or HTTP call-site matches.
3. Review uncertain patterns and select application behavior explicitly.
4. Check the proposal's schema, type, configured runtime, and repository CI evidence before delivery.

Browse the Sentry specification history, replay captured examples, or check supported coverage.