New Relic is now retiring the REST API keys to improve security and reliability. You must update your systems with the new User keys to avoid service disruptions.
The current REST API keys used to access REST API v2 (api.newrelic.com/v2 or api.eu.newrelic.com/v2) will be retired. This change addresses the limitations of the existing account-level keys and aligns with industry best practices.
If your systems or integrations call these specified API end-points using the REST API keys, you must replace them with new User API keys by March 1, 2025, to avoid service disruptions. Failure to update may result in API call failures and errors, also potentially disrupting workflows.
You must complete replacement of the REST API keys by March 1, 2025.
To get started
This change requires you to rotate your API key.
You must do the following:
- Generate new keys: Use the New Relic UI or NerdGraph API.
- Update systems: Replace old keys with new User API keys in your systems.
- Validate: Ensure all API integrations work with the new User keys.
- Remove old keys: Delete old keys once validated.
Rotate API key
To rotate API keys in UI:
- Go to New Relic UI and determine which account you need a key for.
- Create new User API keys associated to that account.
- Update your systems to use the new User API keys. Go to one.newrelic.com/api-keys or one.eu.newrelic.com/api-keys for EU data center and refer to the create and update instructions here.
- Ensure your API integrations function/work correctly with the new keys. This requires updating any scripts or code that reference the old key to use the new key value.
- Once validated, remove the old REST API keys. After the old key is deleted, it cannot be restored.
You can also manage User keys via our NerdGraph API. For instructions, refer to NerdGraph tutorial Manage API keys.
Additional key points
- If you’re using multiple New Relic accounts, each one will have its own REST API key. Each REST API key must be replaced individually with a User API key which is generated in the corresponding account.
- If your API key starts with
NRAK, no update is required.
Contact support
Our support team is here to assist you during this transition. If you have any questions about these changes, please contact Support.
For more information on how to view and manage API Keys in New Relic, click here.