Data & schema semantics

x-konfig-single-parameter-schema

`x-konfig-single-parameter-schema` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-konfig-` namespace, so its meaning is defined by konfig tooling rather than by OpenAPI. Observed values include `konfig-generated-schema-single-parameter-schema-get--performance-goals-quarterly`, `konfig-generated-schema-single-parameter-schema-get--employees`, `konfig-generated-schema-single-parameter-schema-post--employees`, `konfig-generated-schema-single-parameter-schema-get--employees-id`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics x-konfig- namespace derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
53 occurrences
1 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 53

What its value looks like

Value shapeOccurrences
string53

Observed values

Sampled from the specifications, most frequent first.

konfig-generated-schema-single-parameter-schema-get--performance-goals-quarterlykonfig-generated-schema-single-parameter-schema-get--employeeskonfig-generated-schema-single-parameter-schema-post--employeeskonfig-generated-schema-single-parameter-schema-get--employees-idkonfig-generated-schema-single-parameter-schema-put--employees-idkonfig-generated-schema-single-parameter-schema-get--employees-id-custom-fieldskonfig-generated-schema-single-parameter-schema-put--employees-id-custom-fields-konfig-generated-schema-single-parameter-schema-post--employees-id-terminations

Providers publishing it

All 1.

sage-hr

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the data & schema semantics job.