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

OpenTelemetry Traces API

The Traces API from OpenTelemetry — 1 operation(s) for traces.

OpenTelemetry Traces API is one of 6 APIs that OpenTelemetry publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Traces. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, a JSON-LD context, an API reference, a getting-started guide, and 1 JSON Schema.

This API exposes 1 operation across 1 path, and defines 14 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, http://localhost:4318.

1 operations 1 paths 14 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Server
http://localhost:4318
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

OpenTelemetry Traces API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth).

  • bearerAuth — Bearer token authentication for secured OTLP endpoints

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
POST
/v1/traces
OpenTelemetry Export trace data
exportTraces body → 200400429503

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Span (16 properties), AnyValue (7 properties), SpanLink (6 properties), InstrumentationScope (4 properties). Each schema is shown below with its type and property counts.

ScopeSpans
object
Spans associated with an instrumentation scope
3 properties
InstrumentationScope
object
Metadata about the instrumentation library or component that produced the telemetry data.
4 properties
ExportTraceServiceResponse
object
Response message for the trace export service
1 property
ExportTraceServiceRequest
object
Request message for the trace export service
1 property
Span
object
A span represents a single operation within a trace. Spans can be nested to form a trace tree. Each span has a name, timing data, structured log messages (even…
16 properties 6 required
Resource
object
Describes the entity producing telemetry. A resource has attributes such as service.name, service.version, host.name, and other identifying metadata.
2 properties
SpanEvent
object
A timed event within a span
4 properties
AnyValue
object
A polymorphic value container that can hold string, bool, int, double, array, or key-value list values.
7 properties
ResourceSpans
object
Collection of spans from a resource
3 properties
ExportTracePartialSuccess
object
Indicates partial success when some spans were rejected
2 properties
Status
object
Error status response
2 properties
KeyValue
object
A key-value pair for attributes
2 properties 2 required
SpanLink
object
A reference from one span to another
6 properties
SpanStatus
object
Status of the span
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opentelemetry-traces-api-openapi.yml Raw ↑

Other APIs OpenTelemetry publishes across the network.

OpenTelemetry Protocol (OTLP) gRPC API
OpenTelemetry Collector API
OpenTelemetry SDK API
OpenTelemetry Logs API
OpenTelemetry Metrics API
Where this information came from

This is an independent, third-party profile of OpenTelemetry 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.