New Relic

New Relic is a comprehensive application performance monitoring and observability platform that provides real-time insights into application performance, infrastructure health, user experience metrics, and system reliability to help organizations optimize their digital operations and troubleshoot issues effectively.

Power end-to-end data operations for your New Relic API with Nexla. Our bi-directional New Relic connector is purpose-built for New Relic, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to New Relic or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your New Relic workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a New Relic credential, you need to obtain your API key and identify your root URL from your New Relic account. New Relic uses API key authentication for all API requests, with the API key sent in the x-api-key header.

To obtain your New Relic API credentials, follow these steps:

1. Sign in to your New Relic account using your administrator credentials.

2. Navigate to your account settings or profile settings in the New Relic interface.

3. Look for the API Keys or API section in your account settings. This is typically located under Account settings or User preferences.

4. If you don't have an API key yet, click Create API Key or Generate API Key to create a new API key.

5. Configure your API key settings:

   • Enter a name or description for the API key (e.g., "Nexla Integration")
   • Select the key type (User API key or License key)
   • Review and select the permissions or scopes for the key

6. Click Create or Generate to create the API key.

7. Copy the API key immediately after it's generated, as it may not be accessible again after you navigate away from the page.

8. Identify your root URL based on your New Relic instance:

   • US Instance: https://api.newrelic.com/v2
   • EU Instance: https://api.eu.newrelic.com/v2

9. Store both the API key and root URL securely, as you will need them to configure your Nexla credential. The API key is sensitive information and should be kept confidential.

The API key is sent in the x-api-key header for all API requests to the New Relic API. The root URL determines which New Relic instance (US or EU) your API requests will be sent to. The API key authenticates your requests and grants access to New Relic resources based on your account permissions and the key's scopes. If your API key is compromised, you should immediately revoke it in your New Relic account settings and generate a new one. For detailed information about obtaining API keys, API authentication, and available endpoints, refer to the New Relic REST API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key Value	Yes	Yes
Root URL	Yes	No	Root URL for your New Relic API instance (EU or US). Allowed values: US Instance (API v2) (https://api.newrelic.com/v2); EU Instance (API v2) (https://api.eu.newrelic.com/v2)

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – New Relic

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your New Relic API key in the API Key Value field. This is the API key you obtained from your New Relic account settings (API Keys section). The API key is sent in the x-api-key header for all API requests to the New Relic API. The API key is sensitive information and must be kept confidential.

4. Enter your New Relic root URL in the Root URL field. This should be the root URL for your New Relic API instance. Select US Instance (API v2) (https://api.newrelic.com/v2) for US accounts, or EU Instance (API v2) (https://api.eu.newrelic.com/v2) for EU accounts. The root URL determines which New Relic instance your API requests will be sent to.

   Your New Relic API key can be found in your New Relic account settings under the API Keys section. The API key is sent in the x-api-key header for all API requests to the New Relic API. The root URL should match your New Relic instance (US or EU).

   If your API key is compromised, you should immediately revoke it in your New Relic account settings and generate a new one. The API key provides access to your New Relic account data and should be treated as sensitive information. Keep your API key secure and do not share it publicly.

   For detailed information about obtaining API keys, API authentication, and available endpoints, see the New Relic REST API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the New Relic connector tile from the list of available connectors, then select the credential that will be used to connect to your New Relic account, and click Next; or, create a new New Relic credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common New Relic endpoints. Each template is designed specifically for the corresponding New Relic endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get all account users

This endpoint template retrieves all account users from your New Relic account. Use this template when you need to retrieve user information, user roles, or account access details for your New Relic account.

• This endpoint automatically retrieves all account users from your New Relic account. No additional configuration is required beyond selecting this endpoint template.

This endpoint returns all users associated with your New Relic account, including user details, roles, and access information. Use this endpoint to retrieve user information for account management, access control, or user reporting purposes.

For detailed information about user management, API response structures, and available user data, see the New Relic REST API documentation.

Get all applications

This endpoint template retrieves all applications from your New Relic account. Use this template when you need to retrieve application information, application performance metrics, or application configuration details for your New Relic account.

• This endpoint automatically retrieves all applications from your New Relic account. No additional configuration is required beyond selecting this endpoint template.

This endpoint returns all applications associated with your New Relic account, including application details, performance metrics, and configuration information. Use this endpoint to retrieve application information for monitoring, reporting, or application management purposes.

For detailed information about application management, API response structures, and available application data, see the New Relic REST API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

New Relic data sources can also be manually configured to ingest data from any valid New Relic API endpoint not covered by the pre-built templates, including sources that use chained API calls or custom query parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. New Relic API typically uses the GET method.

New Relic API endpoint URLs are built from your root URL (from your credential) plus the API path and any required query parameters, for example https://api.newrelic.com/v2/users.json or https://api.newrelic.com/v2/applications.json. For the Response Data Path, use $.users[*] to extract all users from the users array, or $.applications[*] to extract all applications from the applications array, depending on your endpoint.

Once all of the relevant settings have been configured, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use.

Use as a destination

Click the + icon on the Nexset that will be sent to the New Relic destination, and select the Send to Destination option from the menu. Select the New Relic connector from the list of available destination connectors, then select the credential that will be used to connect to your New Relic account, and click Next; or, create a new New Relic credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common New Relic endpoints. Each template is designed specifically for the corresponding New Relic endpoint, making destination setup easy and efficient. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Add browser apps

This endpoint template creates new browser applications in your New Relic account. Use this template when you need to add browser monitoring applications to track web application performance and user experience metrics.

• This endpoint automatically creates browser applications from your data. No additional configuration is required beyond selecting this endpoint template. The request body should contain the browser application data in JSON format.

This endpoint sends data as JSON in the request body to create new browser applications in your New Relic account. The request body should contain the browser application configuration data, including application name, settings, and other configuration options.

For detailed information about creating browser applications, request body formats, and available configuration options, see the New Relic REST API documentation.

Generate infrastructure condition

This endpoint template creates new infrastructure alert conditions in your New Relic account. Use this template when you need to set up infrastructure monitoring conditions to track system health and trigger alerts based on infrastructure metrics.

• This endpoint automatically creates infrastructure conditions from your data. No additional configuration is required beyond selecting this endpoint template. The request body should contain the infrastructure condition data in JSON format.

This endpoint sends data as JSON in the request body to create new infrastructure alert conditions in your New Relic account. The request body should contain the infrastructure condition configuration data, including condition name, thresholds, and alert settings.

For detailed information about creating infrastructure conditions, request body formats, and available configuration options, see the New Relic Infrastructure API documentation.

Manual configuration

New Relic destinations can also be manually configured to send data to any valid New Relic API endpoint not covered by the pre-built templates, allowing Nexla to automatically send the response received from the New Relic API after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks. New Relic API typically uses the POST method with JSON format.

New Relic API endpoint URLs are built from your root URL (from your credential) plus the API path and any required query parameters, for example https://api.newrelic.com/v2/browser_applications.json. Configure the request body as {message.json} to send the entire Nexset record as JSON, or construct a custom JSON structure with specific field mappings that matches the New Relic API's expected format for the endpoint you're using.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured New Relic endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the New Relic endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.