You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: versions/3.0.md
+30-80Lines changed: 30 additions & 80 deletions
Original file line number
Diff line number
Diff line change
@@ -134,11 +134,7 @@ Field Name | Type | Description
134
134
<aname="oasTags"></a>tags | [[Tag Object](#tagObject)] | A list of tags used by the specification with additional metadata. The order of the tags can be used to reflect on their order by the parsing tools. Not all tags that are used by the [Operation Object](#operationObject) must be declared. The tags that are not declared may be organized randomly or based on the tools' logic. Each tag name in the list MUST be unique.
<aname="oasExtensions"></a>^x- | Any | Allows extensions to the OAS Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
137
+
This object can be extended with [Specification Extensions](#specificationExtensions).
142
138
143
139
#### <aname="oasVersion"></a>OpenAPI Version String
144
140
@@ -165,11 +161,7 @@ Field Name | Type | Description
165
161
<aname="infoLicense"></a>license | [License Object](#licenseObject) | The license information for the exposed API.
166
162
<aname="infoVersion"></a>version | `string` | **Required** Provides the version of the application API (not to be confused with the specification version).
167
163
168
-
##### Patterned Objects
169
-
170
-
Field Pattern | Type | Description
171
-
---|:---:|---
172
-
<aname="infoExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
164
+
This object can be extended with [Specification Extensions](#specificationExtensions).
173
165
174
166
##### Info Object Example:
175
167
@@ -229,11 +221,7 @@ Field Name | Type | Description
229
221
<a name="contactUrl"></a>url | `string` | The URL pointing to the contact information. MUST be in the format of a URL.
230
222
<a name="contactEmail"></a>email | `string` | The email address of the contact person/organization. MUST be in the format of an email address.
231
223
232
-
##### Patterned Objects
233
-
234
-
Field Pattern | Type | Description
235
-
---|:---:|---
236
-
<a name="contactExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
224
+
This object can be extended with [Specification Extensions](#specificationExtensions).
237
225
238
226
##### Contact Object Example:
239
227
@@ -262,11 +250,7 @@ Field Name | Type | Description
262
250
<a name="licenseName"></a>name | `string` | **Required.** The license name used for the API.
263
251
<a name="licenseUrl"></a>url | `string` | A URL to the license used for the API. MUST be in the format of a URL.
264
252
265
-
##### Patterned Objects
266
-
267
-
Field Pattern | Type | Description
268
-
---|:---:|---
269
-
<a name="licenseExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
253
+
This object can be extended with [Specification Extensions](#specificationExtensions).
270
254
271
255
##### License Object Example:
272
256
@@ -309,7 +293,8 @@ The Paths may be empty, due to [ACL constraints](#securityFiltering).
309
293
Field Pattern | Type | Description
310
294
---|:---:|---
311
295
<a name="pathsPath"></a>/{path} | [Path Item Object](#pathItemObject) | A relative path to an individual endpoint. The field name MUST begin with a slash. The path is appended to the [`basePath`](#oasBasePath) in order to construct the full URL. [Path templating](#pathTemplating) is allowed.
312
-
<a name="pathsExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
296
+
297
+
This object can be extended with [Specification Extensions](#specificationExtensions).
313
298
314
299
##### Paths Object Example
315
300
@@ -378,11 +363,8 @@ Field Name | Type | Description
378
363
<a name="pathItemSchemes"></a>schemes | [`string`] | The transfer protocol of the API. Values MUST be from the list: `"http"`, `"https"`, `"ws"`, `"wss"`. This optional value will override the top-level [schemes](#oasSchemes) if present. If the `schemes` is not included, the default scheme to be used is the one used to access the OpenAPI definition itself.
379
364
<a name="pathItemParameters"></a>parameters | [[Parameter Object](#parameterObject) <span>|</span> [Reference Object](#referenceObject)] | A list of parameters that are applicable for all the operations described under this path. These parameters can be overridden at the operation level, but cannot be removed there. The list MUST NOT include duplicated parameters. A unique parameter is defined by a combination of a [name](#parameterName) and [___location](#parameterIn). The list can use the [Reference Object](#referenceObject) to link to parameters that are defined at the [OpenAPI Object's parameters](#oasParameters).
380
365
381
-
##### Patterned Fields
382
366
383
-
Field Pattern | Type | Description
384
-
---|:---:|---
385
-
<a name="pathItemExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
367
+
This object can be extended with [Specification Extensions](#specificationExtensions).
386
368
387
369
##### Path Item Object Example
388
370
@@ -489,11 +471,7 @@ Field Name | Type | Description
489
471
<a name="operationBasePath"></a>basePath | `string` | The base path on which the API is served, which is relative to the [`host`](#pathItemHost). This optional value will override the top-level [basePath](#oasBasePath) or path item-level [basePath](#oasPathItemBasePath) if present. If it is not included, the API is served directly under the `host`. The value MUST start with a leading slash (`/`). The `basePath` does not support [path templating](#pathTemplating).
490
472
<a name="operationSchemes"></a>schemes | [`string`] | The transfer protocol of the API. Values MUST be from the list: `"http"`, `"https"`, `"ws"`, `"wss"`. This optional value will override the top-level [schemes](#oasSchemes) or path-item level [schemes](#pathItemSchemes) if present. If the `schemes` is not included, the default scheme to be used is the one used to access the OpenAPI definition itself.
491
473
492
-
##### Patterned Objects
493
-
494
-
Field Pattern | Type | Description
495
-
---|:---:|---
496
-
<a name="operationExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
474
+
This object can be extended with [Specification Extensions](#specificationExtensions).
497
475
498
476
##### Operation Object Example
499
477
@@ -613,11 +591,7 @@ Field Name | Type | Description
613
591
<a name="externalDocDescription"></a>description | `string` | A short description of the target documentation. [CommonMark syntax](http://spec.commonmark.org/) can be used for rich text representation.
614
592
<a name="externalDocUrl"></a>url | `string` | **Required.** The URL for the target documentation. Value MUST be in the format of a URL.
615
593
616
-
##### Patterned Objects
617
-
618
-
Field Pattern | Type | Description
619
-
---|:---:|---
620
-
<a name="externalDocExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
594
+
This object can be extended with [Specification Extensions](#specificationExtensions).
621
595
622
596
##### External Documentation Object Example
623
597
@@ -658,12 +632,7 @@ Field Name | Type | Description
658
632
<a name="parameterDeprecated"></a> deprecated | `boolean` | Specifies that a parameter is deprecated and should be transitioned out of usage.
659
633
<a name="parameterSchema"></a>schema | [Schema Object](#schemaObject) | The schema defining the type used for the parameter.
660
634
661
-
662
-
##### Patterned Fields
663
-
Field Pattern | Type | Description
664
-
---|:---:|---
665
-
<a name="parameterExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
666
-
635
+
This object can be extended with [Specification Extensions](#specificationExtensions).
667
636
668
637
##### Parameter Object Examples
669
638
@@ -1011,11 +980,7 @@ Field Name | Type | Description
1011
980
<a name="itemsEnum"></a>enum | [*] | See http://json-schema.org/latest/json-schema-validation.html#anchor76.
1012
981
<a name="itemsMultipleOf"></a>multipleOf | `number` | See http://json-schema.org/latest/json-schema-validation.html#anchor14.
1013
982
1014
-
##### Patterned Objects
1015
-
1016
-
Field Pattern | Type | Description
1017
-
---|:---:|---
1018
-
<a name="itemsExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
983
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1019
984
1020
985
##### Items Object Examples
1021
986
@@ -1076,9 +1041,10 @@ It can be used to cover undeclared responses.
1076
1041
Field Pattern | Type | Description
1077
1042
---|:---:|---
1078
1043
<a name="responsesCode"></a>[HTTP Status Code](#httpCodes) | [Response Object](#responseObject) <span>|</span> [Reference Object](#referenceObject) | Any [HTTP status code](#httpCodes) can be used as the property name (one property per HTTP status code). Describes the expected response for that HTTP status code. [Reference Object](#referenceObject) can be used to link to a response that is defined at the [OpenAPI Object's responses](#oasResponses) section. This field must quoted for compatibility between JSON and YAML (i.e. "200"), and may contain the uppercase character, `X` to designate a wildcard, such as `2XX` to represent all response codes between `[200-299]`.
1079
-
<a name="responsesExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
1080
1044
1081
1045
1046
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1047
+
1082
1048
##### Responses Object Example
1083
1049
1084
1050
A 200 response for successful operation and a default response for others (implying an error):
@@ -1140,10 +1106,11 @@ Field Name | Type | Description
1140
1106
Field Pattern | Type | Description
1141
1107
---|:---:|---
1142
1108
<a name="representations"></a>`*` | [Schema Object](#schemaObject)<span>|</span> [Reference Object](#referenceObject) | A schema describing the response value for a specific `Content-Type`
1143
-
<a name="responseExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
1144
1109
1145
1110
Representations may take the form of a wildcard (`*`) to designate any `Content-Type`, or a regular expression for matching a specific type
1146
1111
1112
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1113
+
1147
1114
##### Response Object Examples
1148
1115
1149
1116
Response of an array of a complex type:
@@ -1266,7 +1233,8 @@ A container for possible out-of band callbacks from an operation. A callback may
1266
1233
Field Pattern | Type | Description
1267
1234
---|:---:|---
1268
1235
<a name="responseName"></a>Callback name | [Callback Operation Object](#operationObject) <span>|</span> [Operation Object](#operationObject) | An operation object used to define a callback payload structure
1269
-
<a name="responsesExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
1236
+
1237
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1270
1238
1271
1239
1272
1240
##### Callback Object Example
@@ -1391,7 +1359,8 @@ operationId | string | the name of an _existing_, resolvable OAS operation, as d
1391
1359
parameters | Link Parameters Object | an Object representing parameters to pass to an operation as specified with `operationId` or identified via `href`.
1392
1360
headers | Link Headers Object | an Object representing headers to pass to the linked resource.
1393
1361
description | string | a description of the link, supports [CommonMark syntax](http://spec.commonmark.org/).
1394
-
^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
1362
+
1363
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1395
1364
1396
1365
Locating a linked resource may be performed by either a `href` or `operationId`.
1397
1366
In the case of an `operationId`, it must be unique and resolved in the scope of the OAS document.
@@ -1802,11 +1771,7 @@ Field Name | Type | Description
1802
1771
<a name="headerEnum"></a>enum | [*] | See http://json-schema.org/latest/json-schema-validation.html#anchor76.
1803
1772
<a name="headerMultipleOf"></a>multipleOf | `number` | See http://json-schema.org/latest/json-schema-validation.html#anchor14.
1804
1773
1805
-
##### Patterned Objects
1806
-
1807
-
Field Pattern | Type | Description
1808
-
---|:---:|---
1809
-
<a name="headerExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
1774
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1810
1775
1811
1776
##### Header Object Example
1812
1777
@@ -1836,10 +1801,7 @@ Field Name | Type | Description
1836
1801
<a name="tagDescription"></a>description | `string` | A short description for the tag. [CommonMark syntax](http://spec.commonmark.org/) can be used for rich text representation.
1837
1802
<a name="tagExternalDocs"></a>externalDocs | [External Documentation Object](#externalDocumentationObject) | Additional external documentation for this tag.
1838
1803
1839
-
##### Patterned Fields
1840
-
Field Pattern | Type | Description
1841
-
---|:---:|---
1842
-
<a name="tagExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
1804
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1843
1805
1844
1806
##### Tag Object Example
1845
1807
@@ -2013,11 +1975,7 @@ Field Name | Type | Description
2013
1975
<a name="schemaExamples"></a>examples | Any | An array of free-formed properties to include examples for this schema.
2014
1976
<a name="schemaDeprecated"></a> deprecated | `boolean` | Specifies that a schema is deprecated and should be transitioned out of usage.
2015
1977
2016
-
##### Patterned Objects
2017
-
2018
-
Field Pattern | Type | Description
2019
-
---|:---:|---
2020
-
<a name="schemaExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
1978
+
This object can be extended with [Specification Extensions](#specificationExtensions).
2021
1979
2022
1980
###### Composition and Inheritance (Polymorphism)
2023
1981
@@ -2419,11 +2377,7 @@ Field Name | Type | Description
2419
2377
<a name="xmlAttribute"></a>attribute | `boolean` | Declares whether the property definition translates to an attribute instead of an element. Default value is `false`.
2420
2378
<a name="xmlWrapped"></a>wrapped | `boolean` | MAY be used only for an array definition. Signifies whether the array is wrapped (for example, `<books><book/><book/></books>`) or unwrapped (`<book/><book/>`). Default value is `false`. The definition takes effect only when defined alongside `type` being `array` (outside the `items`).
2421
2379
2422
-
##### Patterned Objects
2423
-
2424
-
Field Pattern | Type | Description
2425
-
---|:---:|---
2426
-
<a name="xmlExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
2380
+
This object can be extended with [Specification Extensions](#specificationExtensions).
2427
2381
2428
2382
##### XML Object Examples
2429
2383
@@ -2992,11 +2946,7 @@ Field Name | Type | Validity | Description
2992
2946
<a name="securitySchemeTokenUrl"></a>tokenUrl | `string` | `oauth2` (`"password"`, `"application"`, `"accessCode"`) | **Required.** The token URL to be used for this flow. This SHOULD be in the form of a URL.
2993
2947
<a name="securitySchemeScopes"></a>scopes | [Scopes Object](#scopesObject) | `oauth2` | **Required.** The available scopes for the OAuth2 security scheme.
2994
2948
2995
-
##### Patterned Fields
2996
-
2997
-
Field Name | Type | Description
2998
-
---|:---:|---
2999
-
<a name="securitySchemeExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
2949
+
This object can be extended with [Specification Extensions](#specificationExtensions).
3000
2950
3001
2951
##### Security Scheme Object Example
3002
2952
@@ -3061,11 +3011,7 @@ Field Pattern | Type | Description
3061
3011
---|:---:|---
3062
3012
<a name="scopesName"></a>{name} | `string` | Maps between a name of a scope to a short description of it (as the value of the property).
3063
3013
3064
-
##### Patterned Objects
3065
-
3066
-
Field Pattern | Type | Description
3067
-
---|:---:|---
3068
-
<a name="scopesExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
3014
+
This object can be extended with [Specification Extensions](#specificationExtensions).
3069
3015
3070
3016
##### Scopes Object Example
3071
3017
@@ -3129,7 +3075,11 @@ petstore_auth:
3129
3075
3130
3076
While the OpenAPI Specification tries to accommodate most use cases, additional data can be added to extend the specification at certain points.
3131
3077
3132
-
The extensions properties are always prefixed by `"x-"` and can have any valid JSON format value.
3078
+
The extensions properties are implemented as patterned fields that are always prefixed by `"x-"`.
3079
+
3080
+
Field Pattern | Type | Description
3081
+
---|:---:|---
3082
+
<a name="infoExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. Can have any valid JSON format value.
3133
3083
3134
3084
The extensions may or may not be supported by the available tooling, but those may be extended as well to add requested support (if tools are internal or open-sourced).
0 commit comments