New Relic Gateway API
✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey3 EndpointsREST
For Agents
Send OTLP-format metrics, traces, and logs to New Relic via the Gateway endpoints. Useful for migrating telemetry from Datadog, Dynatrace, or other observability platforms.
Use for: I want to send metrics from Datadog into New Relic, Forward OpenTelemetry traces to New Relic, Migrate logs from Splunk to New Relic, Set up a dual-write pipeline for metrics during an observability migration
Not supported: Does not handle dashboard creation, NRQL queries, alerting rules, or APM agent installation — use for OTLP metric, trace, and log ingest only.
The New Relic Gateway API ingests metrics, traces, and logs into New Relic using OTLP-format payloads. It is purpose-built for migrating telemetry from other observability platforms — Datadog, Dynatrace, Splunk, and similar — by exposing dedicated /gateway/v1/metrics, /gateway/v1/traces, and /gateway/v1/logs endpoints. Authentication uses an api-key header tied to a New Relic Ingest license key, and payloads follow the OpenTelemetry Protocol over HTTP/JSON.
Install Jentic One Beta
Connect the New Relic Gateway API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the New Relic Gateway API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with New Relic Gateway API.
Ingest OTLP-format metric payloads via POST /gateway/v1/metrics for migration from Datadog or Dynatrace
Forward distributed trace spans through POST /gateway/v1/traces using OpenTelemetry Protocol
Stream application and infrastructure logs into New Relic via POST /gateway/v1/logs
Authenticate ingest workloads with an api-key header bound to a specific New Relic ingest license
Bridge multi-vendor observability stacks during a phased move onto the New Relic platform
Use Cases
Patterns agents use New Relic Gateway API for, with concrete tasks.
★ Datadog-to-New-Relic Metric Migration
Platform teams migrating from Datadog use the Gateway API to dual-write metrics into New Relic during a transition window. POST /gateway/v1/metrics accepts OTLP-format payloads with the api-key header so existing OpenTelemetry collectors can be repointed at otlp.nr-data.net without rewriting instrumentation. Once dashboards are validated in New Relic, the Datadog write path is shut down.
Forward an OTLP metric payload containing a counter named requests.total to POST /gateway/v1/metrics using the configured ingest license key
Distributed Trace Forwarding
Teams running OpenTelemetry collectors send trace spans to New Relic via POST /gateway/v1/traces. Because the endpoint speaks OTLP, the same collector configuration that pointed at another vendor can be retargeted by changing the endpoint URL and api-key header. This avoids re-instrumenting services during an observability platform change.
Forward a 50-span OTLP trace export to POST /gateway/v1/traces and confirm the response indicates ingest success
Log Pipeline Consolidation
Operations teams consolidating multiple log backends into New Relic use POST /gateway/v1/logs to push OTLP-formatted log records. The Gateway endpoint is designed for high-volume ingest, so log shippers like Fluent Bit or the OpenTelemetry Collector can stream records directly without an intermediate aggregator. Logs land in New Relic Logs and can be queried with NRQL alongside metrics and traces.
Send an OTLP log record with severity ERROR and message body 'database connection timeout' to POST /gateway/v1/logs
Agent-Driven Telemetry Validation
An AI agent uses the Gateway API through Jentic to validate ingest pipelines after a configuration change. The agent sends a synthetic OTLP payload to each of the three endpoints, checks the response status, and reports back to the human operator whether the api-key, endpoint URL, and payload format are all configured correctly.
Send a synthetic metric, trace, and log payload to the three Gateway endpoints and report which calls returned a successful status
Key Endpoints
3 endpoints — the new relic gateway api ingests metrics, traces, and logs into new relic using otlp-format payloads.
METHOD
PATH
DESCRIPTION
POST
/gateway/v1/metrics
Ingest OTLP-format metrics into New Relic
POST
/gateway/v1/traces
Ingest OTLP-format trace spans into New Relic
POST
/gateway/v1/logs
Ingest OTLP-format log records into New Relic
POST
/gateway/v1/metrics
Ingest OTLP-format metrics into New Relic
POST
/gateway/v1/traces
Ingest OTLP-format trace spans into New Relic
POST
/gateway/v1/logs
Ingest OTLP-format log records into New Relic
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
New Relic ingest license keys are stored encrypted in the Jentic vault. Agents receive a scoped credential reference and Jentic injects the api-key header at request time, so the license key never enters the agent's context.
Intent-based discovery
Agents search Jentic for intents like 'send OTLP metrics to new relic' and Jentic returns the POST /gateway/v1/metrics operation with its OTLP schema, so the agent constructs a valid payload without reading the OTLP specification.
Time to first call
Direct integration: 1-2 days to wire an OpenTelemetry collector, configure the api-key header, and validate ingest. Through Jentic: under 30 minutes for one-off pushes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using New Relic Gateway API through Jentic.
What authentication does the New Relic Gateway API use?
The Gateway API uses an api-key header carrying a New Relic ingest license key. Through Jentic the key sits in the encrypted vault and Jentic injects it on the agent's behalf, so the license key never appears in the agent's prompt or response.
Can I forward Datadog metrics to New Relic with the Gateway API?
Yes. The /gateway/v1/metrics endpoint accepts OTLP-format payloads, so any OpenTelemetry collector that previously exported to Datadog can be repointed at otlp.nr-data.net. The collector translates Datadog's native model into OTLP before sending — that conversion happens at the collector, not the Gateway.
What payload format does the New Relic Gateway API accept?
All three endpoints — /gateway/v1/metrics, /gateway/v1/traces, and /gateway/v1/logs — accept OpenTelemetry Protocol (OTLP) over HTTP/JSON. The schemas in the OpenAPI spec describe the OTLP request bodies for each signal type.
How do I send a test log entry through Jentic?
Search Jentic for 'send a log to new relic gateway', load the POST /gateway/v1/logs schema, and execute with an OTLP log record. Jentic injects the api-key header automatically. Get started at https://app.jentic.com/sign-up.
Are the metrics, traces, and logs endpoints rate-limited differently?
The Gateway API is designed for high-volume telemetry ingest and returns 4xx responses when payloads exceed account limits or are malformed. For ingest budgets and per-account caps, consult your New Relic account configuration — the spec itself does not encode account-specific limits.
GET STARTED