openapi: 3.1.0 info: title: New Relic Event Alerts Channels API description: The New Relic Event API allows you to send custom event data to the New Relic platform via HTTP POST. Custom events submitted through this API can be queried and visualized using NRQL, making it suitable for tracking arbitrary business or application events. Each event is a JSON object with an eventType and any number of additional attribute key-value pairs. version: '1' contact: name: New Relic Support url: https://support.newrelic.com/ termsOfService: https://newrelic.com/termsandconditions/terms x-last-validated: '2026-04-18' servers: - url: https://insights-collector.newrelic.com description: US Production - url: https://insights-collector.eu01.nr-data.net description: EU Production security: - apiKey: [] tags: - name: Channels paths: /alerts_channels.json: get: tags: - Channels summary: New Relic Get Alerts Channels description: '🔥 This endpoint will be deprecated after 2024/01 🔥 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.
' parameters: - name: page in: query description: Pagination index schema: type: integer example: 100 responses: '200': description: No response was specified headers: link: description: 'Links to related resources, in the format defined by [RFC 5988](https://tools.ietf.org/html/rfc5988#section-5). This will include a link with relation type `next` to the next page and `last` to the last page, unless this page is itself the last page. ' schema: type: array items: type: string content: application/json: schema: $ref: '#/components/schemas/ChannelResponse' examples: Getalertschannels200Example: summary: Default getAlertsChannels 200 response x-microcks-default: true value: channel: configuration: {} id: {} links: {} name: {} type: {} application/xml: schema: $ref: '#/components/schemas/ChannelResponse' examples: Getalertschannels200Example: summary: Default getAlertsChannels 200 response x-microcks-default: true value: channel: configuration: {} id: {} links: {} name: {} type: {} x-api-evangelist-processing: PascalCaseOperationSummaries: true CaselCaseOperationIds: true GenerateOperationSummariesFromPath: true ChooseTags: true operationId: getAlertsChannels x-microcks-operation: delay: 0 dispatcher: FALLBACK post: tags: - Channels summary: New Relic Post Alerts Channels description: "🔥 This endpoint will be deprecated after 2024/01 🔥 New users should use these docs about managing alerts via NerdGraph.\n\nThis API endpoint works with new Alerts on alerts.newrelic.com.
\n\nIt creates a channel associated with your New Relic account.
\n\nNote: Admin User’s API Key is required.
\n\nSee our documentation for a discussion on creating notification channels.
\n\nChannel type configuration options:
\n\n{
\n\n\"recipients\" : \"test@google.com\",\n\"include_json_attachment\" : true\n\n\n }
\nHipChat
\n\n{
\n\n\"auth_token\": \"abc123\",\n\"room_id\": \"google.com\"\n\n\n }
\nOpsGenie
\n\n{
\n\n\"api_key\": \"abc123\",\n\"teams\": \"team1\",\n\"tags\": \"tag1\",\n\"recipients\": \"me@me.com\"\n\n\n }
\nSlack
\n\n{
\n\n\"url\": \"http://test.com\",\n\"channel\": \"channel1\"\n\n\n }
\nCampfire
\n\n{
\n\n\"subdomain\": \"mysubdomain\",\n\"token\": \"123abc\",\n\"room\": \"room1\"\n\n\n }
\nVictorops
\n\n{
\n\n\"key\": \"mykey\",\n\"route_key\": \"theroute\"\n\n\n }
\nPagerDuty
\n\n{
\n\n\"service_key\": \"myservicekey\"\n\n\n }
\nWebhook (json)
\n\n{
\n\n\"base_url\": \"http://test.com\",\n\"auth_username\": \"username\",\n\"auth_password\": \"password\",\n\"payload_type\": \"application/json\",\n\"payload\": {\n \"account_id\": \"$ACCOUNT_ID\",\n \"account_name\": \"$ACCOUNT_NAME\",\n \"condition_id\": \"$CONDITION_ID\",\n \"condition_name\": \"$CONDITION_NAME\",\n \"current_state\": \"$EVENT_STATE\",\n \"details\": \"$EVENT_DETAILS\",\n \"event_type\": \"$EVENT_TYPE\",\n \"incident_acknowledge_url\": \"$INCIDENT_ACKNOWLEDGE_URL\",\n \"incident_id\": \"$INCIDENT_ID\",\n \"incident_url\": \"$INCIDENT_URL\",\n \"owner\": \"$EVENT_OWNER\",\n \"policy_name\": \"$POLICY_NAME\",\n \"policy_url\": \"$POLICY_URL\",\n \"runbook_url\": \"$RUNBOOK_URL\",\n \"severity\": \"$SEVERITY\",\n \"targets\": \"$TARGETS\",\n \"timestamp\": \"$TIMESTAMP\",\n \"violation_chart_url\": \"$VIOLATION_CHART_URL\"\n},\n\"headers\": {\"header1\": \"test\", \"header2\": \"test\"}\n\n\n }
\nWebhook (x-www-form-urlencoded)
\n\n{
\n\n\"base_url\": \"http://test.com\",\n\"auth_username\": \"username\",\n\"auth_password\": \"password\",\n\"payload_type\": \"application/x-www-form-urlencoded\",\n\"payload\": {\n \"account_id\": \"$ACCOUNT_ID\",\n \"account_name\": \"$ACCOUNT_NAME\",\n \"condition_id\": \"$CONDITION_ID\",\n \"condition_name\": \"$CONDITION_NAME\",\n \"current_state\": \"$EVENT_STATE\",\n \"details\": \"$EVENT_DETAILS\",\n \"event_type\": \"$EVENT_TYPE\",\n \"incident_acknowledge_url\": \"$INCIDENT_ACKNOWLEDGE_URL\",\n \"incident_id\": \"$INCIDENT_ID\",\n \"incident_url\": \"$INCIDENT_URL\",\n \"owner\": \"$EVENT_OWNER\",\n \"policy_name\": \"$POLICY_NAME\",\n \"policy_url\": \"$POLICY_URL\",\n \"runbook_url\": \"$RUNBOOK_URL\",\n \"severity\": \"$SEVERITY\",\n \"targets\": \"$TARGETS\",\n \"timestamp\": \"$TIMESTAMP\",\n \"violation_chart_url\": \"$VIOLATION_CHART_URL\"\n},\n\"headers\": {\"header1\": \"test\", \"header2\": \"test\"}\n\n\n }
\nThis 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.
' parameters: - name: channel_id in: path description: Channel ID required: true schema: type: integer example: 100 responses: '200': description: No response was specified content: application/json: schema: $ref: '#/components/schemas/ChannelResponse' examples: Deletealertschannelschannelid200Example: summary: Default deleteAlertsChannelsChannelId 200 response x-microcks-default: true value: channel: configuration: {} id: {} links: {} name: {} type: {} application/xml: schema: $ref: '#/components/schemas/ChannelResponse' examples: Deletealertschannelschannelid200Example: summary: Default deleteAlertsChannelsChannelId 200 response x-microcks-default: true value: channel: configuration: {} id: {} links: {} name: {} type: {} x-api-evangelist-processing: PascalCaseOperationSummaries: true CaselCaseOperationIds: true GenerateOperationSummariesFromPath: true ChooseTags: true operationId: deleteAlertsChannelsChannelId x-microcks-operation: delay: 0 dispatcher: FALLBACK /alerts_policy_channels.json: put: tags: - Channels summary: New Relic Put Alerts Policy Channels description: '🔥 This endpoint will be deprecated after 2024/01 🔥 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.
' parameters: - name: policy_id in: query description: Policy ID required: true schema: type: integer example: 100 - name: channel_ids in: query description: Channel IDs required: true style: form explode: false schema: type: array items: type: string example: - '500123' responses: '200': description: No response was specified content: application/json: schema: $ref: '#/components/schemas/PolicyChannelsResponse' examples: Putalertspolicychannels200Example: summary: Default putAlertsPolicyChannels 200 response x-microcks-default: true value: policy: channel_ids: {} id: {} application/xml: schema: $ref: '#/components/schemas/PolicyChannelsResponse' examples: Putalertspolicychannels200Example: summary: Default putAlertsPolicyChannels 200 response x-microcks-default: true value: policy: channel_ids: {} id: {} x-api-evangelist-processing: PascalCaseOperationSummaries: true CaselCaseOperationIds: true GenerateOperationSummariesFromPath: true ChooseTags: true operationId: putAlertsPolicyChannels x-microcks-operation: delay: 0 dispatcher: FALLBACK delete: tags: - Channels summary: New Relic Delete Alerts Policy Channels description: '🔥 This endpoint will be deprecated after 2024/01 🔥 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.
' parameters: - name: policy_id in: query description: Policy ID required: true schema: type: integer example: 100 - name: channel_id in: query description: Channel ID required: true schema: type: integer example: 100 responses: '200': description: No response was specified content: application/json: schema: $ref: '#/components/schemas/ChannelResponse' examples: Deletealertspolicychannels200Example: summary: Default deleteAlertsPolicyChannels 200 response x-microcks-default: true value: channel: configuration: {} id: {} links: {} name: {} type: {} application/xml: schema: $ref: '#/components/schemas/ChannelResponse' examples: Deletealertspolicychannels200Example: summary: Default deleteAlertsPolicyChannels 200 response x-microcks-default: true value: channel: configuration: {} id: {} links: {} name: {} type: {} x-api-evangelist-processing: PascalCaseOperationSummaries: true CaselCaseOperationIds: true GenerateOperationSummariesFromPath: true ChooseTags: true operationId: deleteAlertsPolicyChannels x-microcks-operation: delay: 0 dispatcher: FALLBACK components: schemas: PolicyChannelsResponseType: type: object properties: channel_ids: type: array items: type: integer example: - 100 id: type: integer example: 100 ChannelBody: type: object properties: configuration: type: object properties: {} example: {} name: type: string example: example-resource-01 type: type: string example: standard ChannelLinksResponse: type: object properties: policy_ids: type: array items: type: integer example: - 100 PolicyChannelsResponse: type: object properties: policy: $ref: '#/components/schemas/PolicyChannelsResponseType' Channel: type: object properties: channel: $ref: '#/components/schemas/ChannelBody' ChannelResponse: type: object properties: channel: $ref: '#/components/schemas/ChannelResponseType' ChannelResponseType: type: object properties: configuration: type: object properties: {} example: {} id: type: integer example: 100 links: $ref: '#/components/schemas/ChannelLinksResponse' name: type: string example: example-resource-01 type: type: string example: standard securitySchemes: apiKey: type: apiKey in: header name: Api-Key description: New Relic License Key or Ingest API Key externalDocs: description: New Relic Event API Documentation url: https://docs.newrelic.com/docs/data-apis/ingest-apis/event-api/introduction-event-api/