• /
  • EnglishEspañol日本語한국어Português
  • Log inStart now

New Relic API keys

Our monitoring solutions and APIs use API keys to authenticate and verify your identity. These keys allow only approved people in your organization to report data to New Relic, access that data, and configure features. The primary keys are the license key (for reporting data) and the (for working with NerdGraph, our GraphQL API).

Screenshot of the API keys UI

To get started with API keys:

  1. Sign up for your free account if you haven't already
  2. Use our agents and integrations to begin ingesting data into New Relic
  3. Create and manage your API keys from the API keys UI page so you can start observing your data right away

Our main API keys

Key

Details

To view and manage

Read more

License key, used for data ingest

License keys are used to report almost all data (except for browser and mobile data, which use their own keys). Each key is tied to a specific account and you can create as many as you want.

Go to the API keys UI (direct link)

Learn more

Browser key, used for data ingest

Browser keys are used to report browser monitoring data. Each key is tied to a specific account, and you can create as many as you want.

Go to the API keys UI (direct link)

Learn more

Mobile app token, used for data ingest

Mobile app tokens are used to report mobile monitoring data. Each token is tied to a specific mobile app.

Go to a monitored app's UI

Learn more

User key, used for querying and configuration

A user key is required to use NerdGraph, our GraphQL API, which is used for querying data and configuring features. Each user key is tied to a specific user.

Go to the API keys UI (direct link)

Learn more

View and manage API keys

You can manage most API keys from the API keys UI page located in the user menu when you click API keys.

To view a key in NerdGraph, copy the key ID. You can also use NerdGraph to manage keys

Recommendations for managing API keys

If your API keys get into the wrong hands, it can present a security risk. For example:

  • Someone with your could send arbitrary data to your account.
  • Someone with one of your team member's user keys could view your New Relic data and make changes to your New Relic account.

You should treat your API keys securely, as you would passwords and other sensitive information. Some recommendations:

  • For the license key and the browser key, consider implementing a key rotation strategy: creating new keys and deleting old ones on a set schedule. Considerations:
    • You can't delete the original ingest keys associated with an account, so we recommend creating additional ingest keys that you can later delete. This ensures you're assuming a strong security posture.
    • Note that this doesn't apply to the mobile app token; you can't delete a token or create additional tokens.
  • For the :
    • Instruct your team members to keep their user keys secure.
    • When members leave your organization, remove their user IDs from New Relic. This disables all the user keys associated with their user ID.

Rotate API keys

Here's how to rotate each of our four most common API keys:

We also have several older or less common API key type. To rotate these keys:

Read more about our API keys

To create or manage API keys, use the UI at one.newrelic.com/launcher/api-keys-ui.api-keys-launcher, or our NerdGraph API. For more details, select a key:

Besides the main API keys explained above, we have several other, older API keys that some New Relic customers still use. If you don't already use these keys, you likely don't need to start.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.