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

SigNoz fields API

The fields API from SigNoz — 2 operation(s) for fields.

SigNoz fields API is one of 29 APIs that SigNoz publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Fields. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a GitHub repository, pricing, and a getting-started guide.

This API exposes 2 operations across 2 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://{host}:{port}{base_path}.

2 operations 2 paths 11 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{host}:{port}
Authentication
API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

SigNoz fields API declares 2 security schemes for authenticating requests. An API key is passed in the header as SigNoz-Api-Key (api_key). It accepts HTTP bearer tokens (Tokenizer) (tokenizer).

  • api_key — API Keys
  • tokenizer — Tokens generated by the tokenizer

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

fields 2
GET
/api/v1/fields/keys
Get field keys
GetFieldsKeys 10 params → 200401403500
GET
/api/v1/fields/values
Get field values
GetFieldsValues 12 params → 200401403500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are TelemetrytypesTelemetryFieldKey (6 properties), ErrorsJSON (4 properties), TelemetrytypesTelemetryFieldValues (4 properties), RenderErrorResponse (2 properties). Each schema is shown below with its type and property counts.

TelemetrytypesFieldContext
string
RenderErrorResponse
object
2 properties 2 required
ErrorsResponseerroradditional
object
1 property
TelemetrytypesSignal
string
TelemetrytypesGettableFieldValues
object
2 properties 2 required
TelemetrytypesTelemetryFieldValues
object
4 properties
ErrorsJSON
object
4 properties 2 required
TelemetrytypesFieldDataType
string
TelemetrytypesSource
string
TelemetrytypesGettableFieldKeys
object
2 properties 2 required
TelemetrytypesTelemetryFieldKey
object
6 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

signoz-fields-api-openapi.yml Raw ↑

Other APIs SigNoz publishes across the network.

SigNoz alerts API
SigNoz authdomains API
SigNoz authz API
SigNoz channels API
SigNoz cloudintegration API
SigNoz dashboard API
SigNoz downtimeschedules API
SigNoz features API
SigNoz gateway API
SigNoz global API
SigNoz health API
SigNoz inframonitoring API
Where this information came from

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