Sentry
GET /api/0/projects/{id}/{id}/issues endpoint removal
Deprecated, no dateSubscribe to SentryShare
Sentry has deprecated the GET /api/0/projects/{id}/{id}/issues endpoint without specifying a shutdown date. Calls made to this endpoint will eventually fail as the endpoint is removed. Sentry notes that it has been replaced by an endpoint that supports project filtering alongside additional functionality.
Calls it hits
GET /api/0/projects/{id}/{id}/issues
What to use instead of these calls
Use GET /api/0/organizations/{organization_id_or_slug}/issues/ with a project filter instead.
In Sentry's words
This endpoint has been replaced with the Organization Issues endpoint which supports filtering on project and additional functionality.
Facts
- API
- Sentry
sentry.io - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Sentry's own pages
Questions
When does this change take effect?
Sentry deprecated GET /api/0/projects/{id}/{id}/issues without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Sentry has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.