# /v2/alerts_violations stops working

Calls to /v2/alerts_violations* on New Relic REST API stop working on July 31, 2027.

On July 31, 2027, the endpoint /v2/alerts_violations* reaches end of life and stops working. Starting on that date, requests sent to these routes fail. The change shuts down the affected New Relic REST API v2 endpoints entirely.

## What to use instead

Switch to reading incidents through the NerdGraph GraphQL API using the NrAiIncident Incident API.

- API: New Relic REST API (api.newrelic.com)
- Kind: Version retirement
- Announced: July 28, 2026
- Takes effect: July 31, 2027
- Calls after that day: fail
- Calls it hits: `/v2/alerts_violations*`
- Source: [Announcement](https://docs.newrelic.com/eol/2026/07/eol-07-31-26-rest-api-v2/)
- Verified: November 6, 2026, against New Relic REST API's own pages
- Page: https://www.okapi.bot/providers/new-relic-rest-api/breaking-changes/v2-alerts-violations-stops-working/

## New Relic REST API's words

> Effective July 31, 2027, the New Relic REST API v2 (excluding some Alerts endpoints) and the Deployments v0 API will reach end of life (EOL). After this date, these API endpoints will no longer be available.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent