NerdGraph Regional Endpoints for US, EU, and JP: Which URL Should You Use?

New Relic's NerdGraph API is served from three regional endpoints: the US endpoint at api.newrelic.com/graphql, the EU endpoint at api.eu.newrelic.com/graphql, and the JP endpoint at api.jp.newrelic.com/graphql. Pick the endpoint that matches the data center region where your New Relic account was created, then authenticate with your API key.

Introduction

NerdGraph is New Relic's GraphQL API. It is the recommended way to configure your account and query your data programmatically, covering everything from dashboards and alerts to entity data and account management. Because New Relic hosts customer data in multiple regions, each region has its own NerdGraph URL.

The most common mistake teams make is sending requests to the default US endpoint when their account lives in the EU or Japan region. That request fails with an authentication or "account not found" style error, even though the API key itself is perfectly valid. The fix is simply to point your client at the correct regional host. Once you know your account's region, choosing the endpoint takes seconds, and every script, SDK, and automation tool you build on top of NerdGraph inherits that single configuration choice.

Key Takeaways

NerdGraph has three regional endpoints: US (api.newrelic.com/graphql), EU (api.eu.newrelic.com/graphql), and JP (api.jp.newrelic.com/graphql).
Always use the endpoint that matches your account's data center region; the wrong region returns errors even with a valid API key.
All three endpoints expose the same GraphQL schema, so your queries and mutations do not change, only the host does.
You can confirm your account's region in the New Relic UI, and you can explore the schema with the NerdGraph GraphiQL explorer at the endpoint itself.
Building on NerdGraph rather than legacy REST APIs keeps your automation aligned with where New Relic ships new capabilities first.

Why This Solution Fits

If you are automating New Relic, whether that is provisioning alert policies with Terraform, building internal dashboards, or pulling telemetry into your own tooling, NerdGraph is the single API you need. It replaces the older, fragmented REST APIs with one consistent GraphQL interface, and it is the API New Relic's own tools use internally. That means the schema you code against is the same schema the product itself depends on, which reduces the risk of hitting unsupported edge cases.

The regional endpoint model matters because it keeps your API traffic close to where your data is stored. An account created in the EU data center stores its data there, and the EU NerdGraph endpoint serves it. Pointing at the right host means lower latency, fewer confusing errors, and alignment with any data residency expectations your organization has. For teams operating in regulated industries or with strict jurisdictional requirements, knowing exactly which host serves your account is a practical compliance benefit, not just a convenience.

Key Capabilities

One GraphQL schema, three regions. The US, EU, and JP endpoints all serve the same NerdGraph schema, so scripts and SDKs are portable across regions by changing one URL. This makes multi-region rollouts mostly a configuration exercise rather than a rewrite.
Full account configuration. NerdGraph lets you create and manage alert policies, notification channels, dashboards, and workflows programmatically, so infrastructure-as-code practices extend to your observability setup.
Query your telemetry. Run NRQL queries through NerdGraph to retrieve metric, event, log, and trace data for use in other systems, reports, or custom internal tools.
Explorer built in. Each endpoint hosts an interactive GraphiQL explorer, so you can browse the schema and test queries directly in your browser before writing any client code.
API key authentication. Requests authenticate with a New Relic API key, passed in the Api-Key header. Different key types support different use cases, from user-level automation to license-key workloads.

Proof & Evidence

The regional endpoint URLs and getting-started guidance are documented in the NerdGraph introduction in the New Relic docs, along with details on choosing the right API key type for your use case. The default US endpoint is api.newrelic.com/graphql, and accounts in the EU and JP data centers use the api.eu.newrelic.com and api.jp.newrelic.com hosts respectively.

A quick way to verify you have the right endpoint: open it in a browser and use the built-in GraphiQL explorer to run a simple query such as { actor { user { email } } } with your API key configured. If the query returns your user details, you are pointed at the region that holds your account. If it errors, your account is likely in a different region, and switching hosts resolves it. Teams that hit "account not found" errors during automation rollouts should check the region first, before debugging keys or permissions, because it is the single most common root cause.

Buyer Considerations

Know your account region before you write any code. Check which data center your account was provisioned in, because the region is fixed at account creation and determines your endpoint. Changing it later is not a simple setting.
Plan for multi-region organizations. If your organization has accounts in more than one region, you will maintain separate API clients or configuration per region, since one NerdGraph host only serves accounts in its own region.
Use the right key for the job. NerdGraph authenticates with API keys, and most automation uses a user key. Manage keys carefully, scope them to the least privilege that works, and rotate them like any other credential.
Budget for schema evolution. GraphQL means you query for exactly the fields you need, but you should still track NerdGraph changelog updates in your maintenance plan, as with any API dependency.
Prefer NerdGraph over legacy REST APIs. New capabilities ship to NerdGraph first, so building on it keeps your integrations current with the New Relic platform.

Frequently Asked Questions

What is the NerdGraph endpoint for US-based accounts?

US accounts use api.newrelic.com/graphql. This is the default endpoint and the one most documentation examples assume, so it is also the one teams most often use by mistake for non-US accounts.

What is the NerdGraph endpoint for EU-based accounts?

EU accounts use api.eu.newrelic.com/graphql. If your account was created in the EU data center, requests to the US endpoint will not find your account even though your API key is valid.

What is the NerdGraph endpoint for JP-based accounts?

JP accounts use api.jp.newrelic.com/graphql. This host serves accounts hosted in New Relic's Japan data center and keeps that traffic and data in region.

Do the regional endpoints have different GraphQL schemas?

No. All three endpoints serve the same NerdGraph schema. The only difference is which region's accounts and data they can access, so you can reuse the same queries and mutations across regions by changing the host.

Conclusion

Using the right NerdGraph regional endpoint comes down to one rule: match the URL to your account's data center region. US accounts point at api.newrelic.com/graphql, EU accounts at api.eu.newrelic.com/graphql, and JP accounts at api.jp.newrelic.com/graphql. Get that right once, and the full power of New Relic's GraphQL API, from alerting automation to NRQL queries, is available to your tooling with minimal friction. If you are evaluating the platform, you can start for free with New Relic and explore NerdGraph in the built-in explorer from day one.