Remove non-org-scoped API endpoints

Open
#1,182 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
api

Research direction

Start in src/lib/api/alerts.ts and compare the affected issue-alert functions with sentry-mcp's listIssueAlertRulesPage() implementation pattern. Update the five listed functions to use the organization-scoped workflows endpoints, while leaving getReplayRecordingSegments and getTraceItemDetail unchanged because no replacement is available. Done means those listed requests no longer use the deprecated project-scoped rules paths.

Written by the indexing model from the issue text.

Description

Summary

/projects/{org}/{project}/rules/ (issue alert rules) was formally deprecated on 2026-05-14 with active brownouts — Sentry returns HTTP 410 GONE every 2 hours for 2 minutes. These are actively failing for users. This is urgent.

The replacement is /organizations/{org}/workflows/. sentry-mcp already uses this — see listIssueAlertRulesPage() there for the implementation pattern.

Affected endpoints in src/lib/api/alerts.ts

  • listIssueAlertsPaginated() — /projects/${org}/${project}/rules/ → /organizations/${org}/workflows/
  • fetchIssueAlertRuleJson() / getIssueAlertRule() — /projects/${org}/${project}/rules/${id}/ → /organizations/${org}/workflows/?id=${id}
  • deleteIssueAlertRule() — DELETE /projects/${org}/${project}/rules/${id}/ → DELETE /organizations/${org}/workflows/${id}/
  • putIssueAlertRule() — PUT /projects/${org}/${project}/rules/${id}/ → PUT /organizations/${org}/workflows/${id}/
  • createIssueAlertRule() — POST /projects/${org}/${project}/rules/ → POST /organizations/${org}/workflows/

Not formally deprecated — no org-scoped equivalent yet

getReplayRecordingSegments and getTraceItemDetail use project-scoped paths with no @deprecated marker. Blocked on getsentry/sentry#118963.

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
22h 3m
Merged PRs (30d)
94

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.