Change Management
66 distinct extensions were invented to do this job. Each one is a provider deciding OpenAPI would not carry something and building their own way through. Where a job has many names and few uses each, nobody won — the problem was solved privately, over and over.
66 extensions
8310 occurrences
12 vendor-named
The extensions
| Extension | What it appears to do | Uses | Providers |
|---|---|---|---|
| x-release-status | `x-release-status` appears on schema objects and properties. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `PUBLIC`, `BETA`, `DEPRECATED`, `testing`. C | 1655 | 2 |
| x-lifecycle-stage | `x-lifecycle-stage` appears on operations and on path items. Its value is a string. Used by 2 providers across 3 OpenAPI documents. Observed values include `General Availability`, `Early Access`, `Pre | 1613 | 2 |
| x-addedInVersion | `x-addedInVersion` appears on schema objects and properties. Its value is a string. Used by a single provider across 18 OpenAPI documents. Observed values include `68`, `2`, `1`, `49`. Consistent with | 1433 | 1 |
| x-deprecated | `x-deprecated` appears on schema objects and properties. Its value is a boolean flag. Used by 22 providers across 66 OpenAPI documents. Consistent with change management — this is inferred from where | 640 | 22 |
| x-release-lifecycle | `x-release-lifecycle` appears on operations and on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `GA`, `EA`, `depre | 619 | 1 |
| x-release | `x-release` appears in the info block. Its value is a string. Used by 101 providers across 374 OpenAPI documents. Observed values include `v4`, `bearer`, `v2`. Consistent with change management — this | 374 | 101 |
| x-deprecatedMessage | `x-deprecatedMessage` appears on schema objects and properties. Its value is a string. Used by 7 providers across 15 OpenAPI documents. Observed values include `Use `storedPaymentMethodId` instead.`, | 275 | 7 |
|
x-yba-api-since
vendor |
`x-yba-api-since` appears on operations. Its value is a string. Used by 2 providers across 11 OpenAPI documents. It sits in the `x-yba-` namespace, so its meaning is defined by yba tooling rather than | 209 | 2 |
| x-alternate-versions | `x-alternate-versions` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferred from where the key appears | 195 | 1 |
| x-lifecycle | `x-lifecycle` appears on operations. Its value is a structured object. Used by 4 providers across 11 OpenAPI documents. Consistent with change management — this is inferred from where the key appears | 135 | 4 |
|
x-ms-deprecation
vendor |
`x-ms-deprecation` appears on operations. Its value is a structured object. Used by 2 providers across 9 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling ra | 135 | 2 |
| x-deprecatedInVersion | `x-deprecatedInVersion` appears on schema objects and properties. Its value is a string. Used by a single provider across 5 OpenAPI documents. Observed values include `49`, `68`, `69`, `1`. Consistent | 126 | 1 |
| x-released | `x-released` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferred from where the key appears an | 112 | 1 |
| x-since | `x-since` appears on operations and on schema objects and properties. Its value is a string. Used by 3 providers across 8 OpenAPI documents. Observed values include `20.14`, `2.10.3`, `2.15.3`, `2.16. | 111 | 3 |
| x-sunset | `x-sunset` appears on operations. Its value is a string. Used by 2 providers across 3 OpenAPI documents. Observed values include `2027-07-01`, `2026-01-22`, `2025-09-30`, `2027-02-04`. Consistent with | 97 | 2 |
| x-deprecation-date | `x-deprecation-date` appears on operations. Its value is a string. Used by 3 providers across 3 OpenAPI documents. Observed values include `2022-12-15T00:00:00Z`, `2022-07-13T00:00:00Z`, `2023-06-01`, | 53 | 3 |
|
x-xgen-changelog
vendor |
`x-xgen-changelog` appears on operations. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-xgen-` namespace, so its meaning is defined by xgen | 48 | 1 |
| x-deprecated-alias-of | `x-deprecated-alias-of` appears on schema objects and properties and on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `author`, `creat | 39 | 1 |
|
x-okta-lifecycle
vendor |
`x-okta-lifecycle` appears on operations. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-okta-` namespace, so its meaning is defined by okta | 39 | 1 |
| x-cdp-releases | `x-cdp-releases` appears at the root of the document. Its value is a string. Used by a single provider across 38 OpenAPI documents. Observed values include `PUBLIC`. Consistent with change management | 38 | 1 |
| x-deprecated-at | `x-deprecated-at` appears on operations and on path items. Its value is a string. Used by 2 providers across 3 OpenAPI documents. Observed values include `20240801T00:00:00Z`. Consistent with change m | 33 | 2 |
| x-sunset-at | `x-sunset-at` appears on operations and on path items. Its value is a string. Used by 2 providers across 3 OpenAPI documents. Observed values include `20250228T00:00:00Z`. Consistent with change manag | 33 | 2 |
| x-release-note | `x-release-note` appears in the info block. Its value is a structured object. Used by 4 providers across 31 OpenAPI documents. Consistent with change management — this is inferred from where the key a | 31 | 4 |
|
x-github-release
vendor |
`x-github-release` appears in the info block. Its value is a number. Used by 2 providers across 25 OpenAPI documents. It sits in the `x-github-` namespace, so its meaning is defined by github tooling | 25 | 2 |
| x-cfDeprecation | `x-cfDeprecation` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferred from where the key | 21 | 1 |
| x-deprecation | `x-deprecation` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferred from where the key ap | 21 | 1 |
|
x-openai-enum-deprecations
vendor |
`x-openai-enum-deprecations` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-openai-` namespace, so | 20 | 1 |
| x-deprecated-date | `x-deprecated-date` appears on schema objects and properties. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `2022-11-01`, `2022-10-01`, `2023-01- | 19 | 1 |
| x-revision | `x-revision` appears at the root of the document. Its value is a string. Used by a single provider across 17 OpenAPI documents. Observed values include `3c039d08312e`. Consistent with change managemen | 17 | 1 |
| x-added-in-version | `x-added-in-version` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `1.1`, `1.2`. Consistent with change | 12 | 1 |
| x-discovery-revision | `x-discovery-revision` appears in the info block. Its value is a string. Used by 5 providers across 11 OpenAPI documents. Observed values include `20260812`, `20260731`, `20260810`, `20260825`. Consis | 11 | 5 |
| x-changes | `x-changes` appears on operations. Its value is a list. Used by a single provider across 3 OpenAPI documents. Consistent with change management — this is inferred from where the key appears and what i | 8 | 1 |
| x-venice-deprecated | `x-venice-deprecated` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with change management — this is inferred from where | 8 | 1 |
| x-venice-deprecated-replacement | `x-venice-deprecated-replacement` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with change management — this is inferre | 8 | 1 |
| x-venice-model-deprecation-date | `x-venice-model-deprecation-date` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with change management — this is inferre | 8 | 1 |
| x-venice-model-deprecation-warning | `x-venice-model-deprecation-warning` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with change management — this is infe | 8 | 1 |
| x-changelog | `x-changelog` appears in the info block. Its value is a list. Used by 5 providers across 7 OpenAPI documents. Consistent with change management — this is inferred from where the key appears and what i | 7 | 5 |
| x-enum-deprecated | `x-enum-deprecated` appears on schema objects and properties. Its value is a list. Used by a single provider across 5 OpenAPI documents. Consistent with change management — this is inferred from where | 7 | 1 |
|
x-mux-doc-decorators-deprecated-enum-values
vendor |
`x-mux-doc-decorators-deprecated-enum-values` appears on schema objects and properties. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-mux-` namespace, so | 7 | 1 |
| x-deprecation-reason | `x-deprecation-reason` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `POST /api/v1/export shall be used instead of the curr | 6 | 1 |
|
x-speakeasy-deprecation-message
vendor |
`x-speakeasy-deprecation-message` appears on operations and on schema objects and properties. Its value is a structured object. Used by 2 providers across 3 OpenAPI documents. It sits in the `x-speake | 6 | 2 |
| x-api-lifecycle | `x-api-lifecycle` appears in the info block. Its value is a structured object. Used by a single provider across 5 OpenAPI documents. Consistent with change management — this is inferred from where the | 5 | 1 |
| x-polygon-deprecation | `x-polygon-deprecation` appears on operations. Its value is a structured object. Used by a single provider across 5 OpenAPI documents. Consistent with change management — this is inferred from where t | 5 | 1 |
| x-az-search-deprecated | `x-az-search-deprecated` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferre | 4 | 1 |
| x-deprecated-values | `x-deprecated-values` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferred from where the | 3 | 1 |
| x-deprecation-notice | `x-deprecation-notice` appears on schema objects and properties and in the info block. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `Permissions inclu | 3 | 2 |
| x-altus-releases | `x-altus-releases` appears at the root of the document. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `PUBLIC`. Consistent with change management | 2 | 1 |
| x-deprecated-enum-values | `x-deprecated-enum-values` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `STARTING_FLOW,STOPPED,IMPORTI | 2 | 1 |
| x-deprecated-reason | `x-deprecated-reason` appears on schema objects and properties. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `Batch-level approval steps are no longer | 2 | 2 |
| x-deprecated_message | `x-deprecated_message` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `use `POST /admin/products/imports` instead.`, `use `P | 2 | 1 |
| x-enum-deprecated-date | `x-enum-deprecated-date` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is in | 2 | 1 |
| x-enumDeprecated | `x-enumDeprecated` appears on schema objects and properties. Its value is a list. Used by 2 providers across 2 OpenAPI documents. Consistent with change management — this is inferred from where the ke | 2 | 2 |
| x-lifecycle-policy | `x-lifecycle-policy` appears at the root of the document. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with change management — this is inferred f | 2 | 1 |
|
x-stainless-deprecation-message
vendor |
`x-stainless-deprecation-message` 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-stainless-` namespace, so its | 2 | 1 |
| x-deprecated-by-vendor | `x-deprecated-by-vendor` appears in the info block. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferred from where th | 1 | 1 |
| x-deprecated-notice | `x-deprecated-notice` appears in the info block. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferred from where | 1 | 1 |
| x-deprecation-notes | `x-deprecation-notes` appears in the info block. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferred from where | 1 | 1 |
| x-eg-lifecycle | `x-eg-lifecycle` appears in the info block. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `PLANNED`. Consistent with change management — this is i | 1 | 1 |
|
x-google-discovery-revision
vendor |
`x-google-discovery-revision` appears in the info block. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-google-` namespace, so its meaning is defined by | 1 | 1 |
| x-last-release-date | `x-last-release-date` appears in the info block. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `2022-08-19`. Consistent with change management — t | 1 | 1 |
| x-mandateshield-release | `x-mandateshield-release` appears at the root of the document. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with change management — this is inferr | 1 | 1 |
|
x-ms-containerapp-revision-name
vendor |
`x-ms-containerapp-revision-name` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is | 1 | 1 |
|
x-obmcs-deprecated
vendor |
`x-obmcs-deprecated` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-obmcs-` namespace, so its meaning is | 1 | 1 |
| x-release-stage | `x-release-stage` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `general_availability`. Consistent with | 1 | 1 |
| x-revision-date | `x-revision-date` appears in the info block. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `2026-05-08`. Consistent with change management — this | 1 | 1 |
| x-sdk-deprecation-message | `x-sdk-deprecation-message` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Use llm_api_key_ref instead`. | 1 | 1 |