Data & schema semantics
2331 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.
2331 extensions
387830 occurrences
389 vendor-named
Inside this job
Identity & relationships203
Type system182
Validation & constraints114
Naming & aliasing83
Size & shape57
Units & formatting50
Defaults & examples32
Mutability & access21
Ordering & sorting11
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 58 providers across 197 OpenAPI documents. Consistent with type system — this is inferred from where the key | 42994 | 58 |
| x-adpParameterData | `x-adpParameterData` appears on operations and on header objects. Its value is a structured object. Used by 2 providers across 118 OpenAPI documents. Consistent with data & schema semantics — this is | 25528 | 2 |
|
x-ms-discriminator-value
vendor |
`x-ms-discriminator-value` appears on schema objects and properties. Its value is a string. Used by 25 providers across 229 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defin | 16687 | 25 |
|
x-microcks-operation
vendor |
`x-microcks-operation` appears on operations. Its value is a structured object. Used by 291 providers across 1,068 OpenAPI documents. It sits in the `x-microcks-` namespace, so its meaning is defined | 16568 | 291 |
|
x-microcks-default
vendor |
`x-microcks-default` appears on response objects. Its value is a boolean flag. Used by 189 providers across 627 OpenAPI documents. It sits in the `x-microcks-` namespace, so its meaning is defined by | 16412 | 189 |
|
x-ms-enum
vendor |
`x-ms-enum` appears on schema objects and properties. Its value is a structured object. Used by 42 providers across 625 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined b | 9120 | 42 |
| x-cds-type | `x-cds-type` appears on schema objects and properties. Its value is a string. Used by 47 providers across 65 OpenAPI documents. Observed values include `PositiveInteger`, `AmountString`, `URIString`, | 9076 | 47 |
|
x-github
vendor |
`x-github` appears on operations. Its value is a structured object. Used by 7 providers across 14 OpenAPI documents. It sits in the `x-github-` namespace, so its meaning is defined by github tooling r | 8510 | 7 |
| 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-position | `x-position` appears on operations. Its value is an integer. Used by 14 providers across 44 OpenAPI documents. Observed values include `1`, `2`, `3`, `4`. Consistent with ordering & sorting — this is | 6614 | 14 |
| 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-versionadded | `x-versionadded` appears on schema objects and properties and on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `v2.33`, `v2.36`, `v2.3 | 5055 | 1 |
|
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-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-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 19 providers across 42 OpenAPI documents. Consistent with type system — this is inferre | 3671 | 19 |
|
x-ms-parameter-location
vendor |
`x-ms-parameter-location` appears on parameter objects. Its value is a string. Used by 20 providers across 548 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tool | 3478 | 20 |
| 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 53 OpenAPI documents. Consistent with identity & relationships — this is inferred from where the | 3097 | 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-source | `x-source` appears on operations. Its value is a string. Used by 186 providers across 490 OpenAPI documents. Observed values include `https://developer.intuit.com/app/developer/qbo/docs/api/accounting | 2691 | 186 |
|
x-ms-identifiers
vendor |
`x-ms-identifiers` appears on schema objects and properties. It is used as a marker with no value. Used by 9 providers across 248 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is | 2597 | 9 |
|
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 17 providers across 305 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning | 2562 | 17 |
|
x-ms-client-flatten
vendor |
`x-ms-client-flatten` appears on schema objects and properties. Its value is a boolean flag. Used by 17 providers across 369 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defi | 2524 | 17 |
| 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-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-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 16 OpenAPI documents. Observed values include `65feb4244cc9110c`, `2696b7 | 2414 | 8 |
|
x-junction-exhaustive
vendor |
`x-junction-exhaustive` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 22 OpenAPI documents. It sits in the `x-junction-` namespace, so its meaning i | 2199 | 2 |
| 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-enumDescriptions | `x-enumDescriptions` appears on schema objects and properties. Its value is a structured object. Used by 39 providers across 91 OpenAPI documents. Consistent with type system — this is inferred from w | 1947 | 39 |
| 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-ms-error-response
vendor |
`x-ms-error-response` appears on response objects. Its value is a boolean flag. Used by 8 providers across 51 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooli | 1863 | 8 |
| x-akeda-audience | `x-akeda-audience` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `external`. Consistent with data & schema semantics — this | 1844 | 1 |
| x-akeda-module | `x-akeda-module` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `finance`, `core`, `stock`, `crm`. Consistent with data & sc | 1844 | 1 |
|
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-intuit-required | `x-intuit-required` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `Optional`, `Required`, `Conditionall | 1831 | 1 |
| 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-extensible-enum | `x-extensible-enum` appears on schema objects and properties. Its value is a list. Used by 19 providers across 59 OpenAPI documents. Observed values include `[AWS, GCP, AZURE]`, `[ZIP, JAR]`, `[ORGANI | 1763 | 19 |
| x-schema-id | `x-schema-id` appears on schema objects and properties. Its value is a string. Used by 3 providers across 5 OpenAPI documents. Observed values include `LocalizedStrings`, `HybridIdentifier`, `Address` | 1759 | 3 |
|
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-maturity | `x-maturity` appears on operations and on parameter objects. Its value is a list. Used by 2 providers across 37 OpenAPI documents. Observed values include `STABLE_OGC`, `DRAFT_OGC`, `STABLE_LDPROXY`, | 1594 | 2 |
| x-enumNames | `x-enumNames` appears on schema objects and properties. Its value is a list. Used by 24 providers across 62 OpenAPI documents. Consistent with type system — this is inferred from where the key appears | 1553 | 24 |
| x-correlator | `x-correlator` appears on header objects. Its value is a structured object. Used by 6 providers across 108 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 1482 | 6 |
| 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-enum-varnames | `x-enum-varnames` appears on schema objects and properties. Its value is a list. Used by 76 providers across 135 OpenAPI documents. Observed values include `['UserFilterSelf']`, `['ApiKeyScopeRead', ' | 1448 | 76 |
|
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-struct | `x-struct` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `null`, `Elixir.ControlWeb.V1.Specs.PreviewTemp | 1407 | 1 |
| x-enum-descriptions | `x-enum-descriptions` appears on schema objects and properties. Its value is a structured object. Used by 34 providers across 69 OpenAPI documents. Consistent with type system — this is inferred from | 1387 | 34 |
| x-accepts | `x-accepts` appears on operations. Its value is a string. Used by 10 providers across 25 OpenAPI documents. Observed values include `application/json`, `application/yaml`. Consistent with data & schem | 1377 | 10 |
|
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 10 providers across 168 OpenAPI documents. It sits in the `x-ms-` namespace, so | 1308 | 10 |
|
x-ms-mutability
vendor |
`x-ms-mutability` appears on schema objects and properties. Its value is a list. Used by 11 providers across 182 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms to | 1305 | 11 |
| x-evidence | `x-evidence` appears on operations and in the info block. Its value is a structured object. Used by 50 providers across 503 OpenAPI documents. Consistent with data & schema semantics — this is inferre | 1260 | 50 |
| 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-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-name | `x-name` appears on request bodies. Its value is a string. Used by 15 providers across 35 OpenAPI documents. Observed values include `request`, `model`, `publishParameters`, `body`. Consistent with na | 1185 | 15 |
|
x-ms-parameter-grouping
vendor |
`x-ms-parameter-grouping` appears on parameter objects. Its value is a structured object. Used by 3 providers across 21 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined b | 1140 | 3 |
| 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-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-stackit-authorization | `x-stackit-authorization` appears on operations. Its value is a structured object. Used by a single provider across 51 OpenAPI documents. Consistent with data & schema semantics — this is inferred fro | 1029 | 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-version | `x-version` appears on operations. Its value is a string. Used by 50 providers across 58 OpenAPI documents. Observed values include `1`, `2`, `3`, `5`. Consistent with data & schema semantics — this i | 1013 | 50 |
| 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-audience | `x-audience` appears on operations. Its value is a string. Used by 31 providers across 108 OpenAPI documents. Observed values include `public`, `business-unit-internal`, `external-public`, `external-p | 943 | 31 |
|
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-go-type | `x-go-type` appears on schema objects and properties. Its value is a string. Used by 37 providers across 48 OpenAPI documents. Observed values include `uint32`, `uint64`, `int64`, `float64`. Consisten | 935 | 37 |
| 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-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-stability | `x-stability` appears on schema objects and properties. Its value is a string. Used by 5 providers across 8 OpenAPI documents. Observed values include `provisional`, `stable`, `experimental`, `beta`. | 788 | 5 |
| 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-immutable | `x-immutable` appears on schema objects and properties. Its value is a boolean flag. Used by 4 providers across 5 OpenAPI documents. Consistent with mutability & access — this is inferred from where t | 725 | 4 |
| x-adpOperationData | `x-adpOperationData` appears on operations. Its value is a structured object. Used by 2 providers across 118 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where th | 724 | 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-adpPathData | `x-adpPathData` appears on path items. Its value is a structured object. Used by 2 providers across 118 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key | 706 | 2 |
| 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-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-generated | `x-generated` appears on operations. Its value is a boolean flag. Used by 41 providers across 99 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appear | 647 | 41 |
| x-protectedValue | `x-protectedValue` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 10 OpenAPI documents. Consistent with data & schema semantics — this is infer | 644 | 1 |
| x-confighub-where | `x-confighub-where` 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 i | 640 | 1 |
| 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-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-ms-request-id
vendor |
`x-ms-request-id` appears on header objects and on operations. Its value is a structured object. Used by 4 providers across 25 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is de | 612 | 4 |
|
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-ms-enum-flags
vendor |
`x-ms-enum-flags` appears on schema objects and properties. Its value is a structured object. Used by 13 providers across 33 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defi | 599 | 13 |
| 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-schema-direction | `x-schema-direction` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `output`, `any`, `input`. Consistent | 596 | 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-intuit-default | `x-intuit-default` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `false`, `This Fiscal Year-to-date`, ` | 553 | 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-ms-azure-resource
vendor |
`x-ms-azure-resource` appears on schema objects and properties. Its value is a boolean flag. Used by 13 providers across 217 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defi | 549 | 13 |
| 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-content-type | `x-content-type` appears on operations. Its value is a string. Used by 11 providers across 22 OpenAPI documents. Observed values include `application/json`, `multipart/form-data`, `application/x-www-f | 533 | 11 |
| x-isnullable | `x-isnullable` appears on schema objects and properties. Its value is a boolean flag. Used by 5 providers across 5 OpenAPI documents. Consistent with type system — this is inferred from where the key | 519 | 5 |
| 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-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-operation-settings | `x-operation-settings` appears on operations. Its value is a structured object. Used by 7 providers across 24 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where t | 513 | 7 |
| 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-graphql-type | `x-graphql-type` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `RTTranslation`, `RTTimeRange`, `RTTripDe | 506 | 1 |
| 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-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-gtm-dangerous | `x-gtm-dangerous` appears on operations. Its value is a boolean flag. Used by a single provider across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the ke | 457 | 1 |
| x-gtm-entity | `x-gtm-entity` appears on operations. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `linkedin_accounts`, `linkedin_scraping`, `linkedin_enrichmen | 457 | 1 |
| x-gtm-envelope | `x-gtm-envelope` appears on operations. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `action`, `search`, `get`, `metrics`. Consistent with data | 457 | 1 |
| x-gtm-mass-action | `x-gtm-mass-action` appears on operations. Its value is a boolean flag. Used by a single provider across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 457 | 1 |
| x-gtm-operation | `x-gtm-operation` appears on operations. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `action`, `search`, `get`, `metrics`. Consistent with data | 457 | 1 |
| x-gtm-schedule-required | `x-gtm-schedule-required` appears on operations. Its value is a boolean flag. Used by a single provider across 3 OpenAPI documents. Consistent with validation & constraints — this is inferred from whe | 457 | 1 |
| x-gtm-step-eligible | `x-gtm-step-eligible` appears on operations. Its value is a boolean flag. Used by a single provider across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where th | 457 | 1 |
| x-gtm-tool-class | `x-gtm-tool-class` appears on operations. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `typical`, `trivial`, `complex`. Consistent with type sys | 457 | 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-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-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-additionalPropertiesName | `x-additionalPropertiesName` appears on schema objects and properties. Its value is a string. Used by 25 providers across 42 OpenAPI documents. Observed values include `nexset_attribute_name`, `db_col | 427 | 25 |
| 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-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-ms-client-request-id
vendor |
`x-ms-client-request-id` appears on header objects and on parameter objects. Its value is a structured object. Used by 6 providers across 20 OpenAPI documents. It sits in the `x-ms-` namespace, so its | 396 | 6 |
| 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-ms-skip-url-encoding
vendor |
`x-ms-skip-url-encoding` appears on parameter objects. Its value is a boolean flag. Used by 9 providers across 171 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms | 392 | 9 |
|
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-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-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-ae-placeholder | `x-ae-placeholder` appears on schema objects and properties. Its value is a boolean flag. Used by 38 providers across 44 OpenAPI documents. Consistent with defaults & examples — this is inferred from | 373 | 38 |
| 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-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 9 OpenAPI documents. Consistent with type system — this is inferred from where the | 352 | 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-aws-operation-name
vendor |
`x-aws-operation-name` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-aws-` namespace, so its meaning is defined by aws tooling rather | 336 | 2 |
| x-field-extra-annotation | `x-field-extra-annotation` appears on schema objects and properties. Its value is a string. Used by 12 providers across 42 OpenAPI documents. Observed values include `@com.fasterxml.jackson.annotation | 336 | 12 |
| 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-filterable | `x-filterable` appears on schema objects and properties and on operations. Its value is a boolean flag. Used by 4 providers across 9 OpenAPI documents. Consistent with data & schema semantics — this i | 330 | 4 |
| x-operator | `x-operator` appears in the info block. Its value is a string. Used by 107 providers across 320 OpenAPI documents. Observed values include `institution`, `tenant`, `institution — every host is under I | 323 | 107 |
| x-commentary-feature-key | `x-commentary-feature-key` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `trackers.agent_api`, `projects.agent_api`, `resea | 320 | 1 |
| 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-refined-from | `x-refined-from` appears at the root of the document. Its value is a list. Used by 15 providers across 312 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 312 | 15 |
|
x-gitlab-tier
vendor |
`x-gitlab-tier` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-gitlab-` namespace, so its meaning is defined by gitlab tooling rat | 310 | 1 |
| x-omitzero | `x-omitzero` appears on schema objects and properties. Its value is a boolean flag. Used by 3 providers across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wher | 304 | 3 |
| 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-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-ms-version
vendor |
`x-ms-version` appears on header objects. Its value is a structured object. Used by 4 providers across 8 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling ra | 297 | 4 |
| x-schema-source | `x-schema-source` appears on response objects. Its value is a string. Used by 3 providers across 3 OpenAPI documents. Observed values include `worked-example`, `sdk`, `documentation`. Consistent with | 295 | 3 |
| x-operation-id-source | `x-operation-id-source` appears on operations. Its value is a string. Used by 11 providers across 96 OpenAPI documents. Observed values include `derived`, `normalized`. Consistent with identity & rela | 289 | 11 |
| 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-bnch-organization | `x-bnch-organization` appears in the document. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `Benchling`. Consistent with data & schema semantics | 287 | 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-intuit-filterable | `x-intuit-filterable` 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 | 284 | 1 |
| 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-zvid-plan-dependent | `x-zvid-plan-dependent` 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 | 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-endpoint-status | `x-endpoint-status` appears on operations. Its value is a string. Used by 12 providers across 12 OpenAPI documents. Observed values include `confirmed`, `modeled`. Consistent with data & schema semant | 270 | 12 |
| x-intuit-operation | `x-intuit-operation` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `GET /v3/company/| 259 |
1 |
|
| x-lune-name | `x-lune-name` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `Inferred vehicle type`, `Logistics site`, | 258 | 1 |
| x-stability-level | `x-stability-level` appears on schema objects and properties and on operations. Its value is a string. Used by 4 providers across 5 OpenAPI documents. Observed values include `beta`, `alpha`, `draft`. | 256 | 4 |
|
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-experimental | `x-experimental` appears on operations. Its value is a boolean flag. Used by 4 providers across 37 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appe | 235 | 4 |
| 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-gtm-paced-bucket | `x-gtm-paced-bucket` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `self_account_sync`, `scraping`, `enrichment`, `messagi | 232 | 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 4 providers across 36 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling | 222 | 4 |
| 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-google-quota
vendor |
`x-google-quota` appears on operations. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-google-` namespace, so its meaning is defined by google tool | 215 | 2 |
| x-operation-name | `x-operation-name` appears on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. Observed values include `GetProperties`, `AddTag`, `DeleteTag`, `CreateAccessToken`. Co | 215 | 3 |
| x-api-key | `x-api-key` appears on schema objects and properties and on parameter objects. Its value is a string. Used by 29 providers across 117 OpenAPI documents. Observed values include `G3VIdNTOjscKbVGPqb8aNM | 213 | 29 |
| x-throttling-tier | `x-throttling-tier` appears on operations. Its value is a string. Used by 4 providers across 16 OpenAPI documents. Observed values include `Unlimited`, `null`. Consistent with data & schema semantics | 212 | 4 |
| 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-apievangelist-source | `x-apievangelist-source` appears in the info block. Its value is a string. Used by 52 providers across 204 OpenAPI documents. Observed values include `https://perfectday.com/wp-json/wp/v2`, `https://a | 204 | 52 |
| 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-typelizer | `x-typelizer` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 4 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 203 | 2 |
| x-allow-parameter-operator | `x-allow-parameter-operator` 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 | 202 | 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-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-regulatory-required | `x-regulatory-required` appears on schema objects and properties. Its value is a list. Used by a single provider across 14 OpenAPI documents. Consistent with validation & constraints — this is inferre | 194 | 1 |
| x-ratelimit-limit | `x-ratelimit-limit` appears on header objects. Its value is a structured object. Used by 14 providers across 25 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 193 | 14 |
|
x-ms-operation-id
vendor |
`x-ms-operation-id` appears on header objects. Its value is a structured object. Used by a single provider across 3 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms | 192 | 1 |
| 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-max-interval-in-months | `x-max-interval-in-months` appears on schema objects and properties. Its value is an integer. Used by 2 providers across 2 OpenAPI documents. Observed values include `3`, `1`. Consistent with validati | 190 | 2 |
| 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-phase | `x-phase` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `setup`, `ideas`, `edit`, `monitoring`. Consistent with data & schema se | 186 | 2 |
| 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-status | `x-status` appears in the info block and on operations. Its value is a string. Used by 35 providers across 101 OpenAPI documents. Observed values include `validated`, `live`, `modeled`, `v0.1`. Consis | 182 | 35 |
| x-umami-audience | `x-umami-audience` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `public`, `internal`, `collect`. Consistent with data & sc | 178 | 1 |
| x-umami-contract | `x-umami-contract` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `explicit`. Consistent with data & schema semantics — this | 178 | 1 |
| x-umami-source | `x-umami-source` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `src/app/api/admin/users/[userId]/2fa/contract.generated.ts` | 178 | 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-validation-rules | `x-validation-rules` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `The `localeCode` is the code of an e | 175 | 1 |
| x-ratelimit-reset | `x-ratelimit-reset` appears on header objects. Its value is a structured object. Used by 11 providers across 21 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 174 | 11 |
| x-original-swagger-version | `x-original-swagger-version` appears at the root of the document. Its value is a string. Used by 48 providers across 171 OpenAPI documents. Observed values include `2.0`. Consistent with naming & alia | 171 | 48 |
| 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 154 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tooling rather than | 167 | 5 |
| x-traitTag | `x-traitTag` appears on tags and in the document. Its value is a boolean flag. Used by 18 providers across 41 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where t | 167 | 18 |
|
x-ms-parameterized-host
vendor |
`x-ms-parameterized-host` appears at the root of the document. Its value is a structured object. Used by 5 providers across 163 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is d | 163 | 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-excluded | `x-excluded` appears on operations. Its value is a boolean flag. Used by 9 providers across 10 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears | 160 | 9 |
|
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-commentary-additional-feature-keys | `x-commentary-additional-feature-keys` appears on operations. It is used as a marker with no value. Used by a single provider across 1 OpenAPI document. Consistent with size & shape — this is inferred | 158 | 1 |
| 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-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-toast-read-only
vendor |
`x-toast-read-only` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-toast-` namespace, so its meaning is define | 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-tool-name | `x-tool-name` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `aidelly_upload_media`, `aidelly_create_media_upload_url`, `aid | 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-setting | `x-setting` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 5 OpenAPI documents. Consistent with data & schema semantics — this is inferred | 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-beta | `x-beta` appears on operations. Its value is a boolean flag. Used by 11 providers across 16 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears and | 147 | 11 |
|
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-description-en | `x-description-en` 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 t | 146 | 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-openai-isConsequential
vendor |
`x-openai-isConsequential` appears on operations. Its value is a boolean flag. Used by 8 providers across 13 OpenAPI documents. It sits in the `x-openai-` namespace, so its meaning is defined by opena | 145 | 8 |
| 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-ratelimit-remaining | `x-ratelimit-remaining` appears on header objects. Its value is a structured object. Used by 15 providers across 24 OpenAPI documents. Consistent with data & schema semantics — this is inferred from w | 144 | 15 |
| x-nestjs_zod-uses-3-point-1-syntax | `x-nestjs_zod-uses-3-point-1-syntax` 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 | 143 | 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-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-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-ibm-configuration
vendor |
`x-ibm-configuration` appears at the root of the document. Its value is a structured object. Used by 4 providers across 137 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defi | 142 | 4 |
| 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-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-required-ability | `x-required-ability` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `account:manage`, `settings:manage`, `settings:read`, ` | 136 | 1 |
| x-hasPayrollUkProblem | `x-hasPayrollUkProblem` appears on operations. Its value is a boolean flag. Used by a single provider across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 135 | 1 |
| x-format | `x-format` appears on schema objects and properties. Its value is a string. Used by 6 providers across 6 OpenAPI documents. Observed values include `int64`, `address`, `decimal`, `+E.164`. Consistent | 134 | 6 |
| 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-external | `x-external` appears 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 where the key appears a | 132 | 2 |
| 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-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-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-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-retryable | `x-retryable` appears on operations. Its value is a boolean flag. Used by a single provider across 7 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key ap | 120 | 1 |
| x-side-effects | `x-side-effects` appears on operations. Its value is a string. Used by a single provider across 7 OpenAPI documents. Observed values include `none`, `device_state_change`, `automation_update`, `create | 120 | 1 |
| x-skill-intent | `x-skill-intent` appears on operations. Its value is a string. Used by a single provider across 7 OpenAPI documents. Observed values include `space.list`, `space.create`, `space.name.update`, `device. | 120 | 1 |
| x-bpx-media | `x-bpx-media` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `image`, `video`, `audio`. Consistent with d | 119 | 1 |
| 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-sensitive | `x-sensitive` appears on schema objects and properties. Its value is a boolean flag. Used by 5 providers across 20 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wh | 119 | 5 |
| x-adpSpecData | `x-adpSpecData` appears at the root of the document. Its value is a structured object. Used by 2 providers across 118 OpenAPI documents. Consistent with data & schema semantics — this is inferred from | 118 | 2 |
| x-apievangelist-product | `x-apievangelist-product` appears in the info block. Its value is a string. Used by 2 providers across 118 OpenAPI documents. Observed values include `ADP Workforce Now (hcm-offrg-wfn)`. Consistent wi | 118 | 2 |
| x-apievangelist-resource-path | `x-apievangelist-resource-path` appears in the info block. Its value is a string. Used by 2 providers across 118 OpenAPI documents. Observed values include `benefits/beneficiaries/v1/beneficiaries`, ` | 118 | 2 |
|
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-bc-throttle-key
vendor |
`x-bc-throttle-key` appears on operations and on path items. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-bc-` namespace, so its meaning is defined by | 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-api-id | `x-api-id` appears in the info block. Its value is a string. Used by 44 providers across 110 OpenAPI documents. Observed values include `TMF931`, `sap-concur-expense-report-v4`, `5ca54741-8f62-4aad-ab | 111 | 44 |
| 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-modeled | `x-modeled` appears on operations. Its value is a boolean flag. Used by 23 providers across 29 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears | 109 | 23 |
| 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-coverage-cat-surface | `x-coverage-cat-surface` appears on operations. Its value is a string. Used by a single provider across 4 OpenAPI documents. Observed values include `consumer`, `operator`, `full`. Consistent with dat | 108 | 1 |
| 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-ms-external
vendor |
`x-ms-external` appears on schema objects and properties. Its value is a boolean flag. Used by 6 providers across 54 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by m | 103 | 6 |
| 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-products | `x-products` appears on operations and at the root of the document. Its value is a list. Used by 2 providers across 40 OpenAPI documents. Observed values include `CDP`, `ALTUS,CDP`. Consistent with da | 102 | 2 |
| 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-camara-commonalities | `x-camara-commonalities` appears in the info block. Its value is a number. Used by 7 providers across 100 OpenAPI documents. Observed values include `0.6`, `0.4.0`, `0.5`, `tbd`. Consistent with data | 100 | 7 |
| 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-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-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-ms-arm-id-details
vendor |
`x-ms-arm-id-details` appears on schema objects and properties. Its value is a structured object. Used by 5 providers across 23 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is d | 95 | 5 |
|
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-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-fb-entity | `x-fb-entity` appears on parameter objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `asset`, `vault_account`. Consistent with identity & rel | 93 | 1 |
| x-multi-segment | `x-multi-segment` appears on operations and on parameter objects. Its value is a boolean flag. Used by 3 providers across 5 OpenAPI documents. Consistent with data & schema semantics — this is inferre | 93 | 3 |
| 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-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-samples-languages | `x-samples-languages` appears at the root of the document. Its value is a list. Used by 14 providers across 89 OpenAPI documents. Consistent with defaults & examples — this is inferred from where the | 89 | 14 |
| x-default | `x-default` appears on security schemes. Its value is a string. Used by 28 providers across 68 OpenAPI documents. Observed values include `auth_token`, `null`, `SALSIFY_TOKEN`, `API_KEY`. Consistent w | 88 | 28 |
| 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-rate-limit | `x-rate-limit` appears on operations. Its value is a string. Used by 10 providers across 13 OpenAPI documents. Observed values include `query`, `100 requests/minute per API credential`, `orders`, `500 | 88 | 10 |
| 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-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-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-eov-operation-handler | `x-eov-operation-handler` appears on operations. Its value is a string. Used by 2 providers across 3 OpenAPI documents. Observed values include `app`, `organization/businessEntities`, `organization/em | 85 | 2 |
| x-abstract | `x-abstract` appears on schema objects and properties. Its value is a boolean flag. Used by 11 providers across 17 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wh | 84 | 11 |
| 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-guidance | `x-guidance` appears in the info block and on operations. Its value is a string. Used by 25 providers across 56 OpenAPI documents. Observed values include `POST a small JSON body (see each operation'' | 84 | 25 |
| x-intuit-type | `x-intuit-type` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `CurrencyRefType`, `IdType`, `number`, `A | 83 | 1 |
| 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-implements | `x-implements` appears on schema objects and properties. Its value is a list. Used by 5 providers across 13 OpenAPI documents. Observed values include `org.folio.innreach.domain.dto.InnReachResponseDa | 82 | 5 |
| 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-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-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-stackit-logging | `x-stackit-logging` 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 inferr | 80 | 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`, `low`. Consistent with data & schema seman | 79 | 1 |
| x-MXComponent | `x-MXComponent` appears on schema objects and properties. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `ISODate`, `LEIIdentifier`, `UUIDv4Identifier`, | 78 | 2 |
| 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-scala-type | `x-scala-type` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `java.time.Instant`, `java.time.LocalDate`, | 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-last-validated | `x-last-validated` appears in the info block. Its value is a string. Used by 25 providers across 77 OpenAPI documents. Observed values include `2026-08-30`, `2026-04-18`, `2026-05-30`, `2026-05-29`. C | 77 | 25 |
| x-metasysEnum | `x-metasysEnum` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `objectTypeEnumSet`, `attributeEnumSet`, ` | 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 |
Showing 400 of 2331. Use the search to reach the rest.
Work with this as data
Every extension here is available over the APIs.io API and to AI agents over MCP. OpenAPI Extensions is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.