Data & schema semantics
1950 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.
1950 extensions
336148 occurrences
380 vendor-named
Inside this job
Identity & relationships185
Type system159
Validation & constraints87
Naming & aliasing76
Units & formatting45
Size & shape44
Defaults & examples24
Mutability & access19
Ordering & sorting14
The extensions
| Extension | What it appears to do | Uses | Providers |
|---|---|---|---|
| x-nullable | `x-nullable` appears on schema objects and properties. Its value is a boolean flag. Used by 48 providers across 185 OpenAPI documents. Consistent with type system — this is inferred from where the key | 40972 | 48 |
|
x-microcks-default
vendor |
`x-microcks-default` appears on response objects. Its value is a boolean flag. Used by 266 providers across 972 OpenAPI documents. It sits in the `x-microcks-` namespace, so its meaning is defined by | 25154 | 266 |
|
x-microcks-operation
vendor |
`x-microcks-operation` appears on operations. Its value is a structured object. Used by 400 providers across 1,507 OpenAPI documents. It sits in the `x-microcks-` namespace, so its meaning is defined | 21938 | 400 |
| x-adpParameterData | `x-adpParameterData` appears on operations and on header objects. Its value is a structured object. Used by a single provider across 59 OpenAPI documents. Consistent with data & schema semantics — thi | 12764 | 1 |
| x-cds-type | `x-cds-type` appears on schema objects and properties. Its value is a string. Used by 46 providers across 53 OpenAPI documents. Observed values include `PositiveInteger`, `AmountString`, `URIString`, | 9020 | 46 |
| x-related-resource | `x-related-resource` appears on operations. Its value is a string. Used by 3 providers across 173 OpenAPI documents. Observed values include `#/definitions/WorkRequest`, `#/definitions/AutonomousDatab | 7134 | 3 |
|
x-github
vendor |
`x-github` appears on operations. Its value is a structured object. Used by 3 providers across 39 OpenAPI documents. It sits in the `x-github-` namespace, so its meaning is defined by github tooling r | 6792 | 3 |
|
x-ms-enum
vendor |
`x-ms-enum` appears on schema objects and properties. Its value is a structured object. Used by 12 providers across 580 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined b | 6650 | 12 |
| x-position | `x-position` appears on operations. Its value is an integer. Used by 11 providers across 36 OpenAPI documents. Observed values include `1`, `2`, `3`, `4`. Consistent with ordering & sorting — this is | 6592 | 11 |
| x-default-description | `x-default-description` appears on parameter objects. Its value is a string. Used by 3 providers across 161 OpenAPI documents. Observed values include `null`, `The default value depends upon `sortBy`, | 5066 | 3 |
|
x-obmcs-top-level-enum
vendor |
`x-obmcs-top-level-enum` appears on schema objects and properties. Its value is a string. Used by 3 providers across 131 OpenAPI documents. It sits in the `x-obmcs-` namespace, so its meaning is defin | 4233 | 3 |
|
x-ms-discriminator-value
vendor |
`x-ms-discriminator-value` appears on schema objects and properties. Its value is a string. Used by 4 providers across 198 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is define | 4051 | 4 |
| x-apim-inline | `x-apim-inline` appears on schema objects and properties. Its value is a boolean flag. Used by 6 providers across 68 OpenAPI documents. Consistent with data & schema semantics — this is inferred from | 3912 | 6 |
| x-struct | `x-struct` appears on schema objects and properties. Its value is a string. Used by a single provider across 12 OpenAPI documents. Observed values include `null`, `Elixir.SwitchboardWeb.V1.Specs.PageI | 3505 | 1 |
| x-api-evangelist-processing | `x-api-evangelist-processing` appears on operations. Its value is a structured object. Used by 9 providers across 48 OpenAPI documents. Consistent with data & schema semantics — this is inferred from | 3475 | 9 |
| x-open-allow-strlist | `x-open-allow-strlist` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inf | 3100 | 1 |
| x-request-id | `x-request-id` appears on header objects. Its value is a structured object. Used by 21 providers across 47 OpenAPI documents. Consistent with identity & relationships — this is inferred from where the | 3086 | 21 |
| x-conditional | `x-conditional` appears on operations and on schema objects and properties. Its value is a boolean flag. Used by 46 providers across 53 OpenAPI documents. Consistent with validation & constraints — th | 3041 | 46 |
|
x-ms-parameter-location
vendor |
`x-ms-parameter-location` appears on parameter objects. Its value is a string. Used by 7 providers across 533 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooli | 2979 | 7 |
| x-enumDescriptions | `x-enumDescriptions` appears on schema objects and properties. Its value is a list. Used by 36 providers across 84 OpenAPI documents. Observed values include `*ref_91`, `&ref_91`. Consistent with type | 2809 | 36 |
| x-open-field-id | `x-open-field-id` appears on schema objects and properties. Its value is an integer. Used by a single provider across 1 OpenAPI document. Observed values include `1`, `2`, `3`, `4`. Consistent with id | 2499 | 1 |
| x-spec-enum-id | `x-spec-enum-id` appears on schema objects and properties and on operations. Its value is a string. Used by 8 providers across 17 OpenAPI documents. Observed values include `65feb4244cc9110c`, `2696b7 | 2467 | 8 |
| x-oaiMeta | `x-oaiMeta` appears on schema objects and properties and on operations. Its value is a structured object. Used by 2 providers across 14 OpenAPI documents. Consistent with data & schema semantics — thi | 2422 | 2 |
|
x-ms-long-running-operation
vendor |
`x-ms-long-running-operation` appears on operations and on path items. Its value is a boolean flag. Used by 8 providers across 296 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning i | 2373 | 8 |
|
x-ms-identifiers
vendor |
`x-ms-identifiers` appears on schema objects and properties. It is used as a marker with no value. Used by a single provider across 240 OpenAPI documents. It sits in the `x-ms-` namespace, so its mean | 2362 | 1 |
|
x-ms-client-flatten
vendor |
`x-ms-client-flatten` appears on schema objects and properties. Its value is a boolean flag. Used by 8 providers across 359 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defin | 2167 | 8 |
| x-open-allow-strnum | `x-open-allow-strnum` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is infe | 2090 | 1 |
| x-description-i18n | `x-description-i18n` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 6 OpenAPI documents. Consistent with data & schema semantics — this is | 2073 | 1 |
| x-allOf | `x-allOf` appears on schema objects and properties. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with type system — this is inferred from where the key appears | 1973 | 1 |
| x-cpanel-api-version | `x-cpanel-api-version` appears on operations. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `UAPI`, `WHM API 1`. Consistent with data & schema se | 1939 | 1 |
| x-extensible-enum | `x-extensible-enum` appears on schema objects and properties. Its value is a list. Used by 16 providers across 55 OpenAPI documents. Observed values include `[AWS, GCP, AZURE]`, `[ZIP, JAR]`, `[ORGANI | 1868 | 16 |
|
x-obmcs-client-retries-enabled
vendor |
`x-obmcs-client-retries-enabled` appears on operations. Its value is a boolean flag. Used by 3 providers across 130 OpenAPI documents. It sits in the `x-obmcs-` namespace, so its meaning is defined by | 1833 | 3 |
| x-v | `x-v` appears on header objects. Its value is a structured object. Used by 46 providers across 53 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appea | 1808 | 46 |
|
x-obmcs-enumref
vendor |
`x-obmcs-enumref` appears on schema objects and properties and on parameter objects. Its value is a string. Used by 3 providers across 116 OpenAPI documents. It sits in the `x-obmcs-` namespace, so it | 1689 | 3 |
| x-positive | `x-positive` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 15 OpenAPI documents. Consistent with type system — this is inferred from where the | 1613 | 1 |
| x-open-source | `x-open-source` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `$.rpc.output.data`, `$.http.query.adverti | 1604 | 1 |
| x-enum-varnames | `x-enum-varnames` appears on schema objects and properties. Its value is a list. Used by 75 providers across 124 OpenAPI documents. Observed values include `[INPUT, FILTER, PRE_OUTPUT, OUTPUT]`, `['Us | 1585 | 75 |
| x-mutating | `x-mutating` appears on operations. Its value is a boolean flag. Used by a single provider across 36 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key ap | 1450 | 1 |
|
x-atlassian-data-security-policy
vendor |
`x-atlassian-data-security-policy` appears on operations. Its value is a list. Used by a single provider across 91 OpenAPI documents. It sits in the `x-atlassian-` namespace, so its meaning is defined | 1443 | 1 |
| x-self-access | `x-self-access` appears on operations and on path items. Its value is a boolean flag. Used by 2 providers across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wh | 1439 | 2 |
| x-enum-descriptions | `x-enum-descriptions` appears on schema objects and properties. Its value is a structured object. Used by 28 providers across 61 OpenAPI documents. Consistent with type system — this is inferred from | 1372 | 28 |
| x-correlator | `x-correlator` appears on header objects. Its value is a structured object. Used by 5 providers across 107 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 1332 | 5 |
| x-enumNames | `x-enumNames` appears on schema objects and properties. Its value is a list. Used by 20 providers across 53 OpenAPI documents. Consistent with type system — this is inferred from where the key appears | 1261 | 20 |
| x-readonly | `x-readonly` appears on operations. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with mutability & access — this is inferred from where the key appears | 1218 | 1 |
| x-evidence | `x-evidence` appears on operations and in the info block. Its value is a structured object. Used by 47 providers across 500 OpenAPI documents. Consistent with data & schema semantics — this is inferre | 1198 | 47 |
|
x-ms-mutability
vendor |
`x-ms-mutability` appears on schema objects and properties. Its value is a list. Used by 4 providers across 175 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms too | 1195 | 4 |
| x-schemaName | `x-schemaName` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `PriceRule`, `AdminAddClaimItems`, `AdminA | 1194 | 1 |
| x-add-datatype | `x-add-datatype` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred | 1127 | 1 |
|
x-ms-long-running-operation-options
vendor |
`x-ms-long-running-operation-options` appears on operations and on path items. Its value is a structured object. Used by 3 providers across 161 OpenAPI documents. It sits in the `x-ms-` namespace, so | 1127 | 3 |
| x-name | `x-name` appears on request bodies. Its value is a string. Used by 12 providers across 27 OpenAPI documents. Observed values include `request`, `model`, `publishParameters`, `body`. Consistent with na | 1119 | 12 |
|
x-ms-parameter-grouping
vendor |
`x-ms-parameter-grouping` appears on parameter objects. Its value is a structured object. Used by a single provider across 19 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is def | 1087 | 1 |
| x-value | `x-value` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Aim`, `Automation`, `CampaignPoll`, `Conversati | 1087 | 1 |
|
x-xgen-version
vendor |
`x-xgen-version` appears on response objects. Its value is a string. Used by a single provider across 2 OpenAPI documents. It sits in the `x-xgen-` namespace, so its meaning is defined by xgen tooling | 1077 | 1 |
| x-source | `x-source` appears on schema objects and properties. Its value is a structured object. Used by 127 providers across 276 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 1044 | 127 |
|
x-junction-exhaustive
vendor |
`x-junction-exhaustive` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 8 OpenAPI documents. It sits in the `x-junction-` namespace, so its mean | 1032 | 1 |
| x-access | `x-access` appears on schema objects and properties. Its value is a list. Used by 4 providers across 6 OpenAPI documents. Observed values include `Public`, `invitation-only-beta`, `gated`. Consistent | 1019 | 4 |
| x-anyOf | `x-anyOf` appears on schema objects and properties. Its value is a list. Used by 4 providers across 8 OpenAPI documents. Consistent with type system — this is inferred from where the key appears and w | 1007 | 4 |
| x-maturity | `x-maturity` appears on operations. Its value is a list. Used by a single provider across 32 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears an | 981 | 1 |
| x-schema-id | `x-schema-id` appears on schema objects and properties. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `LocalizedStrings`, `HybridIdentifier`, `Ad | 979 | 1 |
| x-version | `x-version` appears on operations. Its value is a string. Used by 49 providers across 56 OpenAPI documents. Observed values include `1`, `2`, `3`, `5`. Consistent with data & schema semantics — this i | 951 | 49 |
|
x-apidog-name
vendor |
`x-apidog-name` appears on response objects. Its value is a string. Used by 5 providers across 7 OpenAPI documents. It sits in the `x-apidog-` namespace, so its meaning is defined by apidog tooling ra | 936 | 5 |
| x-accepts | `x-accepts` appears on operations. Its value is a string. Used by 9 providers across 23 OpenAPI documents. Observed values include `application/json`, `application/yaml`. Consistent with data & schema | 929 | 9 |
| x-referenceable | `x-referenceable` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with identity & relationships — this is inferr | 910 | 1 |
|
x-apifox-folder
vendor |
`x-apifox-folder` appears on operations. Its value is a string. Used by 4 providers across 24 OpenAPI documents. It sits in the `x-apifox-` namespace, so its meaning is defined by apifox tooling rathe | 908 | 4 |
| x-form-factors | `x-form-factors` appears on schema objects and properties and on operations. Its value is a string. Used by a single provider across 38 OpenAPI documents. Observed values include `public`, `private`, | 906 | 1 |
| x-bnch-rate-limit-tier | `x-bnch-rate-limit-tier` appears on operations. Its value is an integer. Used by a single provider across 1 OpenAPI document. Observed values include `4`, `5`, `3`, `2`. Consistent with data & schema | 873 | 1 |
| x-allowNullValue | `x-allowNullValue` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 9 OpenAPI documents. Consistent with data & schema semantics — this is inferr | 862 | 1 |
|
x-apifox-name
vendor |
`x-apifox-name` appears on response objects. Its value is a string. Used by 4 providers across 24 OpenAPI documents. It sits in the `x-apifox-` namespace, so its meaning is defined by apifox tooling r | 847 | 4 |
|
x-ms-error-response
vendor |
`x-ms-error-response` appears on response objects. Its value is a boolean flag. Used by 2 providers across 43 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooli | 844 | 2 |
|
x-ds-definition-name
vendor |
`x-ds-definition-name` appears on schema objects and properties. Its value is a string. Used by a single provider across 6 OpenAPI documents. It sits in the `x-ds-` namespace, so its meaning is define | 843 | 1 |
|
x-twilio
vendor |
`x-twilio` appears on path items. Its value is a structured object. Used by a single provider across 47 OpenAPI documents. It sits in the `x-twilio-` namespace, so its meaning is defined by twilio too | 833 | 1 |
| x-cohesity-discriminator-value | `x-cohesity-discriminator-value` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `kVMware`, `kCassandra`, | 824 | 1 |
| x-go-type-skip-optional-pointer | `x-go-type-skip-optional-pointer` appears on schema objects and properties. Its value is a boolean flag. Used by 16 providers across 37 OpenAPI documents. Consistent with type system — this is inferre | 767 | 16 |
| x-terraform-force-new | `x-terraform-force-new` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is i | 749 | 1 |
|
x-apidog-folder
vendor |
`x-apidog-folder` appears on operations and on schema objects and properties. Its value is a string. Used by 5 providers across 7 OpenAPI documents. It sits in the `x-apidog-` namespace, so its meanin | 725 | 5 |
| x-esri-field-type | `x-esri-field-type` appears on schema objects and properties. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `esriFieldTypeString`, `esriFieldTypeDouble | 725 | 2 |
| x-ai-description | `x-ai-description` appears on operations. Its value is a structured object. Used by a single provider across 19 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 720 | 1 |
| x-iam-actions | `x-iam-actions` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appears a | 716 | 1 |
|
x-aws-operation-name
vendor |
`x-aws-operation-name` appears on operations. Its value is a string. Used by 4 providers across 4 OpenAPI documents. It sits in the `x-aws-` namespace, so its meaning is defined by aws tooling rather | 704 | 4 |
| x-rollback | `x-rollback` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `none`, `clean`, `lossy`. Consistent with data & schema semanti | 690 | 1 |
|
x-apifox-status
vendor |
`x-apifox-status` appears on operations. Its value is a string. Used by 4 providers across 24 OpenAPI documents. It sits in the `x-apifox-` namespace, so its meaning is defined by apifox tooling rathe | 681 | 4 |
| x-run-in-apifox | `x-run-in-apifox` appears on operations. Its value is a string. Used by 4 providers across 24 OpenAPI documents. Observed values include `https://app.apifox.com/web/project/7948067/apis/api-430293359- | 681 | 4 |
| x-pattern | `x-pattern` appears on schema objects and properties. Its value is a string. Used by 6 providers across 184 OpenAPI documents. Observed values include `[\u0020-\uD7FF\uE000-\uFFFD\uD800\uDC00-\uDBFF\u | 659 | 6 |
|
x-fabric-request-id
vendor |
`x-fabric-request-id` appears on header objects. Its value is a structured object. Used by a single provider across 10 OpenAPI documents. It sits in the `x-fabric-` namespace, so its meaning is define | 651 | 1 |
| x-immutable | `x-immutable` appears on schema objects and properties. Its value is a boolean flag. Used by 3 providers across 4 OpenAPI documents. Consistent with mutability & access — this is inferred from where t | 641 | 3 |
| x-ai-responding-instructions | `x-ai-responding-instructions` appears on operations. Its value is a list. Used by a single provider across 19 OpenAPI documents. Consistent with type system — this is inferred from where the key appe | 630 | 1 |
| x-ai-reasoning-instructions | `x-ai-reasoning-instructions` appears on operations. Its value is a list. Used by a single provider across 19 OpenAPI documents. Consistent with type system — this is inferred from where the key appea | 624 | 1 |
| x-operation-name | `x-operation-name` appears on operations. Its value is a string. Used by 4 providers across 5 OpenAPI documents. Observed values include `get`, `list`, `delete`, `update`. Consistent with naming & ali | 621 | 4 |
| x-terraform-computed | `x-terraform-computed` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with mutability & access — this is inferr | 617 | 1 |
|
x-plaid-business-unit-context
vendor |
`x-plaid-business-unit-context` appears on path items. Its value is a string. Used by a single provider across 67 OpenAPI documents. It sits in the `x-plaid-` namespace, so its meaning is defined by p | 607 | 1 |
| x-alternatives | `x-alternatives` appears on schema objects and properties and on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is | 604 | 1 |
| x-enum-description | `x-enum-description` appears on schema objects and properties. Its value is a list. Used by 2 providers across 16 OpenAPI documents. Consistent with type system — this is inferred from where the key a | 596 | 2 |
| x-description-1 | `x-description-1` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Invalid signature received for JSON Web Token valida | 591 | 1 |
| x-ai-suggestions | `x-ai-suggestions` appears on operations. Its value is a list. Used by a single provider across 19 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appe | 585 | 1 |
| x-fhir-search-type | `x-fhir-search-type` appears on operations. Its value is a string. Used by 2 providers across 111 OpenAPI documents. Observed values include `token`, `reference`, `date`, `number`. Consistent with typ | 570 | 2 |
| x-type-name | `x-type-name` appears on schema objects and properties and on parameter objects. Its value is a string. Used by a single provider across 16 OpenAPI documents. Observed values include `UtcDateTime`, `D | 561 | 1 |
| x-apyhub-atoms | `x-apyhub-atoms` appears on operations. Its value is an integer. Used by a single provider across 210 OpenAPI documents. Observed values include `50`, `100`, `500`, `30`. Consistent with data & schema | 552 | 1 |
| x-gitbook-description-html | `x-gitbook-description-html` appears on schema objects and properties. Its value is a structured object. Used by 3 providers across 6 OpenAPI documents. Consistent with data & schema semantics — this | 552 | 3 |
| x-client-only | `x-client-only` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred | 542 | 1 |
| x-open-convert | `x-open-convert` appears on schema objects and properties and on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is | 542 | 1 |
| x-workload | `x-workload` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred fro | 542 | 1 |
| x-trace-id | `x-trace-id` appears on header objects. Its value is a structured object. Used by 2 providers across 10 OpenAPI documents. Consistent with identity & relationships — this is inferred from where the ke | 539 | 2 |
| x-dependency | `x-dependency` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferr | 515 | 1 |
| x-audience | `x-audience` appears on server objects and on operations. Its value is a string. Used by 27 providers across 102 OpenAPI documents. Observed values include `business-unit-internal`, `public`, `externa | 513 | 27 |
| x-fhir-search-parameter | `x-fhir-search-parameter` appears on operations. Its value is a string. Used by 2 providers across 111 OpenAPI documents. Observed values include `http://hl7.org/fhir/R4/SearchParameter/Resource-id`, | 513 | 2 |
| x-response-codes | `x-response-codes` appears on response objects. Its value is a structured object. Used by a single provider across 24 OpenAPI documents. Consistent with data & schema semantics — this is inferred from | 512 | 1 |
| x-isnullable | `x-isnullable` appears on schema objects and properties. Its value is a boolean flag. Used by 4 providers across 4 OpenAPI documents. Consistent with type system — this is inferred from where the key | 510 | 4 |
|
x-ms-azure-resource
vendor |
`x-ms-azure-resource` appears on schema objects and properties. Its value is a boolean flag. Used by 8 providers across 211 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defin | 509 | 8 |
| x-insta-unchangeable | `x-insta-unchangeable` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is in | 502 | 1 |
| x-validators | `x-validators` appears on schema objects and properties. Its value is a list. Used by 2 providers across 3 OpenAPI documents. Consistent with validation & constraints — this is inferred from where the | 489 | 2 |
|
x-ms-request-id
vendor |
`x-ms-request-id` appears on header objects and on operations. Its value is a structured object. Used by 2 providers across 23 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is de | 488 | 2 |
| x-authenticated | `x-authenticated` appears on operations. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the ke | 484 | 1 |
|
x-ds-method
vendor |
`x-ds-method` appears on operations. Its value is a string. Used by a single provider across 6 OpenAPI documents. It sits in the `x-ds-` namespace, so its meaning is defined by ds tooling rather than | 484 | 1 |
|
x-ds-service
vendor |
`x-ds-service` appears on operations. Its value is a string. Used by a single provider across 6 OpenAPI documents. It sits in the `x-ds-` namespace, so its meaning is defined by ds tooling rather than | 484 | 1 |
|
x-apideck-schema-id
vendor |
`x-apideck-schema-id` appears on schema objects and properties. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is de | 478 | 1 |
| x-amf-union | `x-amf-union` appears on schema objects and properties. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with type system — this is inferred from where the key appe | 472 | 1 |
|
x-portone-description
vendor |
`x-portone-description` appears on operations and on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-portone-` namespace, s | 456 | 1 |
| x-errors | `x-errors` appears on response objects. Its value is a list. Used by 3 providers across 12 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears and | 451 | 3 |
| x-required-privilege | `x-required-privilege` appears on operations. Its value is a structured object. Used by a single provider across 20 OpenAPI documents. Consistent with validation & constraints — this is inferred from | 448 | 1 |
| x-required-privileges | `x-required-privileges` appears on operations. Its value is a list. Used by a single provider across 20 OpenAPI documents. Consistent with validation & constraints — this is inferred from where the ke | 448 | 1 |
| x-operation-settings | `x-operation-settings` appears on operations. Its value is a structured object. Used by 7 providers across 23 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where t | 445 | 7 |
|
x-obmcs-terraform
vendor |
`x-obmcs-terraform` appears on operations. Its value is a structured object. Used by 3 providers across 53 OpenAPI documents. It sits in the `x-obmcs-` namespace, so its meaning is defined by obmcs to | 440 | 3 |
| x-discovery-path-template | `x-discovery-path-template` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `v2/{name}`, `v3/{name}`, `v2/{parent}/contexts` | 437 | 1 |
| x-exegesis-controller | `x-exegesis-controller` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Organization`, `Delivery`, `User`, `Location`. Consi | 437 | 1 |
| x-state | `x-state` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `Experimental; added in 9.5.0`, `Generally available; added in 9.4.0`, ` | 431 | 2 |
|
x-ibm-ahub-byok
vendor |
`x-ibm-ahub-byok` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tooling r | 429 | 1 |
| x-disallowUser | `x-disallowUser` appears on operations. Its value is a boolean flag. Used by a single provider across 17 OpenAPI documents. Consistent with validation & constraints — this is inferred from where the k | 424 | 1 |
| x-providerName | `x-providerName` appears in the info block. Its value is a string. Used by 122 providers across 414 OpenAPI documents. Observed values include `amazonaws.com`, `googleapis.com`, `azure.com`, `Qlik`. C | 416 | 122 |
| x-serviceName | `x-serviceName` appears in the info block. Its value is a string. Used by 118 providers across 410 OpenAPI documents. Observed values include `glue`, `codebuild`, `apprunner`, `states`. Consistent wit | 411 | 118 |
| x-run-in-apidog | `x-run-in-apidog` appears on operations. Its value is a string. Used by 5 providers across 11 OpenAPI documents. Observed values include `https://app.apidog.com/web/project/737471/apis/api-11716510-ru | 409 | 5 |
| x-additionalPropertiesName | `x-additionalPropertiesName` appears on schema objects and properties. Its value is a string. Used by 20 providers across 37 OpenAPI documents. Observed values include `nexset_attribute_name`, `db_col | 405 | 20 |
| x-body-name | `x-body-name` appears on request bodies. Its value is a string. Used by 4 providers across 10 OpenAPI documents. Observed values include `body`, `source`, `environment`, `role_definition`. Consistent | 395 | 4 |
| x-twitter | `x-twitter` appears in the info block. Its value is a string. Used by 110 providers across 393 OpenAPI documents. Observed values include `PermittedSoc`, `youtube`, `MercedesBenz`, `TomTom`. Consisten | 393 | 110 |
|
x-swagger-1-2-source
vendor |
`x-swagger-1-2-source` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-swagger-` namespace, so its meaning is defined by swagger to | 389 | 1 |
|
x-apidog-status
vendor |
`x-apidog-status` appears on operations. Its value is a string. Used by 5 providers across 7 OpenAPI documents. It sits in the `x-apidog-` namespace, so its meaning is defined by apidog tooling rather | 388 | 5 |
| x-go-type | `x-go-type` appears on schema objects and properties. Its value is a string. Used by 34 providers across 45 OpenAPI documents. Observed values include `float64`, `uuid.UUID`, `int64`, `string`. Consis | 388 | 34 |
| x-preferred | `x-preferred` appears in the info block. Its value is a boolean flag. Used by 110 providers across 387 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key | 388 | 110 |
| x-open-enum | `x-open-enum` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with type system — this is inferred from where | 385 | 1 |
| x-apiClientRegistration | `x-apiClientRegistration` appears in the info block. Its value is a structured object. Used by 107 providers across 383 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 384 | 107 |
| x-xml-element | `x-xml-element` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `ServiceInfo`, `HourlyLmps`, `Outages`, `FiveMinLmps`. Consis | 377 | 1 |
|
x-apisguru-driver
vendor |
`x-apisguru-driver` appears in the info block. Its value is a string. Used by 101 providers across 374 OpenAPI documents. It sits in the `x-apisguru-` namespace, so its meaning is defined by apisguru | 374 | 101 |
| x-hasEquivalentPaths | `x-hasEquivalentPaths` appears at the root of the document. Its value is a boolean flag. Used by 92 providers across 365 OpenAPI documents. Consistent with data & schema semantics — this is inferred f | 365 | 92 |
| x-adpOperationData | `x-adpOperationData` appears on operations. Its value is a structured object. Used by a single provider across 59 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 362 | 1 |
| x-content-type | `x-content-type` appears on operations. Its value is a string. Used by 8 providers across 18 OpenAPI documents. Observed values include `application/json`, `application/octet-stream`, `application/x-w | 360 | 8 |
| x-i18n | `x-i18n` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred fro | 360 | 1 |
| x-properties | `x-properties` appears on operations and in the document. Its value is a structured object. Used by 4 providers across 138 OpenAPI documents. Consistent with data & schema semantics — this is inferred | 355 | 4 |
| x-adpPathData | `x-adpPathData` appears on path items. Its value is a structured object. Used by a single provider across 59 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where th | 353 | 1 |
| x-enum-elements | `x-enum-elements` appears on schema objects and properties. Its value is a list. Used by 11 providers across 22 OpenAPI documents. Consistent with type system — this is inferred from where the key app | 352 | 11 |
| x-is-money | `x-is-money` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 8 OpenAPI documents. Consistent with type system — this is inferred from where the | 351 | 1 |
|
x-fds-fql-formula
vendor |
`x-fds-fql-formula` appears on schema objects and properties. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-fds-` namespace, so its meaning is defined | 350 | 1 |
|
x-box-resource-id
vendor |
`x-box-resource-id` appears on schema objects and properties. Its value is a string. Used by a single provider across 51 OpenAPI documents. It sits in the `x-box-` namespace, so its meaning is defined | 346 | 1 |
| x-sensitive | `x-sensitive` appears on schema objects and properties. Its value is a boolean flag. Used by 6 providers across 21 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wh | 346 | 6 |
|
x-ms-skip-url-encoding
vendor |
`x-ms-skip-url-encoding` appears on parameter objects. Its value is a boolean flag. Used by 2 providers across 163 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms | 339 | 2 |
| x-shortName | `x-shortName` appears in the document. Its value is a string. Used by 46 providers across 52 OpenAPI documents. Observed values include `Accounts`, `Account Balances`, `Products`, `Transactions`. Cons | 334 | 46 |
| x-field-extra-annotation | `x-field-extra-annotation` appears on schema objects and properties. Its value is a string. Used by 10 providers across 35 OpenAPI documents. Observed values include `@com.fasterxml.jackson.annotation | 325 | 10 |
| x-operator | `x-operator` appears in the info block. Its value is a string. Used by 106 providers across 319 OpenAPI documents. Observed values include `institution`, `tenant`, `institution — every host is under I | 322 | 106 |
| x-constraint | `x-constraint` appears on schema objects and properties and on operations. Its value is a structured object. Used by 5 providers across 5 OpenAPI documents. Consistent with validation & constraints — | 317 | 5 |
| x-extra-attributes | `x-extra-attributes` appears on response objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with size & shape — this is inferred from where the | 317 | 1 |
| x-practice-access | `x-practice-access` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `share_patients" need to be set for data access among pra | 316 | 1 |
|
x-ms-client-request-id
vendor |
`x-ms-client-request-id` appears on parameter objects and on header objects. Its value is a boolean flag. Used by 3 providers across 17 OpenAPI documents. It sits in the `x-ms-` namespace, so its mean | 307 | 3 |
| x-description-2 | `x-description-2` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Client is not global.`, `Invalid signature received | 305 | 1 |
| x-endpoint-status | `x-endpoint-status` appears on operations. Its value is a string. Used by 13 providers across 13 OpenAPI documents. Observed values include `confirmed`, `modeled`. Consistent with data & schema semant | 304 | 13 |
| x-orum-error-invalid | `x-orum-error-invalid` appears on schema objects and properties and on parameter objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with validat | 302 | 1 |
| x-filterable | `x-filterable` appears on schema objects and properties. Its value is a boolean flag. Used by 3 providers across 8 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wh | 301 | 3 |
|
x-veeam-spec
vendor |
`x-veeam-spec` appears on parameter objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-veeam-` namespace, so its meaning is defined by v | 301 | 1 |
| x-workflow | `x-workflow` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `removeItemReturnActionWorkflow`, `getOrderDetailWorkflow`, `up | 288 | 1 |
| x-audiences | `x-audiences` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appears and | 285 | 1 |
| x-feature | `x-feature` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `TeamMessaging`, `ReadExtensions`, `SMSSending`, `EditUsers`. Con | 285 | 1 |
| x-experimental | `x-experimental` appears on operations. Its value is a boolean flag. Used by 5 providers across 38 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appe | 283 | 5 |
| x-path-item-properties | `x-path-item-properties` appears on operations. Its value is a structured object. Used by a single provider across 8 OpenAPI documents. Consistent with size & shape — this is inferred from where the k | 283 | 1 |
| x-stripeBypassValidation | `x-stripeBypassValidation` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 29 OpenAPI documents. Consistent with validation & constraints — this | 281 | 1 |
| x-surfaces | `x-surfaces` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appears and | 280 | 1 |
| x-expandableFields | `x-expandableFields` appears on schema objects and properties and on response objects. Its value is a list. Used by a single provider across 47 OpenAPI documents. Consistent with identity & relationsh | 274 | 1 |
| x-custom-config | `x-custom-config` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where th | 272 | 1 |
|
x-apideck-api
vendor |
`x-apideck-api` appears on operations. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is defined by apideck tooling | 255 | 1 |
| x-request-access-name | `x-request-access-name` appears on operations and on path items. Its value is a string. Used by 2 providers across 3 OpenAPI documents. Observed values include `SQL API v1`, `User Notifications API v1 | 253 | 2 |
| x-sd-openapi | `x-sd-openapi` appears on operations. Its value is a structured object. Used by a single provider across 29 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 252 | 1 |
| x-parent | `x-parent` appears on schema objects and properties. Its value is a string. Used by 11 providers across 15 OpenAPI documents. Observed values include `data.attributes`, `true`, `Brand Kits`, `data`. C | 250 | 11 |
| x-length | `x-length` appears on schema objects and properties. Its value is an integer. Used by a single provider across 1 OpenAPI document. Observed values include `35`, `70`, `5`, `16`. Consistent with valida | 236 | 1 |
|
x-veeam-authorize
vendor |
`x-veeam-authorize` appears on operations. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-veeam-` namespace, so its meaning is defined by vee | 236 | 1 |
| x-node_available_in | `x-node_available_in` appears on schema objects and properties. Its value is a list. Used by a single provider across 21 OpenAPI documents. Consistent with data & schema semantics — this is inferred f | 235 | 1 |
| x-one-of | `x-one-of` appears on schema objects and properties. Its value is a string. Used by 2 providers across 9 OpenAPI documents. Observed values include `config`, `ProjectIdentifier`, `principal`, `probe`. | 228 | 2 |
|
x-ms-odata
vendor |
`x-ms-odata` appears on path items and on operations. Its value is a string. Used by 3 providers across 35 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling | 220 | 3 |
| x-unresolved-stoplight-ref | `x-unresolved-stoplight-ref` appears on schema objects and properties. Its value is a string. Used by a single provider across 5 OpenAPI documents. Observed values include `stoplight://resources/overr | 220 | 1 |
| x-discriminator-value | `x-discriminator-value` appears on schema objects and properties. Its value is a string. Used by 5 providers across 6 OpenAPI documents. Observed values include `RFQ`, `DCA`, `TWAP`, `GRID`. Consisten | 218 | 5 |
| x-xsd-source | `x-xsd-source` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `schemas/iso-new-england-web-services-ns0.x | 217 | 1 |
| x-fhir-supported-profile | `x-fhir-supported-profile` appears on operations. Its value is a list. Used by 2 providers across 69 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key ap | 216 | 2 |
| x-max-page-items | `x-max-page-items` appears on parameter objects. Its value is an integer. Used by 2 providers across 3 OpenAPI documents. Observed values include `500`, `1000`, `255`, `5000`. Consistent with validati | 216 | 2 |
| x-operation-id-source | `x-operation-id-source` appears on operations. Its value is a string. Used by 9 providers across 71 OpenAPI documents. Observed values include `derived`, `normalized`. Consistent with identity & relat | 210 | 9 |
| x-external-error | `x-external-error` appears on header objects. Its value is a structured object. Used by a single provider across 9 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wh | 207 | 1 |
| x-pushable | `x-pushable` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 4 OpenAPI documents. Consistent with data & schema semantics — this is inferred fro | 204 | 1 |
| x-stage | `x-stage` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `beta`, `alpha`. Consistent with data & schema semantics — this is | 204 | 1 |
| x-open-allowlist | `x-open-allowlist` appears on operations. It is used as a marker with no value. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from whe | 202 | 1 |
| x-open-denylist | `x-open-denylist` appears on operations. It is used as a marker with no value. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from wher | 202 | 1 |
| x-open-rules | `x-open-rules` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the k | 202 | 1 |
| x-open-settings | `x-open-settings` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where th | 202 | 1 |
| x-polygon-go-type | `x-polygon-go-type` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 34 OpenAPI documents. Consistent with type system — this is inferred fr | 200 | 1 |
|
x-xgen-method-verb-override
vendor |
`x-xgen-method-verb-override` 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 defin | 199 | 1 |
| x-expansionResources | `x-expansionResources` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 33 OpenAPI documents. Consistent with identity & relationships — thi | 198 | 1 |
| x-product-area | `x-product-area` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appears | 197 | 1 |
| x-required | `x-required` appears on schema objects and properties. Its value is a list. Used by 2 providers across 11 OpenAPI documents. Observed values include `true`. Consistent with validation & constraints — | 197 | 2 |
|
x-amz-target
vendor |
`x-amz-target` appears on operations. Its value is a string. Used by 5 providers across 5 OpenAPI documents. It sits in the `x-amz-` namespace, so its meaning is defined by amz tooling rather than by | 195 | 5 |
|
x-postman-collection
vendor |
`x-postman-collection` appears on operations. Its value is a string. Used by 2 providers across 4 OpenAPI documents. It sits in the `x-postman-` namespace, so its meaning is defined by postman tooling | 195 | 2 |
| x-jsoninclude-nonnull-annotation | `x-jsoninclude-nonnull-annotation` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 7 OpenAPI documents. Consistent with data & schema semantics | 191 | 1 |
| x-ratelimit-limit | `x-ratelimit-limit` appears on header objects. Its value is a structured object. Used by 12 providers across 23 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 190 | 12 |
| x-allowableValues | `x-allowableValues` appears on parameter objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Existing account token`, `Existing statement summ | 188 | 1 |
| x-right | `x-right` appears on operations. Its value is a string. Used by a single provider across 12 OpenAPI documents. Observed values include `iam/assignRole`, `iam/unassignRole`, `iam/listAssignedRoles`, `i | 186 | 1 |
| x-terraform-field-name | `x-terraform-field-name` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `tag`, `tag_management_enabled`, | 186 | 1 |
| x-discriminator | `x-discriminator` appears on schema objects and properties. Its value is a string. Used by 3 providers across 6 OpenAPI documents. Observed values include `type`, `actionType`, `cloudCredentialsType`, | 185 | 3 |
| x-json-property | `x-json-property` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `http://bibfra.me/vocab/lite/name`, `htt | 185 | 1 |
|
x-portone-status-code
vendor |
`x-portone-status-code` appears on schema objects and properties. Its value is an integer. Used by a single provider across 1 OpenAPI document. It sits in the `x-portone-` namespace, so its meaning is | 185 | 1 |
| x-type | `x-type` appears on schema objects and properties. Its value is a string. Used by 9 providers across 17 OpenAPI documents. Observed values include `bignumber`, `monetary`, `crn`, `String`. Consistent | 185 | 9 |
| x-response-identifier | `x-response-identifier` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `id`, `name`, `ip`, `access`. Consistent with identit | 183 | 1 |
|
x-microcks-refs
vendor |
`x-microcks-refs` appears on response objects. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-microcks-` namespace, so its meaning is defined by microcks t | 182 | 1 |
|
x-google-method-id
vendor |
`x-google-method-id` appears on operations. 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 google toolin | 179 | 1 |
| x-pattern-message | `x-pattern-message` appears on schema objects and properties. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `should be 'Logs' or 'Metrics' or 'Slo`, `s | 177 | 2 |
| x-apiary-response-models | `x-apiary-response-models` appears on response objects. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where | 175 | 1 |
| x-api-key | `x-api-key` appears on schema objects and properties. Its value is a string. Used by 21 providers across 83 OpenAPI documents. Observed values include `G3VIdNTOjscKbVGPqb8aNMeCA1dAHxnz`, `integrator's | 174 | 21 |
|
x-ms-version
vendor |
`x-ms-version` appears on header objects. Its value is a structured object. Used by 2 providers across 6 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling ra | 173 | 2 |
| x-ratelimit-reset | `x-ratelimit-reset` appears on header objects. Its value is a structured object. Used by 10 providers across 20 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 172 | 10 |
| x-auditable | `x-auditable` appears on schema objects and properties. Its value is a boolean flag. Used by 4 providers across 4 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 167 | 4 |
|
x-ibm-name
vendor |
`x-ibm-name` appears in the info block. Its value is a string. Used by 5 providers across 153 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tooling rather than | 166 | 5 |
| x-resource | `x-resource` appears in the document. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `Employee`, `Group`, `Role Assignment`, `Role`. Consistent with ide | 163 | 2 |
|
x-yba-api-audit
vendor |
`x-yba-api-audit` appears on operations. Its value is a structured object. Used by 2 providers across 11 OpenAPI documents. It sits in the `x-yba-` namespace, so its meaning is defined by yba tooling | 162 | 2 |
| x-file | `x-file` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `strings.yaml`, `countries.yaml`, `businessRules.yaml`, `updateBusi | 161 | 1 |
| x-definition-type | `x-definition-type` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `ISO20022`, `Hal`, `Resources`, `Tech | 160 | 1 |
|
x-fds-dh
vendor |
`x-fds-dh` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. It sits in the `x-fds-` namespace, so its meaning is defined by fds to | 160 | 1 |
|
x-apideck-enum-id
vendor |
`x-apideck-enum-id` appears on schema objects and properties. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is defi | 159 | 1 |
|
x-merge-override
vendor |
`x-merge-override` 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-merge-` namespace, so its meaning | 159 | 1 |
|
x-ms-parameterized-host
vendor |
`x-ms-parameterized-host` appears at the root of the document. Its value is a structured object. Used by 2 providers across 159 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is d | 159 | 2 |
| x-node_unavailable_in | `x-node_unavailable_in` appears on schema objects and properties. It is used as a marker with no value. Used by a single provider across 13 OpenAPI documents. Consistent with data & schema semantics — | 158 | 1 |
| x-refined-from | `x-refined-from` appears at the root of the document. Its value is a list. Used by 13 providers across 157 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 157 | 13 |
| x-tier | `x-tier` appears on operations. Its value is a string. Used by 3 providers across 21 OpenAPI documents. Observed values include `free`, `pro`, `2`, `business`. Consistent with data & schema semantics | 157 | 3 |
| x-references | `x-references` appears on path items. Its value is a structured object. Used by 2 providers across 4 OpenAPI documents. Consistent with identity & relationships — this is inferred from where the key a | 156 | 2 |
| x-canvas-declared-type | `x-canvas-declared-type` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `User`, `Progress`, `RubricAssessment`, `Assig | 155 | 1 |
|
x-apideck-weights
vendor |
`x-apideck-weights` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its mean | 153 | 1 |
| x-original-swagger-version | `x-original-swagger-version` appears at the root of the document. Its value is a string. Used by 43 providers across 152 OpenAPI documents. Observed values include `2.0`. Consistent with naming & alia | 152 | 43 |
|
x-box-sanitized
vendor |
`x-box-sanitized` appears on operations. Its value is a boolean flag. Used by a single provider across 11 OpenAPI documents. It sits in the `x-box-` namespace, so its meaning is defined by box tooling | 151 | 1 |
| x-derived | `x-derived` appears on schema objects and properties. Its value is a structured object. Used by 4 providers across 6 OpenAPI documents. Consistent with mutability & access — this is inferred from wher | 150 | 4 |
| x-extensions | `x-extensions` appears on operations. Its value is a string. Used by a single provider across 6 OpenAPI documents. Observed values include `workload`, `workload,df`, `redirect,df`, `df`. Consistent wi | 150 | 1 |
|
x-fds-sdf
vendor |
`x-fds-sdf` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. It sits in the `x-fds-` namespace, so its meaning is defined by fds t | 150 | 1 |
| x-terraform-write-only | `x-terraform-write-only` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with mutability & access — this is infe | 150 | 1 |
| x-probe | `x-probe` appears on operations. Its value is a structured object. Used by 5 providers across 6 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears | 149 | 5 |
| x-orum-error-missing | `x-orum-error-missing` appears on schema objects and properties and on parameter objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & | 148 | 1 |
| x-apievangelist-source | `x-apievangelist-source` appears in the info block. Its value is a string. Used by 53 providers across 147 OpenAPI documents. Observed values include `https://perfectday.com/wp-json/wp/v2`, `https://a | 147 | 53 |
|
x-portone-error
vendor |
`x-portone-error` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-portone-` namespace, so its meaning is defined by port | 147 | 1 |
| x-anchors | `x-anchors` appears at the root of the document. Its value is a structured object. Used by 3 providers across 143 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 145 | 3 |
|
x-apifox
vendor |
`x-apifox` appears on schema objects and properties and on parameter objects. Its value is a structured object. Used by 2 providers across 4 OpenAPI documents. It sits in the `x-apifox-` namespace, so | 145 | 2 |
| x-passthrough | `x-passthrough` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key a | 145 | 1 |
| x-rbac | `x-rbac` appears on operations. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears | 145 | 2 |
|
x-swagger-1-2-name
vendor |
`x-swagger-1-2-name` 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-swagger-` namespace, so its meaning is defi | 145 | 1 |
| x-insta-comment | `x-insta-comment` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `See x-insta-comment on awsSettings`, ` | 144 | 1 |
| x-resourceId | `x-resourceId` appears on schema objects and properties. Its value is a string. Used by a single provider across 47 OpenAPI documents. Observed values include `refund`, `payment_method`, `apple_pay_do | 143 | 1 |
|
x-amz-apigw-id
vendor |
`x-amz-apigw-id` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-amz-` namespace, so its meaning is defined by amz t | 142 | 1 |
| x-amzn-RequestId | `x-amzn-RequestId` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from whe | 142 | 1 |
| x-bnch-organization | `x-bnch-organization` appears in the document. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Benchling`. Consistent with data & schema semantics | 142 | 1 |
| x-default-client | `x-default-client` appears at the root of the document. Its value is a string. Used by 2 providers across 142 OpenAPI documents. Observed values include `cURL`. Consistent with defaults & examples — t | 142 | 2 |
| x-excluded | `x-excluded` appears on operations. Its value is a boolean flag. Used by 8 providers across 9 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears a | 142 | 8 |
| x-headers | `x-headers` appears in the document. Its value is a structured object. Used by 3 providers across 142 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key a | 142 | 3 |
| x-verified | `x-verified` appears on operations. Its value is a structured object. Used by 10 providers across 18 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key ap | 142 | 10 |
|
x-ibm-configuration
vendor |
`x-ibm-configuration` appears at the root of the document. Its value is a structured object. Used by 4 providers across 136 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defi | 141 | 4 |
|
x-ms-enum-flags
vendor |
`x-ms-enum-flags` appears on schema objects and properties. Its value is a structured object. Used by 2 providers across 14 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defin | 141 | 2 |
| x-ratelimit-remaining | `x-ratelimit-remaining` appears on header objects. Its value is a structured object. Used by 12 providers across 21 OpenAPI documents. Consistent with data & schema semantics — this is inferred from w | 140 | 12 |
| x-path | `x-path` appears on schema objects and properties. Its value is a string. Used by 3 providers across 6 OpenAPI documents. Observed values include `/tapi-common:context/tapi-connectivity:connection/tap | 139 | 3 |
| x-expanded-response | `x-expanded-response` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `CloudProjectDatabaseServiceIntegration`, `CloudProject | 138 | 1 |
| x-js-format | `x-js-format` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `bigint`. Consistent with type system — this | 137 | 1 |
|
x-oai-discriminator-values
vendor |
`x-oai-discriminator-values` appears on schema objects and properties. Its value is a list. Used by a single provider across 3 OpenAPI documents. It sits in the `x-oai-` namespace, so its meaning is d | 137 | 1 |
| x-rbac-enabled | `x-rbac-enabled` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key | 134 | 1 |
| x-execution-weight | `x-execution-weight` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `medium`, `small`, `free`, `xl`. Consistent with orderi | 132 | 1 |
| x-format | `x-format` appears on schema objects and properties. Its value is a string. Used by 5 providers across 5 OpenAPI documents. Observed values include `int64`, `address`, `decimal`, `+E.164`. Consistent | 132 | 5 |
| x-writes | `x-writes` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appear | 131 | 1 |
| x-controller | `x-controller` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `api/comments`, `api/company_ssp_duty_assignment_matrix_duties`, `a | 130 | 2 |
| x-correlation-id | `x-correlation-id` appears on header objects. Its value is a structured object. Used by 4 providers across 6 OpenAPI documents. Consistent with identity & relationships — this is inferred from where t | 130 | 4 |
|
x-apideck-gotchas
vendor |
`x-apideck-gotchas` appears on operations. Its value is a list. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is defined by apideck toolin | 129 | 1 |
| x-traitTag | `x-traitTag` appears in the document and on tags. Its value is a boolean flag. Used by 16 providers across 38 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where t | 129 | 16 |
| x-abstractType | `x-abstractType` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 3 OpenAPI documents. Consistent with data & schema semantics — this is inf | 128 | 1 |
| x-cas-attribute | `x-cas-attribute` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `timeLatestTradePrice`, `valueLatestTra | 128 | 1 |
| x-hasPayrollUkProblem | `x-hasPayrollUkProblem` appears on operations. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 128 | 1 |
| x-rbac-allowed-groups | `x-rbac-allowed-groups` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `admin`, `admin,member`, `admin,saml-admin`, `admin,m | 127 | 1 |
| x-custom-attributes | `x-custom-attributes` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from wher | 126 | 1 |
| x-external | `x-external` appears on path items. Its value is a boolean flag. Used by 2 providers across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears a | 126 | 2 |
| x-modeled | `x-modeled` appears on operations. Its value is a boolean flag. Used by 22 providers across 28 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears | 126 | 22 |
|
x-atlassian-narrative
vendor |
`x-atlassian-narrative` appears at the root of the document. Its value is a structured object. Used by a single provider across 122 OpenAPI documents. It sits in the `x-atlassian-` namespace, so its m | 122 | 1 |
| x-fhir-instantiates | `x-fhir-instantiates` appears in the info block. Its value is a list. Used by 2 providers across 120 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key ap | 120 | 2 |
| x-fhir-patch-formats | `x-fhir-patch-formats` appears in the info block. Its value is a list. Used by 2 providers across 120 OpenAPI documents. Consistent with type system — this is inferred from where the key appears and w | 120 | 2 |
| x-ae-placeholder | `x-ae-placeholder` appears on schema objects and properties. Its value is a boolean flag. Used by 7 providers across 8 OpenAPI documents. Consistent with defaults & examples — this is inferred from wh | 119 | 7 |
| x-resources | `x-resources` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with identity & relationships — this is inferred from where the key appears an | 119 | 1 |
|
x-portone-enum
vendor |
`x-portone-enum` 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-portone-` namespace, so its meaning | 118 | 1 |
| x-zudoku-playground-enabled | `x-zudoku-playground-enabled` appears on operations. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from | 118 | 1 |
| x-ratelimit-tier | `x-ratelimit-tier` appears on operations. Its value is an integer. Used by a single provider across 12 OpenAPI documents. Observed values include `3`, `2`, `4`, `1`. Consistent with data & schema sema | 116 | 1 |
| x-authorization-privileges | `x-authorization-privileges` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the | 114 | 1 |
| x-og-claims-required | `x-og-claims-required` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with validation & constraints — this is inferred from where the key a | 113 | 1 |
| x-action | `x-action` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `index`, `show`, `create`, `update`. Consistent with data & schema | 112 | 1 |
| x-appdirect-api-stage | `x-appdirect-api-stage` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Early Access`, `Deprecated`. Consistent with data & | 111 | 1 |
| x-method | `x-method` appears in the info block and at the root of the document. Its value is a string. Used by 36 providers across 96 OpenAPI documents. Observed values include `searched`, `derived`, `probed`, | 111 | 36 |
| x-stability-level | `x-stability-level` appears on schema objects and properties and on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. Observed values include `beta`, `alpha`, `draft`. | 111 | 3 |
| x-observed-confidence | `x-observed-confidence` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `high`, `medium`. Consistent with data & schema seman | 109 | 1 |
| x-observed-method-evidence | `x-observed-method-evidence` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `explicit GET helper call site`, `explicit POST | 109 | 1 |
| x-observed-registry-key | `x-observed-registry-key` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `brokingHouse.branch`, `quote.indicationSuggestions | 109 | 1 |
| x-terraform-resource-name | `x-terraform-resource-name` appears on path items. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `users_v2`, `gcp_service_attachments_accept_list | 109 | 1 |
| x-api-id | `x-api-id` appears in the info block. Its value is a string. Used by 42 providers across 107 OpenAPI documents. Observed values include `TMF931`, `sap-concur-expense-report-v4`, `5ca54741-8f62-4aad-ab | 108 | 42 |
| x-status | `x-status` appears in the info block and on operations. Its value is a string. Used by 27 providers across 76 OpenAPI documents. Observed values include `validated`, `modeled`, `Work in progress`, `ST | 107 | 27 |
| x-openhandle-operation | `x-openhandle-operation` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `instagram.comment.likers.list`, `instagram.hashtag. | 106 | 1 |
| x-atMostOne | `x-atMostOne` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 8 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 105 | 1 |
| x-no-compatibility-guarantee | `x-no-compatibility-guarantee` appears on operations and on schema objects and properties. Its value is a boolean flag. Used by a single provider across 10 OpenAPI documents. Consistent with data & sc | 104 | 1 |
| x-oaiExpandable | `x-oaiExpandable` appears on schema objects and properties. Its value is a boolean flag. Used by 3 providers across 7 OpenAPI documents. Consistent with identity & relationships — this is inferred fro | 102 | 3 |
| x-createOnly | `x-createOnly` appears on schema objects and properties. Its value is a list. Used by a single provider across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wher | 101 | 1 |
| x-originalName | `x-originalName` appears on operations. Its value is a string. Used by 6 providers across 7 OpenAPI documents. Observed values include `pageSize`, `apiKey`, `editorLock`, `authorization`. Consistent w | 100 | 6 |
| x-terraform-sensitive | `x-terraform-sensitive` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is i | 100 | 1 |
| x-audit-log | `x-audit-log` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the ke | 99 | 1 |
| x-camara-commonalities | `x-camara-commonalities` appears in the info block. Its value is a number. Used by 6 providers across 99 OpenAPI documents. Observed values include `0.6`, `0.4.0`, `0.5`, `tbd`. Consistent with data & | 99 | 6 |
| x-data-access | `x-data-access` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the | 99 | 1 |
| x-hasAccountingValidationError | `x-hasAccountingValidationError` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with validation & constraints — this is inferred fr | 99 | 1 |
|
x-postman-request
vendor |
`x-postman-request` appears on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. It sits in the `x-postman-` namespace, so its meaning is defined by postman tooling ra | 99 | 3 |
| x-typelizer | `x-typelizer` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 99 | 1 |
|
x-ms-external
vendor |
`x-ms-external` appears on schema objects and properties. Its value is a boolean flag. Used by 3 providers across 51 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by m | 98 | 3 |
| x-security | `x-security` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key | 98 | 1 |
| x-tab-id | `x-tab-id` appears on schema objects and properties. Its value is a string. Used by 2 providers across 4 OpenAPI documents. Observed values include `WhatsApp`, `MMS`, `Messenger`, `Viber`. Consistent | 98 | 2 |
| x-enable-objectmeta | `x-enable-objectmeta` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred | 96 | 2 |
| x-apply-to | `x-apply-to` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appears and | 95 | 1 |
| x-max-interval-in-months | `x-max-interval-in-months` appears on schema objects and properties. Its value is an integer. Used by a single provider across 1 OpenAPI document. Observed values include `3`, `1`. Consistent with val | 95 | 1 |
|
x-obmcs-mysql-isDynamic
vendor |
`x-obmcs-mysql-isDynamic` 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 meanin | 94 | 1 |
| x-operation-request-parameters-name | `x-operation-request-parameters-name` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `ListActionsRequestParameters`, `ListAc | 94 | 1 |
| x-cadl-name | `x-cadl-name` appears on schema objects and properties. Its value is a string. Used by a single provider across 5 OpenAPI documents. Observed values include `string[]`, `Rest.ResourceLocation`, `Recor | 93 | 1 |
| x-default-unit | `x-default-unit` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `ms`, `s`, `k`. Consistent with defaults | 93 | 1 |
| x-enable-listmeta | `x-enable-listmeta` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 93 | 2 |
| x-operator-evidence | `x-operator-evidence` appears in the info block. Its value is a structured object. Used by 33 providers across 93 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 93 | 33 |
| x-generated | `x-generated` appears in the info block and at the root of the document. Its value is a string. Used by 34 providers across 89 OpenAPI documents. Observed values include `2026-08-30`, `2026-09-01`, `A | 92 | 34 |
| x-duration | `x-duration` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from | 91 | 1 |
| x-beta | `x-beta` appears on operations. Its value is a boolean flag. Used by 9 providers across 14 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears and | 90 | 9 |
|
x-box-variant
vendor |
`x-box-variant` appears on schema objects and properties. Its value is a string. Used by a single provider across 21 OpenAPI documents. It sits in the `x-box-` namespace, so its meaning is defined by | 90 | 1 |
| x-filename-id | `x-filename-id` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `rest-api-v1.3-campaigns-campaignname-sms-trigger-post`, `res | 88 | 1 |
| x-implements | `x-implements` appears on schema objects and properties. Its value is a list. Used by 6 providers across 14 OpenAPI documents. Observed values include `io.airbyte.api.common.ConfigurableActor`, `org.f | 88 | 6 |
| x-operationVersions | `x-operationVersions` appears on operations. Its value is a list. Used by a single provider across 13 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key a | 87 | 1 |
| x-samples-languages | `x-samples-languages` appears at the root of the document. Its value is a list. Used by 13 providers across 87 OpenAPI documents. Consistent with defaults & examples — this is inferred from where the | 87 | 13 |
|
x-ibm-endpoints
vendor |
`x-ibm-endpoints` appears at the root of the document. Its value is a list. Used by 2 providers across 86 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tooling | 86 | 2 |
| x-rate-limit | `x-rate-limit` appears on operations. Its value is a string. Used by 8 providers across 11 OpenAPI documents. Observed values include `query`, `100 requests/minute per API credential`, `orders`, `500 | 86 | 8 |
| x-readOnly | `x-readOnly` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 4 OpenAPI documents. Consistent with mutability & access — this is inferred from where th | 86 | 2 |
| x-bodyName | `x-bodyName` appears on request bodies. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `request`, `body`, `adSets`, `idsToAppend`. Consistent with | 85 | 1 |
| x-enable-id | `x-enable-id` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 3 OpenAPI documents. Consistent with identity & relationships — this is inferred from wh | 84 | 2 |
| x-qualified-classname | `x-qualified-classname` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `com.curalate.mediaapi.model.api.v1.BookmarkQuery`, ` | 83 | 1 |
| x-resource-id | `x-resource-id` appears on schema objects and properties. Its value is a string. Used by 2 providers across 3 OpenAPI documents. Observed values include `BuyerTaxonomyNodes`, `BuyerTaxonomyNode`, `Err | 83 | 2 |
| x-terraform-id | `x-terraform-id` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with identity & relationships — this is inferre | 82 | 1 |
|
x-aws-signingName
vendor |
`x-aws-signingName` appears in the info block. Its value is a string. Used by 66 providers across 81 OpenAPI documents. It sits in the `x-aws-` namespace, so its meaning is defined by aws tooling rath | 81 | 66 |
| x-fhir-update-create | `x-fhir-update-create` appears on operations. Its value is a boolean flag. Used by 2 providers across 21 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the ke | 81 | 2 |
| x-insert-after | `x-insert-after` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred | 81 | 1 |
| x-source-page | `x-source-page` appears on operations. Its value is a string. Used by 4 providers across 20 OpenAPI documents. Observed values include `https://developer.westernalliancebank.com/s/postman-collection`, | 81 | 4 |
| x-featured | `x-featured` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appe | 80 | 1 |
| x-guidance | `x-guidance` appears in the info block and on operations. Its value is a string. Used by 22 providers across 52 OpenAPI documents. Observed values include `POST a small JSON body (see each operation'' | 80 | 22 |
| x-last-validated | `x-last-validated` appears in the info block. Its value is a string. Used by 26 providers across 80 OpenAPI documents. Observed values include `2026-08-30`, `2026-04-18`, `2026-05-30`, `2026-05-29`. C | 80 | 26 |
| x-validation | `x-validation` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with validation & constraints — this is inferred f | 79 | 1 |
| x-criticality | `x-criticality` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `high`, `medium`. Consistent with data & schema semantics — | 78 | 1 |
| x-passthrough-target | `x-passthrough-target` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `rawls`, `agora`, `cromiam`, `sam`. Consistent with da | 78 | 1 |
|
x-toast-read-only
vendor |
`x-toast-read-only` 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-toast-` namespace, so its meaning is d | 78 | 1 |
|
x-bb-suppressions
vendor |
`x-bb-suppressions` appears on schema objects and properties. Its value is a list. Used by a single provider across 13 OpenAPI documents. It sits in the `x-bb-` namespace, so its meaning is defined by | 77 | 1 |
| x-oneOf | `x-oneOf` appears on schema objects and properties. Its value is a list. Used by 2 providers across 2 OpenAPI documents. Consistent with type system — this is inferred from where the key appears and w | 77 | 2 |
| x-supra-chain-id | `x-supra-chain-id` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with identity & relationships — this is inferred from wh | 77 | 1 |
|
x-apidog
vendor |
`x-apidog` appears on operations. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-apidog-` namespace, so its meaning is defined by apidog tooling ra | 76 | 2 |
| x-convert | `x-convert` appears on operations. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appea | 76 | 2 |
| x-default | `x-default` appears on security schemes. Its value is a string. Used by 27 providers across 67 OpenAPI documents. Observed values include `auth_token`, `null`, `SALSIFY_TOKEN`, `API_KEY`. Consistent w | 76 | 27 |
| x-humanmirror-canonical-bundle | `x-humanmirror-canonical-bundle` appears on operations. Its value is a string. Used by a single provider across 4 OpenAPI documents. Observed values include `https://humanmirror.fr/api/v1/agent/operat | 76 | 1 |
| x-operationId | `x-operationId` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `listAddresses`, `createAddress`, `retrieveAddress`, `updateA | 76 | 1 |
| x-foreign | `x-foreign` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with identity & relationships — this is inferred fro | 74 | 1 |
| x-is-jackson-optional-nullable | `x-is-jackson-optional-nullable` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with type system — this is infer | 74 | 1 |
| x-argyle-decimal-mode | `x-argyle-decimal-mode` appears in the document and on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `fixed`, `vari | 73 | 1 |
| x-200 | `x-200` appears on response objects. Its value is a string. Used by 5 providers across 5 OpenAPI documents. Observed values include `请求成功:`, `Example Response (Over 30 Photos):`, `Esim voucher error:` | 72 | 5 |
| x-MXComponent | `x-MXComponent` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `ISODate`, `LEIIdentifier`, `UUIDv4Identif | 72 | 1 |
| x-quote-probe | `x-quote-probe` appears on operations. Its value is a structured object. Used by a single provider across 5 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 72 | 1 |
| x-client-id | `x-client-id` appears on parameter objects. Its value is a structured object. Used by 25 providers across 70 OpenAPI documents. Consistent with identity & relationships — this is inferred from where t | 71 | 25 |
| x-error | `x-error` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 10 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 71 | 2 |
| x-given | `x-given` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key ap | 71 | 1 |
| x-targetService | `x-targetService` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `metadata`, `metadata-service`, `connectivity`. Consistent | 71 | 1 |
| x-apievangelist-method | `x-apievangelist-method` appears in the info block. Its value is a string. Used by 45 providers across 70 OpenAPI documents. Observed values include `generated`, `derived`, `searched`. Consistent with | 70 | 45 |
|
x-apifox-enum
vendor |
`x-apifox-enum` appears on schema objects and properties and on parameter objects. Its value is a list. Used by 2 providers across 3 OpenAPI documents. It sits in the `x-apifox-` namespace, so its mea | 70 | 2 |
| x-associatedSchema | `x-associatedSchema` appears on tags. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 70 | 1 |
| x-cel-message-0 | `x-cel-message-0` appears on schema objects and properties. Its value is a string. Used by a single provider across 10 OpenAPI documents. Observed values include `spec.skuRef is immutable`, `spec.zone | 70 | 1 |
| x-cel-rule-0 | `x-cel-rule-0` appears on schema objects and properties. Its value is a string. Used by a single provider across 10 OpenAPI documents. Observed values include `self == oldSelf`, `!oldSelf.hasValue() | | 70 | 1 |
|
x-workday-type
vendor |
`x-workday-type` 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-workday-` namespace, so its meaning is defined | 70 | 1 |
| x-relation | `x-relation` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with identity & relationships — this is inferred from where the key appears and | 69 | 1 |
| x-verbose-required | `x-verbose-required` appears on schema objects and properties. It is used as a marker with no value. Used by a single provider across 1 OpenAPI document. Consistent with validation & constraints — thi | 69 | 1 |
| x-allowExtraHeaders | `x-allowExtraHeaders` appears on operations. Its value is a boolean flag. Used by 3 providers across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key | 68 | 3 |
| x-api-evangelist-certified | `x-api-evangelist-certified` appears on operations. Its value is a string. Used by 2 providers across 15 OpenAPI documents. Observed values include `2025-07-16`, `2025-07-20`, `2025-07-18`. Consistent | 68 | 2 |
| x-arrayCheckCount | `x-arrayCheckCount` appears on operations. Its value is a boolean flag. Used by 3 providers across 3 OpenAPI documents. Consistent with size & shape — this is inferred from where the key appears and w | 68 | 3 |
| x-bodyMatchMode | `x-bodyMatchMode` appears on operations. Its value is a string. Used by 3 providers across 3 OpenAPI documents. Observed values include `NONE`, `RAW`. Consistent with data & schema semantics — this is | 68 | 3 |
| x-matchResponseSchema | `x-matchResponseSchema` appears on operations. Its value is a boolean flag. Used by 3 providers across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the ke | 68 | 3 |
| x-argyle-decimal-places | `x-argyle-decimal-places` appears in the document and on schema objects and properties. Its value is an integer. Used by a single provider across 1 OpenAPI document. Observed values include `2`, `4`. | 67 | 1 |
| x-bearer-format | `x-bearer-format` appears on security schemes. Its value is a string. Used by 18 providers across 67 OpenAPI documents. Observed values include `bearer`, `token`. Consistent with type system — this is | 67 | 18 |
| x-VpsaType | `x-VpsaType` appears on schema objects and properties. Its value is a string. Used by a single provider across 4 OpenAPI documents. Observed values include `VPSA Flash Array`, `VPSA Storage Array`, `h | 66 | 1 |
| x-apievangelist-generated | `x-apievangelist-generated` appears in the info block. Its value is a string. Used by 47 providers across 66 OpenAPI documents. Observed values include `true`, `2026-08-02`, `2026-07-19`, `2026-07-18` | 66 | 47 |
| x-is-date | `x-is-date` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with type system — this is inferred from where the k | 66 | 1 |
|
x-okta-parent
vendor |
`x-okta-parent` 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-okta-` namespace, so its meaning is defined by o | 66 | 1 |
| x-quoted | `x-quoted` appears on parameter objects. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key | 66 | 1 |
|
x-ms-arm-id-details
vendor |
`x-ms-arm-id-details` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 19 OpenAPI documents. It sits in the `x-ms-` namespace, so its meanin | 65 | 1 |
| x-apievangelist | `x-apievangelist` appears in the info block. Its value is a structured object. Used by 31 providers across 64 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where t | 64 | 31 |
| x-cohesity-discriminator-details | `x-cohesity-discriminator-details` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with type system — this | 62 | 1 |
| x-discriminator-fields | `x-discriminator-fields` appears on schema objects and properties. Its value is a list. Used by a single provider across 8 OpenAPI documents. Consistent with type system — this is inferred from where | 61 | 1 |
|
x-ms-code-generation-settings
vendor |
`x-ms-code-generation-settings` appears in the info block. Its value is a structured object. Used by a single provider across 61 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is | 61 | 1 |
| x-remove-response | `x-remove-response` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 4 OpenAPI documents. Consistent with data & schema semantics — this is infer | 60 | 1 |
| x-sample-urls | `x-sample-urls` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with defaults & examples — this is inferred from where the key appears and w | 60 | 1 |
| x-terraform-resource-poll-enabled | `x-terraform-resource-poll-enabled` appears on response objects. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with identity & relationships — this is i | 60 | 1 |
Showing 400 of 1950. Use the search to reach the rest.