How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

New Relic Traces API

Distributed trace span ingestion

New Relic Traces API is one of 19 APIs that New Relic publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 111 JSON Schema definitions.

Tagged areas include Traces. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, a JSON-LD context, rate-limit docs, and 111 JSON Schemas.

This API exposes 1 operation across 1 path, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against 2 base URLs: https://trace-api.newrelic.com, https://trace-api.eu.newrelic.com.

1 operations 1 paths 8 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.newrelic.com/v2/
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

New Relic Traces API declares 1 security scheme for authenticating requests. An API key is passed in the header as Api-Key (apiKey). By default, every request must be authenticated.

  • apiKey — New Relic License Key or Ingest API Key

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Traces 1

Distributed trace span ingestion

POST
/trace/v1
New Relic Send Trace Spans
sendTraces 4 params body → 202400403413429

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ZipkinSpan (11 properties), Span (4 properties), SpanBatch (2 properties), ErrorResponse (2 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
2 properties
ZipkinTracePayload
array
Zipkin JSON v2 format trace payload
ZipkinSpan
object
A single span in Zipkin JSON v2 format
11 properties 2 required
CommonBlock
object
Shared attributes applied to all spans in this batch
1 property
AcceptedResponse
object
1 property
NewRelicTracePayload
array
New Relic format trace payload — array of span batch objects
SpanBatch
object
A batch of spans with optional shared attributes
2 properties 1 required
Span
object
A single distributed trace span in New Relic format
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

new-relic-traces-api-openapi.yml Raw ↑

Other APIs New Relic publishes across the network.

New Relic NerdGraph API
New Relic Alerts API
New Relic Synthetics API
New Relic Infrastructure Alerts API
New Relic Browser API
New Relic Partnership API
New Relic Telemetry SDKs
New Relic OpenTelemetry OTLP Endpoint
New Relic Control
New Relic NRQL Lookups API
New Relic Security Data API
New Relic Mobile SDK
Where this information came from

This is an independent, third-party profile of New Relic Traces API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.