New Relic

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. Delete -- New users should use these docs about managing alerts via NerdGraph. This API endpoint deletes Alerts notification channels. Note: User notification channels cannot be deleted. Note: Admin User’s API Key is required. See our documentation for a discussion on deleting notification channels. via DELETE /alerts_channels/{channel_id}.json

Delete -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to delete APM Application and Key Transaction, Browser and Mobile application metric conditions for your alert policies. Conditions for web transaction percentiles, or conditions targeting labels (dynamic targeting), are not available. Note: Admin User’s API Key is required. See our documentation for a discussion on deleting conditions. via DELETE /alerts_conditions/{condition_id}.json

Remove -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to disassociate an entity with a specified Alerts condition. Note: Admin User’s API Key is required. Entity type options (Synthetics is not yet supported): BrowserApplication Application MobileApplication Server KeyTransaction via DELETE /alerts_entity_conditions/{entity_id}.json

Delete -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to delete external service conditions associated with your alert policy. Note: Admin User’s API Key is required. See our documentation for a discussion on deleting External services conditions. via DELETE /alerts_external_service_conditions/{condition_id}.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. Delete -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to Delete the alerts location failure conditions for your Alerts policy. via DELETE /alerts_location_failure_conditions/{condition_id}.json

Delete -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to delete NRQL conditions for your Alerts policy. NRQL Baseline conditions are not available. Note: Admin User’s API Key is required. via DELETE /alerts_nrql_conditions/{condition_id}.json

Delete -- New users should use these docs about managing alerts via NerdGraph. This API endpoint deletes Alerts policies associated with your New Relic account. Note: Admin User’s API Key is required. See our documentation for a discussion on using the REST API for deleting policies. via DELETE /alerts_policies/{policy_id}.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. Delete -- New users should use these docs about managing alerts via NerdGraph. This API endpoint deletes Alerts policy/channel associations. Note: Admin User’s API Key is required. See our documentation for a discussion on deleting notification channels with policies. via DELETE /alerts_policy_channels.json

Delete -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to delete Synthetics conditions associated with your alert policy. Note: Admin User’s API Key is required. See our documentation for a discussion on deleting Synthetic conditions. via DELETE /alerts_synthetics_conditions/{condition_id}.json

Delete -- This API endpoint deletes the specified deployment record. Note: Admin User’s API Key is required. via DELETE /applications/{application_id}/deployments/{id}.json

Delete -- This API endpoint deletes an application and all of its reported data. WARNING: Only applications that have stopped reporting can be deleted. This is an irreversible process which will delete all reported data for this application. via DELETE /applications/{id}.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. List -- New users should use these docs about managing alerts via NerdGraph. This API endpoint works with new Alerts on alerts.newrelic.com. It returns a list of the channels associated with your New Relic account. Note: See our documentation for a discussion on listing notification channels. via GET /alerts_channels.json

List -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to list APM Application and Key Transaction, Browser and Mobile application metric conditions for your alert policies. Note: Conditions for web transaction percentiles, or conditions targeting labels (dynamic targeting), are not available. See our documentation for a discussion on output pagination. via GET /alerts_conditions.json

List -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to list the Alerts conditions an entity is part of. Entity type options (Synthetics is not yet supported): BrowserApplication Application MobileApplication Server KeyTransaction via GET /alerts_entity_conditions/{entity_id}.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. List -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to list the alert events for your account. Alerts events can be filter by product, target type, group ID, instance ID, and event type. The options for products are: APM, BROWSER, MOBILE, SERVERS, SYNTHETICS, and ALERTS. The options for entity type are: Application, Server, KeyTransaction, MobileApplication, BrowserApplication, and Monitor. The options for event type are: NOTIFICATION, DEPLOYMENT, VIOLATION_OPEN, VIOLATION_CLOSE, VIOLATION, and INSTRUMENTATION. The group ID option is normally the same as the entity ID (e.g. an Application group ID and entity ID will be the same) See our documentation for a discussion on output pagination. via GET /alerts_events.json

List -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to list the external service conditions for your alert policy. See our documentation for a discussion on output pagination. via GET /alerts_external_service_conditions.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. List -- This endpoint will be deprecated after 2027/01 New users should use these docs about managing alerts via NerdGraph. This API endpoint returns a list of the Incidents associated with your New Relic account. See our documentation for a discussion on listing incidents and output pagination. via GET /alerts_incidents.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. List -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to list the alerts location failure conditions for your Alerts policy. via GET /alerts_location_failure_conditions/policies/{policy_id}.json

List -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to list the NRQL conditions for your Alerts policy. Note: NRQL Baseline conditions are not available. via GET /alerts_nrql_conditions.json

List -- New users should use these docs about managing alerts via NerdGraph. This API endpoint works with new Alerts on alerts.newrelic.com. This API endpoint returns a list of the alert policies associated with your New Relic account. See our documentation for a discussion on output pagination. via GET /alerts_policies.json

List -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to list the Synthetics conditions for your alert policy. See our documentation for a discussion on listing Synthetic conditions and output pagination. via GET /alerts_synthetics_conditions.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. List -- New users should use these docs about managing alerts via NerdGraph. This API endpoint works with new Alerts on alerts.newrelic.com. It returns a list of the violations associated with your New Relic account. See our documentation for a discussion on output pagination. via GET /alerts_violations.json

List -- This API endpoint returns a paginated list of the deployments associated with a given application. See our documentation for a discussion on output pagination. via GET /applications/{application_id}/deployments.json

Metric Data -- This API endpoint returns a list of values for each of the requested metrics. The list of available metrics can be returned using the Metric Name API endpoint. Metric data can be filtered by a number of parameters, including multiple names and values, and by time range. Metric names and values will be matched intelligently in the background. You can also retrieve a summarized data point across the entire time range selected by using the summarize parameter. See our documentation for a discussion on output pagination, time range related considerations, and for examples of requesting and using metric values. via GET /applications/{application_id}/hosts/{host_id}/metrics/data.json

Metric Names -- Return a list of known metrics and their value names for the given resource. See our documentation for a discussion on output pagination and for examples of requesting and using metric values. via GET /applications/{application_id}/hosts/{host_id}/metrics.json

Show -- This API endpoint returns a single application host, identified by ID. The time range for summary data is the last 3-4 minutes. See our documentation for a discussion of summary data output. via GET /applications/{application_id}/hosts/{id}.json

List -- This API endpoint returns a paginated list of hosts associated with the given application. The time range for summary data is the last 3-4 minutes. Application hosts can be filtered by hostname, or the list of application host IDs. See our documentation for a discussion and examples of using filters and summary data output. via GET /applications/{application_id}/hosts.json

Show -- This API endpoint returns a single application instance, identified by ID. The time range for summary data is the last 3-4 minutes. See our documentation for a discussion of summary data output. via GET /applications/{application_id}/instances/{id}.json

Metric Data -- This API endpoint returns a list of values for each of the requested metrics. The list of available metrics can be returned using the Metric Name API endpoint. Metric data can be filtered by a number of parameters, including multiple names and values, and by time range. Metric names and values will be matched intelligently in the background. You can also retrieve a summarized data point across the entire time range selected by using the summarize parameter. See our documentation for a discussion on output pagination, time range related considerations, and for examples of requesting and using metric values. via GET /applications/{application_id}/instances/{instance_id}/metrics/data.json

Metric Names -- Return a list of known metrics and their value names for the given resource. See our documentation for a discussion on output pagination and for examples of requesting and using metric values. via GET /applications/{application_id}/instances/{instance_id}/metrics.json

List -- This API endpoint returns a paginated list of instances associated with the given application. The time range for summary data is the last 3-4 minutes. Application instances can be filtered by hostname, or the list of application instance IDs. See our documentation for a discussion and examples of using filters and summary data output. via GET /applications/{application_id}/instances.json

Metric Data -- This API endpoint returns a list of values for each of the requested metrics. The list of available metrics can be returned using the Metric Name API endpoint. Metric data can be filtered by a number of parameters, including multiple names and values, and by time range. Metric names and values will be matched intelligently in the background. You can also retrieve a summarized data point across the entire time range selected by using the summarize parameter. See our documentation for a discussion on output pagination, time range related considerations, and for examples of requesting and using metric values. via GET /applications/{application_id}/metrics/data.json

Metric Names -- Return a list of known metrics and their value names for the given resource. See our documentation for a discussion on output pagination and for examples of requesting and using metric values. via GET /applications/{application_id}/metrics.json

Show -- This API endpoint returns a single Application, identified by ID. The time range for summary data is the last 3-4 minutes. See our documentation for a discussion of the summary data output. via GET /applications/{id}.json

List -- This API endpoint returns a paginated list of the Applications associated with your New Relic account. The time range for summary data is the last 3-4 minutes. Applications can be filtered by their name, hosts, the list of application IDs or the application language as reported by the agents. See our documentation for a discussion and examples of using filters and summary data output. via GET /applications.json

Show -- This endpoint returns a single key transaction, identified by ID. The time range for summary data is the last 10 minutes. See our documentation for a discussion of summary data output. via GET /key_transactions/{id}.json

List -- This API endpoint returns a paginated list of the key transactions associated with your New Relic account. The time range for summary data is the last 10 minutes. Key transactions can be filtered by their name or list of IDs. See our documentation for a discussion of summary data output. via GET /key_transactions.json

Show -- This API endpoint returns a single Mobile Application, identified by ID. The time range for summary data is the last 30 minutes. via GET /mobile_applications/{id}.json

Metric Data -- This API endpoint returns a list of values for each of the requested metrics. The list of available metrics can be returned using the Metric Name API endpoint. Metric data can be filtered by a number of parameters, including multiple names and values, and by time range. Metric names and values will be matched intelligently in the background. You can also retrieve a summarized data point across the entire time range selected by using the summarize parameter. See our documentation for a discussion on output pagination, time range related considerations, and for examples of requesting and using metric values. via GET /mobile_applications/{mobile_application_id}/metrics/data.json

Metric Names -- Return a list of known metrics and their value names for the given resource. See our documentation for a discussion on output pagination and for examples of requesting and using metric values. via GET /mobile_applications/{mobile_application_id}/metrics.json

List -- This API endpoint returns a list of the Mobile Applications associated with your New Relic account. MobileApplications can be filtered by their name, or by the application IDs. via GET /mobile_applications.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. Create -- New users should use these docs about managing alerts via NerdGraph. This API endpoint works with new Alerts on alerts.newrelic.com. It creates a channel associated with your New Relic account. Note: Admin User’s API Key is required. See our documentation for a discussion on creating notification channels. Channel type configuration options: Email { "recipients" : "test@google.com", "include_json_attachment" : true } HipChat { "auth_token": "abc123", "room_id": "google.com" } OpsGenie { "api_key": "abc123", "teams": "team1", "tags": "tag1", "recipients": "me@me.com" } Slack { "url": "http://test.com", "channel": "channel1" } Campfire { "subdomain": "mysubdomain", "token": "123abc", "room": "room1" } Victorops { "key": "mykey", "route_key": "theroute" } PagerDuty { "service_key": "myservicekey" } Webhook (json) { "base_url": "http://test.com", "auth_username": "username", "auth_password": "password", "payload_type": "application/json", "payload": { "account_id": "$ACCOUNT_ID", "account_name": "$ACCOUNT_NAME", "condition_id": "$CONDITION_ID", "condition_name": "$CONDITION_NAME", "current_state": "$EVENT_STATE", "details": "$EVENT_DETAILS", "event_type": "$EVENT_TYPE", "incident_acknowledge_url": "$INCIDENT_ACKNOWLEDGE_URL", "incident_id": "$INCIDENT_ID", "incident_url": "$INCIDENT_URL", "owner": "$EVENT_OWNER", "policy_name": "$POLICY_NAME", "policy_url": "$POLICY_URL", "runbook_url": "$RUNBOOK_URL", "severity": "$SEVERITY", "targets": "$TARGETS", "timestamp": "$TIMESTAMP", "violation_chart_url": "$VIOLATION_CHART_URL" }, "headers": {"header1": "test", "header2": "test"} } Webhook (x-www-form-urlencoded) { "base_url": "http://test.com", "auth_username": "username", "auth_password": "password", "payload_type": "application/x-www-form-urlencoded", "payload": { "account_id": "$ACCOUNT_ID", "account_name": "$ACCOUNT_NAME", "condition_id": "$CONDITION_ID", "condition_name": "$CONDITION_NAME", "current_state": "$EVENT_STATE", "details": "$EVENT_DETAILS", "event_type": "$EVENT_TYPE", "incident_acknowledge_url": "$INCIDENT_ACKNOWLEDGE_URL", "incident_id": "$INCIDENT_ID", "incident_url": "$INCIDENT_URL", "owner": "$EVENT_OWNER", "policy_name": "$POLICY_NAME", "policy_url": "$POLICY_URL", "runbook_url": "$RUNBOOK_URL", "severity": "$SEVERITY", "targets": "$TARGETS", "timestamp": "$TIMESTAMP", "violation_chart_url": "$VIOLATION_CHART_URL" }, "headers": {"header1": "test", "header2": "test"} } via POST /alerts_channels.json

Create -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to create APM Application and Key Transaction, Browser and Mobile application metric conditions for your alert policies. Conditions for web transaction percentiles, or conditions targeting labels (dynamic targeting), are not available. Note: Admin User’s API Key is required. See our documentation for a discussion on creating conditions for policies. All fields are required except for “runbook_url”, “enabled” (defaults to false), “user_defined”. type: apm_app_metric, apm_kt_metric, servers_metric, browser_metric, mobile_metric. name: A title for your condition. enabled: The status of your condition (optional). entities: An array of instance IDs associated with your condition. metric: The metric field accepts parameters based on the condition type selected as follows: When apm_app_metric: apdex, error_percentage, response_time_web, response_time_background, throughput_web, throughput_background, user_defined. When apm_kt_metric: apdex, error_percentage, error_count, response_time, throughput. When servers_metric: cpu_percentage, disk_io_percentage, memory_percentage, fullest_disk_percentage, load_average_one_minute, user_defined. When browser_metric: end_user_apdex, total_page_load, page_rendering, web_application, network, dom_processing, request_queuing, ajax_response_time, page_views_with_js_errors, page_view_throughput, ajax_throughput, user_defined. When mobile_metric: database, images, json, network, view_loading, network_error_percentage, status_error_percentage, mobile_crash_rate, user_defined. condition_scope: Set to either instance to target a Java application instance or application for a Java app. violation_close_timer (in hours): 1, 2, 4, 8, 12, 24. Duration after which instance-based (including JVM health metric) violations will automatically close. runbook_url: Runbook URL to display in notifications (optional). terms[duration] (in minutes): 5, 10, 15, 30, 60, 120. terms[operator]: above, below, equal. terms[priority]: critical, warning. terms[threshold]: Must be 0 or greater. terms[time_function]: all, any. user_defined[metric]: A custom metric to be evaluated. user_defined[value_function]: average, min, max, total, sample_size. via POST /alerts_conditions/policies/{policy_id}.json

Create -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to create external service conditions for your alert policies. Note: Admin User’s API Key is required. See our documentation for a discussion on creating conditions for external services. All fields are required except for “runbook_url”, “enabled” (defaults to false). type: apm_external_service, mobile_external_service. name: A title for your condition. enabled: The status of your condition (optional). entities: An array of instance IDs associated with your condition. external_service_url: The URL of the external service. Must not include protocol (“example.com”, not “https://example.com”) metric: The metric field accepts parameters based on the condition type selected as follows: When apm_external_service: response_time_average, response_time_minimum, response_time_maximum, throughput. When mobile_external_service: response_time_average, response_time_minimum, response_time_maximum, throughput, network_failure_percentage, http_status_error_percentage. runbook_url: Runbook URL to display in notifications (optional). terms[duration] (in minutes): 5, 10, 15, 30, 60, 120. terms[operator]: above, below, equal. terms[priority]: critical, warning. terms[threshold]: Must be 0 or greater. terms[time_function]: all, any. via POST /alerts_external_service_conditions/policies/{policy_id}.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. Create -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to create the alerts location failure conditions for your Alerts policy. via POST /alerts_location_failure_conditions/policies/{policy_id}.json

Create -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to create NRQL conditions for your Alerts policy. Note: Admin User’s API Key is required. See our documentation for a discussion on creating conditions for policies. via POST /alerts_nrql_conditions/policies/{policy_id}.json

Create -- New users should use these docs about managing alerts via NerdGraph. This API endpoint works with new Alerts on alerts.newrelic.com. This Alerts API endpoint creates a policy associated with your New Relic account. Note: Admin User’s API Key is required. Rollup stategy options: PER_POLICY PER_CONDITION PER_CONDITION_AND_TARGET See our documentation for a discussion on using the REST API for creating new policies. via POST /alerts_policies.json

Create -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to create Synthetics conditions for your alert policies. Note: Admin User’s API Key is required. See our documentation for a discussion on creating Synthetic conditions. All fields are required except for “runbook_url”, “enabled” (defaults to false). name: A title for your condition. monitor_id: The GUID of the Synthetics monitor to alert on. runbook_url: Runbook URL to display in notifications (optional). enabled: The status of your condition (optional). via POST /alerts_synthetics_conditions/policies/{policy_id}.json

Create -- This API endpoint creates a deployment record for a given application. Deployment records are created with the following attributes: Required: - Application ID - Revision, such as a git SHA Optional: - Changelog - Description - User posting the deployment Note that the time of your deployment will be recorded as the current time in UTC. via POST /applications/{application_id}/deployments.json

Update -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to update APM Application and Key Transaction, Browser and Mobile application metric conditions for your alert policies. Conditions for web transaction percentiles, or conditions targeting labels (dynamic targeting), are not available. Note: Admin User’s API Key is required. See Alerts Conditions > Create for an explanation of the field values or the online documentation on updating conditions for policies. via PUT /alerts_conditions/{condition_id}.json

Add -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to add an entity to a specified Alerts condition. Note: Admin User’s API Key is required. Entity type options (Synthetics is not yet supported): BrowserApplication Application MobileApplication Server KeyTransaction via PUT /alerts_entity_conditions/{entity_id}.json

Update -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to update external service conditions for your alert policies. Note: Admin User’s API Key is required. See Alerts External Service Conditions > Create for an explanation of the field values used in this command or the online documentation on updating conditions for external services. via PUT /alerts_external_service_conditions/{condition_id}.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. Update -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to update the alerts location failure conditions for your Alerts policy. via PUT /alerts_location_failure_conditions/{condition_id}.json

Update -- New users should use these docs about managing alerts via NerdGraph. This API endpoint allows you to update NRQL conditions for your Alerts policy. NRQL Baseline conditions are not available. Note: Admin User’s API Key is required. See Alerts NRQL Conditions > Create for an explanation of the field values. via PUT /alerts_nrql_conditions/{condition_id}.json

Update -- New users should use these docs about managing alerts via NerdGraph. This API endpoint updates Alerts policies associated with your New Relic account. Note: Admin User’s API Key is required. See our documentation for a discussion on using the REST API for updating policies. via PUT /alerts_policies/{policy_id}.json

DEPRECATED by New Relic -- filed under its swagger tag "Deprecation Notice - ...", and retired with REST API v2 on 2027-07-31; New Relic points new users at NerdGraph for this. Still live today. Update -- New users should use these docs about managing alerts via NerdGraph. This API endpoint updates policy/channel associations. Note: Admin User’s API Key is required. See our documentation for a discussion on updating notification channels with policies. via PUT /alerts_policy_channels.json

Update -- New users should use NRQL Alert Conditions, refer to these docs about managing alerts via NerdGraph. This API endpoint allows you to update Synthetics conditions for your alert policies. Note: Admin User’s API Key is required. See our documentation for a discussion on updating Synthetic conditions. See Alerts Synthetics Conditions > Create for an explanation of the field values used in this command. via PUT /alerts_synthetics_conditions/{condition_id}.json

Update -- This API endpoint allows you to update certain parameters of your application. The input is expected to be in JSON or XML format in the body parameter of the PUT request. The exact schema is defined below. Any extra parameters passed in the body will be ignored. See our documentation for a discussion and simple example of updating an application. via PUT /applications/{id}.json