New Relic REST API v2 and Deployments v0 API, end-of-life effective July 31, 2027

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.

Background

This retirement is part of the ongoing work to improve our platform and streamline our APIs, ensuring continued innovation and a more sustainable system. REST API v2 functionalities are available through NerdGraph, New Relic's GraphQL API, which offers a single unified endpoint, precise data fetching, and strong data typing — providing a more robust, consistent, and unified experience.

What's changing

The following API endpoints will be permanently retired on July 31, 2027:

https://api.newrelic.com/v2/: US datacenter (including the Alerts endpoints, /v2/alerts*, but excluding the retained conditions and policies namespaces listed under Not impacted below)
https://api.eu.newrelic.com/v2/: EU datacenter (including the Alerts endpoints, /v2/alerts*, but excluding the retained conditions and policies namespaces listed under Not impacted below)
https://rpm.newrelic.com/deployments: Legacy Deployments v0 API

Alerts

The following Alerts endpoints are being retired. Each one has a NerdGraph replacement that covers the common use cases:

alerts_violations: EOL the REST violations endpoint; customers can migrate to the NerdGraph Incident API (NrAiIncident)
alerts_incidents: EOL the REST incidents endpoint; customers can migrate to the NerdGraph Issues API (NrAiIssue). (Note: "incident" was renamed to "issue" in the modern model)
alerts_channels: EOL the REST channels endpoint; customers can migrate to Notifications Workflows and Destinations by updating API calls to use the NerdGraph APIs or update your terraform to use the workflows and destinations resources.
alerts_events: EOL the REST events endpoint; most accounts use it for deployments and migrate to the NerdGraph change tracking API. Accounts using the feature flag for alert-related event data have no direct replacement today — handled case-by-case via Support.

If you run into challenges with your migration please reach out to Support.

Not impacted:

The following Alerts conditions and policies namespaces are not affected — no action needed:
- /alerts_policies/*
- /alerts_conditions/*
- /alerts_nrql_conditions/*
- /alerts_external_service_conditions/*
- /alerts_synthetics_conditions/*
- /alerts_location_failure_conditions/policies/*
- /alerts_entity_conditions/*
The NerdGraph GraphQL APIs hosted on the same domain (https://api.newrelic.com/graphql, https://api.eu.newrelic.com/graphql) are not affected
New Relic agent communication and data ingest are not affected for supported agent versions (versions prior to January 2026 will not be able to report deployment markers)

How do I know if I'm affected?

These API calls may originate from proprietary tools, reporting systems, or third-party integrations, and include any utilization of the affected Alerts endpoints (/v2/alerts*). To determine what action you need to take:

Identify your REST API v2 usage: Search your codebase, CI/CD pipelines, and automation scripts for calls to api.newrelic.com/v2/, api.eu.newrelic.com/v2/, and https://rpm.newrelic.com/deployments

Common integrations include:
- CI/CD pipelines that record deployments or manage browser/mobile app configuration
- Scripts that pull metric data for external dashboards or data warehousing
- Automation that checks application health status or alert conditions
Check which endpoints you use: If you use the Alerts endpoints (/v2/alerts*), they are part of this EOL.
Review the migration guide: For each REST API v2 call you identify, our migration guide provides the equivalent NerdGraph query or mutation.

What you need to do

Migrate your integrations from REST API v2 to NerdGraph before July 31, 2027:

Update your API calls to use NerdGraph: Use the migration guide for endpoint-by-endpoint mappings, including:
- Applications: list, show, update, and delete via entity search and mutations
- Metric data: query via NRQL, with a mapping table from REST API metric values to NRQL functions
- Hosts & instances: query via NRQL with host faceting
- Deployments: record via changeTrackingCreateDeployment mutation, query via NRQL
- Key transactions: query via entity search
- Mobile & browser applications: query via entity search
Test your new integrations: Use the NerdGraph API Explorer in the New Relic platform to interactively build and test queries before deploying changes.
Important note for metric data users: The REST API v2 returns metric data in a proprietary format. In NerdGraph, metric data is queried using NRQL (New Relic Query Language). While the same data is available, the response format is different. The migration guide includes a complete mapping table to help you translate your existing metric value names (for example, average_response_time, call_count) to the equivalent NRQL functions. Please allow adequate time for this migration.
If you use the Alerts endpoints (/v2/alerts*): These endpoints are part of this EOL and will be retired on July 31, 2027. Detailed migration guidance for the Alerts endpoints will follow in a supplemental announcement. In the meantime, identify where your integrations call /v2/alerts* so you're ready to migrate when that guidance is published. If you need help planning your migration, contact New Relic Support.

What happens if you take no action

After July 31, 2027, any integrations, scripts, or tools that call the REST API v2 endpoints listed above will stop working. This could affect:

Deployment tracking in your CI/CD pipelines
Metric data exports to external systems or data warehouses
Application health monitoring scripts that rely on REST API v2
Browser or mobile app provisioning automation

Resources

Additional support

We understand that migrating your integration is challenging, and our team is here to assist. If you have questions regarding these transitions or need help identifying impacted accounts, please reach out to your account team or contact support.