Change Management
40 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.
40 extensions
5474 occurrences
8 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-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-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-deprecatedMessage | `x-deprecatedMessage` appears on schema objects and properties. Its value is a string. Used by 5 providers across 18 OpenAPI documents. Observed values include `Use `storedPaymentMethodId` instead.`, | 491 | 5 |
| 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-deprecated | `x-deprecated` appears on schema objects and properties. Its value is a boolean flag. Used by 15 providers across 19 OpenAPI documents. Consistent with change management — this is inferred from where | 141 | 15 |
|
x-yba-api-since
vendor |
`x-yba-api-since` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. It sits in the `x-yba-` namespace, so its meaning is defined by yba tooling rather | 140 | 1 |
| 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-release | `x-release` appears in the info block. Its value is a string. Used by 98 providers across 106 OpenAPI documents. Observed values include `v4`, `bearer`, `v2`, `s3`. Consistent with change management — | 106 | 98 |
|
x-ms-deprecation
vendor |
`x-ms-deprecation` appears on operations. Its value is a structured object. Used by a single provider across 6 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tool | 104 | 1 |
| x-sunset | `x-sunset` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `2027-07-01`, `2025-09-30`, `2026-01-22`, `2027-02-04`. Consistent with | 58 | 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-since | `x-since` appears on schema objects and properties. Its value is a number. Used by 2 providers across 6 OpenAPI documents. Observed values include `20.14`, `24.2`, `22.7`, `20.15`. Consistent with cha | 36 | 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-xgen-changelog
vendor |
`x-xgen-changelog` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-xgen-` namespace, so its meaning is defined by xgen t | 23 | 1 |
| 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-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-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-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-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-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 `os selection not supported by proxy prov | 3 | 2 |
| 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-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-lifecycle | `x-lifecycle` appears in the info block. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. Consistent with change management — this is inferred from where the key appea | 2 | 2 |
|
x-speakeasy-deprecation-message
vendor |
`x-speakeasy-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-speakeasy-` 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-note | `x-deprecation-note` 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 t | 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-enumDeprecated | `x-enumDeprecated` 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 inferred | 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-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-okta-lifecycle
vendor |
`x-okta-lifecycle` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-okta-` namespace, so its meaning i | 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 |
Work with this as data
Every extension here is available over the APIs.io API and to AI agents over MCP. OpenAPI Extensions is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for openapi extensions
3 MCP tools reach this
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
Search the catalog
curl "https://apis.io/api/v1/search?q=change-management&limit=10"
Everything under a tag
curl "https://apis.io/api/v1/tags/change-management"Discovery needs no key. Ratings and market analysis are Pro.