• Log inStart now

New Relic API keys

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

If you’re just getting started using New Relic, you don’t need to manually find or input a key: our guided install procedures will automatically include the keys for you. Not yet using New Relic? Set up your New Relic account: it's free, forever!

View and manage API keys

You can view and manage most API keys from the API keys UI page, which is at one.newrelic.com/api-keys (from the account dropdown, click API keys).

From one.newrelic.com/launcher/api-keys-ui.api-keys-launcher, you can create and manage license keys, browser keys, and user keys.

Other ways to create and manage keys:

Get to know 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 monitoring 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

Keep your API keys secure

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

  • Someone with your license key 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 keys associated with an account, so to implement a strong security strategy, you must create additional keys that you can later delete.
    • Note that this doesn't apply to the mobile app token; you can't delete a token or create additional tokens.
  • For user keys:
    • Instruct your team members to keep their user keys secure.
    • When members leave your organization, even if they're basic users, remove them from New Relic.

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:

Other keys

Besides our 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 should have no reason to learn about them.

Account ID

The account ID is another identifying number often required for reporting data to New Relic. See Account ID.

Copyright © 2022 New Relic Inc.

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