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).
To get started with API keys:
- Sign up for your free account if you haven't already
- Use our agents and integrations to begin ingesting data into New Relic
- Create and manage your API keys from the API keys UI page so you can start observing your data right away
- Use NerdGraph explorer to view and create user keys
- Use our NerdGraph API for a programmatic way to manage license keys, browser keys, and user keys
The account ID is another identifying number often required for reporting data to New Relic.
You can also copy existing API keys from the API keys UI page. Here are some details about the language used in the UI:
- Copy key versus Copy key ID: The first option copies the value of the key itself. In almost all cases, you'll use that. The second option copies the ID of the key, which is sometimes needed for referencing the key object via API.
- Copy truncated key: This option is available for keys that are not yours. It copies only a few digits from the key, which can be useful for your internal tracking of keys, or for talking with support.
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 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 the :
- Instruct your team members to keep their user keys secure.
- When members leave your organization, remove them from New Relic.
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.