Integrate Postman with New Relic
Postman offers two New Relic integrations that you can set up independently depending on your needs.
New Relic is an application performance management solution to monitor real-time and trending data for your processes or web apps. Use Postman’s New Relic integration to send Postman Monitor results to New Relic.
You can also add New Relic to Postman Context Graph to provide observability data (read access) to your agent.
Add New Relic to Postman Context Graph
Connecting New Relic to Postman Context Graph brings production telemetry into the graph as telemetry nodes. This is separate from the monitor integration described in the rest of this topic, and it uses a different kind of key: a New Relic User key instead of an ingest license key.
Get a New Relic User key
In New Relic, create or copy a User key. A User key starts with NRAK. Postman connects every New Relic account that the key can see, so use a key whose access matches what you want in the graph.
For more information about key types, see the New Relic API keys documentation.
Connect New Relic
To connect New Relic to Context Graph, do the following:
- Go to
Home > Agent Context.
- Click Manage Data Sources. New Relic is listed under Connected sources.
- Next to New Relic, click Connect.
- Enter your New Relic User key in User key.
- Select the Region for your New Relic account, US or EU.
- Click Connect & index.
Postman saves the key for your whole team. If your team already has a saved key, Postman asks whether you want to replace it.
Indexing runs as a background job. You can keep using the graph while it runs, but results might be incomplete until indexing finishes.
Retrieve your New Relic Ingest License key
Setting up a New Relic monitor integration requires you to get an API key (referred to as an ingest license key) from New Relic and configure your Postman monitors. After you set up the integration, you can view real-time alerts based on the results of your monitors. To retrieve your ingest license key from New Relic, do the following:
- Sign in to New Relic.
- The first time you sign up for New Relic with a single account, an organization with its own license key are created. To access your ingest license key, click your avatar in the top right, copy your license key, and save it in a secure location outside New Relic. Once you’ve copied your license key the first time, you won’t be able to copy the key again as New Relic has removed the ability to copy API keys from the UI.
There are different types of API keys in New Relic. Use an ingest license key for Postman Monitor integration. For more information on API Keys in New Relic, see the New Relic API keys documentation.
Configure the New Relic integration
- From the Postman Home page, click Integrations.
- Select New Relic, then click Add Integration.
- Enter a Nickname for the integration.
- Select the workspace with the monitor you want to use.
- Select the monitor you want to use.
- For New Relic API Key, enter the ingest license key you copied from New Relic.
- Select a New Relic region. New Relic offers the US and EU region instances. See the New Relic data center documentation for more information.
- Click Add Integration.
You can view your configured integrations on the Integrations page. Configured integrations have a green dot in the upper right corner of the tile.
Connect New Relic from a monitor
You can also connect New Relic when you create a monitor or edit an existing one. You don’t need to choose a workspace or monitor, because the integration is for that monitor.
To connect New Relic from a monitor, do the following:
-
Open the monitor’s create or edit page.
-
Click Send updates to. Under Observability, click New Relic.
-
In the Connect New Relic dialog, enter the following:
- Integration name - A name for the integration. By default, the name is the monitor’s name followed by ”- New Relic Integration”.
- API key - Enter the ingest license key you copied from New Relic.
- Region - Select US (.com) or EU (.eu).
-
Click Connect.
Visualize your data with the Postman quickstart
New Relic I/O (Instant Observability) has integrations that bundle observability tools to help you get started with monitoring your stack. The Postman quickstart provides you with an out-of-the-box dashboard with a suggested view for API monitoring.
To visualize your data with the Postman quickstart, do the following:
- Install the Postman quickstart in New Relic I/O.
- If you don’t have a New Relic account, follow the sign up instructions to get started for free. Check your email for a link to continue to the next step.
- Select an account, then click Begin installation.
- Under Postman (manual install) click Done if you’ve already completed the steps in the Configure New Relic integration section.
- Click See your data.
- You can visualize your Postman API data on the New Relic dashboard.

Manually view and query data in New Relic
When your monitor runs, Postman starts sending metrics data to New Relic. Once the data is present in New Relic, you can query and display metrics.
In New Relic, click Metrics and Events and then click Metrics. To view Postman Monitor results, search for metrics that begin with “postman”. You can create queries to customize the graph displayed. New Relic also has a query builder to help you construct advanced searches.
You can add one or more charts to a dashboard, tracking key metrics over time. For more information, see the New Relic dashboard documentation.
Metrics pushed to New Relic
Postman pushes the following metrics and their values to New Relic. Run-level metrics are valid for the entire run (for example, the number of errors). Request-level metrics send data for each request in the collection used by the monitor. You can filter for each specific request using the dimensions passed along with the metric.
Dimension attributes
You can use several attributes as dimensions when viewing metrics in New Relic. For example, add monitor.name or user.name to show separate lines for the monitor or user in the graph. The following example pivots latency data with regions:

You can use the following attributes as dimensions:
regionrun.idcollection.idcollection.namemonitor.idmonitor.nameenvironment.idenvironment.namerequest.idrequest.nameuser.iduser.name