Data & schema semantics

x-konfig-generated-schema

`x-konfig-generated-schema` appears on schema objects and properties. 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-components-schemas-EmployeeListActiveEmployeesResponse-p`, `konfig-generated-schema-components-schemas-LeaveManagementGetTimeOffPolicyByIdRe`, `konfig-generated-schema-components-schemas-EmployeeGetByIdResponse-properties-da`, `konfig-generated-schema-components-schemas-RecruitmentGetPositionDetailsResponse`. 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.
600 occurrences
1 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
schema 599
operation 1

What its value looks like

Value shapeOccurrences
string600

Observed values

Sampled from the specifications, most frequent first.

konfig-generated-schema-components-schemas-EmployeeListActiveEmployeesResponse-pkonfig-generated-schema-components-schemas-LeaveManagementGetTimeOffPolicyByIdRekonfig-generated-schema-components-schemas-EmployeeGetByIdResponse-properties-dakonfig-generated-schema-components-schemas-RecruitmentGetPositionDetailsResponsekonfig-generated-schema-components-schemas-RecruitmentListPositionsResponse-propkonfig-generated-schema-components-schemas-LeaveManagementListTimeOffRequestsReskonfig-generated-schema-components-schemas-RecruitmentGetApplicantDetailsResponskonfig-generated-schema-components-schemas-EmployeeUpdateByIdRequest-properties-

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.