Elastic Observability opentelemetry intake API
The OpenTelemetry intake API uses the OpenTelemetry Protocol (OTLP) to send traces, metrics, and logs to APM Server. OTLP is the default transfer protocol for OpenTelemetry and is supported natively by APM Server. APM Server supports two OTLP communication protocols on the same port: OTLP/HTTP (protobuf) and OTLP/gRPC.
Elastic Observability opentelemetry intake API is one of 5 APIs that Elastic Observability publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include opentelemetry intake. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 6 operations across 6 paths. It is described by OpenAPI 3.2.0, at version 0.1.
Requests are made against a single base URL, /.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Elastic Observability opentelemetry intake API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as Authorization (apiKeyAuth).
It accepts HTTP bearer tokens (Secret token) (secretToken).
By default, every request must be authenticated.
apiKeyAuth— e.g. Authorization: ApiKey base64AccessApiKey
Paths & Operations 6
Across 6 paths, the API surfaces 6 operations — 6 POST. Each is listed below with its method, path, parameters, and response codes.
The OpenTelemetry intake API uses the OpenTelemetry Protocol (OTLP) to send traces, metrics, and logs to APM Server. OTLP is the default transfer protocol for OpenTelemetry and is…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Elastic Observability 4
Other APIs Elastic Observability publishes across the network.
This is an independent, third-party profile of Elastic Observability opentelemetry intake 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.