Security
125 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.
125 extensions
26483 occurrences
31 vendor-named
The extensions
| Extension | What it appears to do | Uses | Providers |
|---|---|---|---|
| x-fapi-interaction-id | `x-fapi-interaction-id` appears on header objects. Its value is a structured object. Used by 81 providers across 175 OpenAPI documents. Consistent with security — this is inferred from where the key a | 10518 | 81 |
|
x-atlassian-oauth2-scopes
vendor |
`x-atlassian-oauth2-scopes` appears on operations. Its value is a list. Used by a single provider across 97 OpenAPI documents. It sits in the `x-atlassian-` namespace, so its meaning is defined by atl | 1929 | 1 |
|
x-atlassian-connect-scope
vendor |
`x-atlassian-connect-scope` appears on operations. Its value is a string. Used by a single provider across 95 OpenAPI documents. It sits in the `x-atlassian-` namespace, so its meaning is defined by a | 1468 | 1 |
| x-jws-signature | `x-jws-signature` appears on header objects. Its value is a structured object. Used by 30 providers across 91 OpenAPI documents. Consistent with security — this is inferred from where the key appears | 1420 | 30 |
| x-permissions | `x-permissions` appears on operations. Its value is a list. Used by 7 providers across 22 OpenAPI documents. Observed values include `null`. Consistent with security — this is inferred from where the | 1130 | 7 |
| x-rolesRequirements | `x-rolesRequirements` appears on operations. Its value is a list. Used by a single provider across 2 OpenAPI documents. Consistent with security — this is inferred from where the key appears and what | 958 | 1 |
| x-scopes | `x-scopes` appears on operations. Its value is a list. Used by 54 providers across 66 OpenAPI documents. Observed values include `read:policy`. Consistent with security — this is inferred from where t | 893 | 54 |
| x-permission | `x-permission` appears on operations. Its value is a structured object. Used by 7 providers across 10 OpenAPI documents. Consistent with security — this is inferred from where the key appears and what | 732 | 7 |
| x-ai-role | `x-ai-role` appears on operations. Its value is a string. Used by a single provider across 19 OpenAPI documents. Observed values include `marketing_automation_specialist`, `customer_support_specialist | 634 | 1 |
| x-oauth-scopes | `x-oauth-scopes` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears and what it car | 559 | 1 |
| x-api-token-group | `x-api-token-group` appears on operations. Its value is a list. Used by 4 providers across 4 OpenAPI documents. Consistent with security — this is inferred from where the key appears and what it carri | 544 | 4 |
| x-cfPermissionsRequired | `x-cfPermissionsRequired` appears on operations. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. Consistent with security — this is inferred from where the key appear | 530 | 2 |
| x-encrypted | `x-encrypted` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 3 OpenAPI documents. Consistent with security — this is inferred from where the key appe | 523 | 2 |
| x-entur-permissions | `x-entur-permissions` appears on operations. Its value is a structured object. Used by a single provider across 10 OpenAPI documents. Consistent with security — this is inferred from where the key app | 503 | 1 |
| x-app-permission | `x-app-permission` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `ReadAccounts`, `EditAccounts`, `TeamMessaging`, `EditExte | 446 | 1 |
| x-required-scope | `x-required-scope` appears on operations. Its value is a string. Used by 5 providers across 5 OpenAPI documents. Observed values include `read`, `write`, `sites:write`, `agent:write`. Consistent with | 322 | 5 |
| x-acl | `x-acl` appears on operations. Its value is a list. Used by a single provider across 15 OpenAPI documents. Consistent with security — this is inferred from where the key appears and what it carries, n | 280 | 1 |
| x-required-permissions | `x-required-permissions` appears on operations. Its value is a structured object. Used by a single provider across 17 OpenAPI documents. Consistent with security — this is inferred from where the key | 268 | 1 |
|
x-ms-secret
vendor |
`x-ms-secret` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 62 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined | 259 | 1 |
| x-user-permission | `x-user-permission` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `ConfigureEmergencyMaps`, `ReadExtensions`, `Meetings`, ` | 236 | 1 |
| x-drata-permissions | `x-drata-permissions` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears and what i | 197 | 1 |
|
x-ibm-dx-security-user-roles
vendor |
`x-ibm-dx-security-user-roles` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tool | 189 | 1 |
| x-appdirect-required-scopes | `x-appdirect-required-scopes` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the k | 165 | 1 |
|
x-yba-api-authz
vendor |
`x-yba-api-authz` appears on operations. Its value is a list. Used by 2 providers across 11 OpenAPI documents. It sits in the `x-yba-` namespace, so its meaning is defined by yba tooling rather than b | 165 | 2 |
| x-roles | `x-roles` appears on operations. Its value is a string. Used by 2 providers across 9 OpenAPI documents. Observed values include `account_admin`, `Platform Admin`, `admin`, `Platform Admin, Organizatio | 157 | 2 |
| x-role-requirements | `x-role-requirements` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Viewer or higher`, `Data Manager or higher`, `Admin`, | 146 | 1 |
| x-dct-toolkit-credential-field | `x-dct-toolkit-credential-field` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with security — this is inferre | 128 | 1 |
| x-scope | `x-scope` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `read`, `write`, `read:users`, `read:api_keys`. Consistent with security | 98 | 2 |
| x-fapi-auth-date | `x-fapi-auth-date` appears on parameter objects. Its value is a structured object. Used by 27 providers across 85 OpenAPI documents. Consistent with security — this is inferred from where the key appe | 85 | 27 |
| x-fapi-customer-ip-address | `x-fapi-customer-ip-address` appears on parameter objects. Its value is a structured object. Used by 27 providers across 85 OpenAPI documents. Consistent with security — this is inferred from where th | 85 | 27 |
|
x-obmcs-authz-declarations
vendor |
`x-obmcs-authz-declarations` appears on operations. Its value is a structured object. Used by 3 providers across 17 OpenAPI documents. It sits in the `x-obmcs-` namespace, so its meaning is defined by | 80 | 3 |
| x-byrd-roles | `x-byrd-roles` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears and what it carri | 66 | 1 |
| x-auth | `x-auth` appears on operations. Its value is a string. Used by 2 providers across 5 OpenAPI documents. Observed values include `public`, `trading`, `read`, `authvalue`. Consistent with security — this | 42 | 2 |
| x-ironfang-scopes | `x-ironfang-scopes` appears on operations. Its value is a list. Used by a single provider across 2 OpenAPI documents. Observed values include `[finance:einvoices:read]`, `[finance:einvoices:write]`, ` | 41 | 1 |
|
x-mastercard-api-encrypted
vendor |
`x-mastercard-api-encrypted` appears on operations. Its value is a boolean flag. Used by a single provider across 11 OpenAPI documents. It sits in the `x-mastercard-` namespace, so its meaning is defi | 41 | 1 |
| x-required-acl | `x-required-acl` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Observed values include `[staff, owner, read-only]`, `[owner]`, `[owner, read-only]`, | 35 | 1 |
| x-required-roles | `x-required-roles` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears and what it c | 35 | 1 |
|
x-ibm-permissions
vendor |
`x-ibm-permissions` appears on operations. Its value is a structured object. Used by a single provider across 5 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm t | 29 | 1 |
| x-permission-denied | `x-permission-denied` appears on response objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key | 28 | 1 |
| x-auth-type | `x-auth-type` appears on operations. Its value is a string. Used by a single provider across 5 OpenAPI documents. Observed values include `Application & Application User`, `Application`, `None`. Consi | 26 | 1 |
|
x-ibm-oauth-provider
vendor |
`x-ibm-oauth-provider` appears in the document. Its value is a string. Used by 2 providers across 17 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tooling rath | 24 | 2 |
| x-korbit-permission | `x-korbit-permission` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `readOrders`, `readDeposits`, `readWithdrawals`, `write | 24 | 1 |
|
x-vault-sudo
vendor |
`x-vault-sudo` appears on path items. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-vault-` namespace, so its meaning is defined by vault tooling | 24 | 1 |
|
x-amz-signature
vendor |
`x-amz-signature` appears on schema objects and properties. Its value is a string. Used by 9 providers across 10 OpenAPI documents. It sits in the `x-amz-` namespace, so its meaning is defined by amz | 23 | 9 |
|
x-ms-request-server-encrypted
vendor |
`x-ms-request-server-encrypted` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is d | 23 | 1 |
| x-required-role | `x-required-role` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `team-admin`, `org-admin`, `member`. Consistent with securi | 23 | 1 |
|
x-amz-credential
vendor |
`x-amz-credential` appears on schema objects and properties. Its value is a string. Used by 8 providers across 9 OpenAPI documents. It sits in the `x-amz-` namespace, so its meaning is defined by amz | 22 | 8 |
| x-restricted | `x-restricted` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears and what | 21 | 1 |
| x-api-key-scope | `x-api-key-scope` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `services:read`, `billing:read`, `proxy:read`, `proxy:write | 20 | 1 |
|
x-ms-encryption-scope
vendor |
`x-ms-encryption-scope` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defined by | 18 | 1 |
| x-scope3-semantic-validation | `x-scope3-semantic-validation` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is infer | 18 | 1 |
|
x-vault-unauthenticated
vendor |
`x-vault-unauthenticated` appears on path items. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-vault-` namespace, so its meaning is defined by vau | 18 | 1 |
|
x-ms-encryption-key-sha256
vendor |
`x-ms-encryption-key-sha256` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defin | 17 | 1 |
|
x-vault-createSupported
vendor |
`x-vault-createSupported` appears on path items. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-vault-` namespace, so its meaning is defined by vau | 14 | 1 |
|
x-ms-file-permission-key
vendor |
`x-ms-file-permission-key` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defined | 11 | 1 |
| x-required-scopes | `x-required-scopes` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears and what it | 10 | 1 |
| x-api-key-permissions | `x-api-key-permissions` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears and what | 9 | 1 |
|
x-ms-server-encrypted
vendor |
`x-ms-server-encrypted` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined b | 9 | 1 |
| x-guarded-string | `x-guarded-string` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `true`. Consistent with security — thi | 8 | 1 |
| x-scopes-required-access-tier | `x-scopes-required-access-tier` appears on security schemes. Its value is a structured object. Used by a single provider across 8 OpenAPI documents. Consistent with security — this is inferred from wh | 8 | 1 |
| x-scopeValidate | `x-scopeValidate` appears in the document. Its value is a structured object. Used by a single provider across 6 OpenAPI documents. Consistent with security — this is inferred from where the key appear | 6 | 1 |
| x-secret | `x-secret` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key ap | 6 | 1 |
|
x-vault-displayAttrs
vendor |
`x-vault-displayAttrs` 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-vault-` namespace, so its mean | 6 | 1 |
|
x-amz-server-side-encryption
vendor |
`x-amz-server-side-encryption` appears on header objects. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-amz-` namespace, so its meaning is defined | 5 | 2 |
| x-fapi-financial-id-Param | `x-fapi-financial-id-Param` appears on parameter objects. Its value is a structured object. Used by 4 providers across 5 OpenAPI documents. Consistent with security — this is inferred from where the k | 5 | 4 |
| x-fapi-interaction-id-Param | `x-fapi-interaction-id-Param` appears on parameter objects. Its value is a structured object. Used by 4 providers across 5 OpenAPI documents. Consistent with security — this is inferred from where the | 5 | 4 |
| x-forbid-unknown-cookie | `x-forbid-unknown-cookie` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appear | 5 | 1 |
| x-forbid-unknown-header | `x-forbid-unknown-header` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appear | 5 | 1 |
| x-forbid-unknown-path | `x-forbid-unknown-path` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears | 5 | 1 |
| x-forbid-unknown-query | `x-forbid-unknown-query` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears | 5 | 1 |
| x-app-secret | `x-app-secret` appears on operations and on security schemes. It is used as a marker with no value. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred fro | 4 | 1 |
| x-auth-id-alias | `x-auth-id-alias` appears on security schemes. Its value is a boolean flag. Used by 2 providers across 2 OpenAPI documents. Consistent with security — this is inferred from where the key appears and w | 4 | 2 |
| x-fapi-channel-id | `x-fapi-channel-id` appears on parameter objects. Its value is a structured object. Used by a single provider across 4 OpenAPI documents. Consistent with security — this is inferred from where the key | 4 | 1 |
| x-fapi-customer-ip-address-Param | `x-fapi-customer-ip-address-Param` appears on parameter objects. Its value is a structured object. Used by 3 providers across 4 OpenAPI documents. Consistent with security — this is inferred from wher | 4 | 3 |
| x-fapi-customer-last-logged-time-Param | `x-fapi-customer-last-logged-time-Param` appears on parameter objects. Its value is a structured object. Used by 3 providers across 4 OpenAPI documents. Consistent with security — this is inferred fro | 4 | 3 |
| x-fapi-financial-id | `x-fapi-financial-id` appears in the document. Its value is a structured object. Used by a single provider across 4 OpenAPI documents. Consistent with security — this is inferred from where the key ap | 4 | 1 |
| x-fapi-trace-id | `x-fapi-trace-id` appears on parameter objects. Its value is a structured object. Used by a single provider across 4 OpenAPI documents. Consistent with security — this is inferred from where the key a | 4 | 1 |
| x-USCorePractitionerRole | `x-USCorePractitionerRole` appears on response objects. Its value is a structured object. Used by a single provider across 3 OpenAPI documents. Consistent with security — this is inferred from where t | 3 | 1 |
| x-client-secret | `x-client-secret` appears on security schemes. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `portal-client-secret`, `3586fea59c3ef4d3a829b398a865fb95` | 3 | 2 |
| x-cog-secret | `x-cog-secret` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the ke | 3 | 1 |
| x-wrong-credentials | `x-wrong-credentials` appears on response objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key | 3 | 1 |
| x-allowedTenantIdForRestriction | `x-allowedTenantIdForRestriction` appears in the document. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. Consistent with security — this is inferred from where the | 2 | 2 |
| x-api-permissions | `x-api-permissions` appears on operations. Its value is a list. Used by a single provider across 2 OpenAPI documents. Consistent with security — this is inferred from where the key appears and what it | 2 | 1 |
| x-auth-failed | `x-auth-failed` appears on response objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appea | 2 | 1 |
| x-auth-role | `x-auth-role` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears a | 2 | 1 |
| x-auth-token | `x-auth-token` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with security — this is inferred from where the key appears | 2 | 1 |
| x-auth-user | `x-auth-user` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears a | 2 | 1 |
| x-authorization-signature | `x-authorization-signature` appears on parameter objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with security — this is inferred from where | 2 | 1 |
| x-generate-global-scope | `x-generate-global-scope` appears in the info block. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with security — this is inferred from where the key a | 2 | 1 |
| x-insta-oauth-authenticated | `x-insta-oauth-authenticated` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key ap | 2 | 1 |
| x-is-auth | `x-is-auth` appears on security schemes. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with security — this is inferred from where the key appears and w | 2 | 1 |
| x-legacy-signature | `x-legacy-signature` appears on operations. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with security — this is inferred from where the key appears an | 2 | 1 |
| x-legacy-signature-recommend | `x-legacy-signature-recommend` appears on operations. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with security — this is inferred from where the key | 2 | 1 |
| x-Auth-Token | `x-Auth-Token` appears in the info block. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `{{ACCESS_TOKEN}}`. Consistent with security — this is inf | 1 | 1 |
| x-accelerate-signature | `x-accelerate-signature` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the ke | 1 | 1 |
|
x-ads-role
vendor |
`x-ads-role` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ads-` namespace, so its meaning is defined by ads tooli | 1 | 1 |
| x-allowed-roles | `x-allowed-roles` appears at the root of the document. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears | 1 | 1 |
|
x-amz-acl
vendor |
`x-amz-acl` 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-amz-` namespace, so its meaning is defined by amz to | 1 | 1 |
|
x-amz-server-side-encryption-aws-kms-key-id
vendor |
`x-amz-server-side-encryption-aws-kms-key-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 it | 1 | 1 |
| x-auth-responses | `x-auth-responses` appears at the root of the document. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `&AUTHRESPONSES`. Consistent with security — | 1 | 1 |
| x-availability-scope | `x-availability-scope` appears in the info block. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Swisscom only — requires HLR/VLR signalling suppo | 1 | 1 |
| x-byrd-permissions | `x-byrd-permissions` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appear | 1 | 1 |
| x-encrypted-base64 | `x-encrypted-base64` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where | 1 | 1 |
| x-genesis-vault | `x-genesis-vault` appears at the root of the document. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the | 1 | 1 |
|
x-ibm-dx-operator-entrypoint-roles
vendor |
`x-ibm-dx-operator-entrypoint-roles` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-ibm-` namespace, so its meaning is defined by ib | 1 | 1 |
|
x-ibm-dx-user-auth
vendor |
`x-ibm-dx-user-auth` appears on parameter objects. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tooli | 1 | 1 |
| x-jws-signature-Param | `x-jws-signature-Param` appears on parameter objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the | 1 | 1 |
|
x-ms-acl
vendor |
`x-ms-acl` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling r | 1 | 1 |
|
x-ms-default-encryption-scope
vendor |
`x-ms-default-encryption-scope` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is de | 1 | 1 |
|
x-ms-deny-encryption-scope-override
vendor |
`x-ms-deny-encryption-scope-override` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning | 1 | 1 |
|
x-ms-permissions
vendor |
`x-ms-permissions` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defined by ms t | 1 | 1 |
| x-oauth-error-codes | `x-oauth-error-codes` appears at the root of the document. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where | 1 | 1 |
|
x-obmcs-splat-search-metadata-scope
vendor |
`x-obmcs-splat-search-metadata-scope` appears in the document. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-obmcs-` namespace, so its meaning is define | 1 | 1 |
| x-out-of-scope-note | `x-out-of-scope-note` appears in the info block. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key a | 1 | 1 |
| x-permission-checks | `x-permission-checks` appears in the document. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears and what | 1 | 1 |
| x-qfex-hmac-signature | `x-qfex-hmac-signature` appears on parameter objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the | 1 | 1 |
| x-redlock-auth | `x-redlock-auth` appears on security schemes. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appe | 1 | 1 |
| x-role-system | `x-role-system` appears in the info block. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears | 1 | 1 |
| x-sca-id | `x-sca-id` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears and | 1 | 1 |
| x-sca-required | `x-sca-required` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appear | 1 | 1 |
| x-sca-type | `x-sca-type` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears an | 1 | 1 |
| x-scopeValidateFunc | `x-scopeValidateFunc` appears on security schemes. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `api.middleware.auth.validate_scopes`. Consistent | 1 | 1 |
| x-signature-sha256 | `x-signature-sha256` appears on parameter objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key | 1 | 1 |
| x-tmt-secret | `x-tmt-secret` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the key appears | 1 | 1 |
| x-zapier-auth-scheme-exempt | `x-zapier-auth-scheme-exempt` appears on security schemes. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with security — this is inferred from where the | 1 | 1 |