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="infoObject"></a>Info Object
144
140
@@ -156,11 +152,7 @@ Field Name | Type | Description
156
152
<aname="infoLicense"></a>license | [License Object](#licenseObject) | The license information for the exposed API.
157
153
<aname="infoVersion"></a>version | `string` | **Required** Provides the version of the application API (not to be confused with the specification version).
158
154
159
-
##### Patterned Objects
160
-
161
-
Field Pattern | Type | Description
162
-
---|:---:|---
163
-
<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.
155
+
This object can be extended with [Specification Extensions](#specificationExtensions).
164
156
165
157
##### Info Object Example:
166
158
@@ -220,11 +212,7 @@ Field Name | Type | Description
220
212
<a name="contactUrl"></a>url | `string` | The URL pointing to the contact information. MUST be in the format of a URL.
221
213
<a name="contactEmail"></a>email | `string` | The email address of the contact person/organization. MUST be in the format of an email address.
222
214
223
-
##### Patterned Objects
224
-
225
-
Field Pattern | Type | Description
226
-
---|:---:|---
227
-
<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.
215
+
This object can be extended with [Specification Extensions](#specificationExtensions).
228
216
229
217
##### Contact Object Example:
230
218
@@ -253,11 +241,7 @@ Field Name | Type | Description
253
241
<a name="licenseName"></a>name | `string` | **Required.** The license name used for the API.
254
242
<a name="licenseUrl"></a>url | `string` | A URL to the license used for the API. MUST be in the format of a URL.
255
243
256
-
##### Patterned Objects
257
-
258
-
Field Pattern | Type | Description
259
-
---|:---:|---
260
-
<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.
244
+
This object can be extended with [Specification Extensions](#specificationExtensions).
261
245
262
246
##### License Object Example:
263
247
@@ -300,7 +284,8 @@ The Paths may be empty, due to [ACL constraints](#securityFiltering).
300
284
Field Pattern | Type | Description
301
285
---|:---:|---
302
286
<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.
303
-
<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.
287
+
288
+
This object can be extended with [Specification Extensions](#specificationExtensions).
304
289
305
290
##### Paths Object Example
306
291
@@ -369,11 +354,8 @@ Field Name | Type | Description
369
354
<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.
370
355
<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).
371
356
372
-
##### Patterned Fields
373
357
374
-
Field Pattern | Type | Description
375
-
---|:---:|---
376
-
<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.
358
+
This object can be extended with [Specification Extensions](#specificationExtensions).
377
359
378
360
##### Path Item Object Example
379
361
@@ -480,11 +462,7 @@ Field Name | Type | Description
480
462
<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).
481
463
<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.
482
464
483
-
##### Patterned Objects
484
-
485
-
Field Pattern | Type | Description
486
-
---|:---:|---
487
-
<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.
465
+
This object can be extended with [Specification Extensions](#specificationExtensions).
488
466
489
467
##### Operation Object Example
490
468
@@ -604,11 +582,7 @@ Field Name | Type | Description
604
582
<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.
605
583
<a name="externalDocUrl"></a>url | `string` | **Required.** The URL for the target documentation. Value MUST be in the format of a URL.
606
584
607
-
##### Patterned Objects
608
-
609
-
Field Pattern | Type | Description
610
-
---|:---:|---
611
-
<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.
585
+
This object can be extended with [Specification Extensions](#specificationExtensions).
612
586
613
587
##### External Documentation Object Example
614
588
@@ -649,12 +623,7 @@ Field Name | Type | Description
649
623
<a name="parameterDeprecated"></a> deprecated | `boolean` | Specifies that a parameter is deprecated and should be transitioned out of usage.
650
624
<a name="parameterSchema"></a>schema | [Schema Object](#schemaObject) | The schema defining the type used for the parameter.
651
625
652
-
653
-
##### Patterned Fields
654
-
Field Pattern | Type | Description
655
-
---|:---:|---
656
-
<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.
657
-
626
+
This object can be extended with [Specification Extensions](#specificationExtensions).
658
627
659
628
##### Parameter Object Examples
660
629
@@ -1002,11 +971,7 @@ Field Name | Type | Description
1002
971
<a name="itemsEnum"></a>enum | [*] | See http://json-schema.org/latest/json-schema-validation.html#anchor76.
1003
972
<a name="itemsMultipleOf"></a>multipleOf | `number` | See http://json-schema.org/latest/json-schema-validation.html#anchor14.
1004
973
1005
-
##### Patterned Objects
1006
-
1007
-
Field Pattern | Type | Description
1008
-
---|:---:|---
1009
-
<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.
974
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1010
975
1011
976
##### Items Object Examples
1012
977
@@ -1067,9 +1032,10 @@ It can be used to cover undeclared responses.
1067
1032
Field Pattern | Type | Description
1068
1033
---|:---:|---
1069
1034
<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]`.
1070
-
<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.
1071
1035
1072
1036
1037
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1038
+
1073
1039
##### Responses Object Example
1074
1040
1075
1041
A 200 response for successful operation and a default response for others (implying an error):
@@ -1131,10 +1097,11 @@ Field Name | Type | Description
1131
1097
Field Pattern | Type | Description
1132
1098
---|:---:|---
1133
1099
<a name="representations"></a>`*` | [Schema Object](#schemaObject)<span>|</span> [Reference Object](#referenceObject) | A schema describing the response value for a specific `Content-Type`
1134
-
<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.
1135
1100
1136
1101
Representations may take the form of a wildcard (`*`) to designate any `Content-Type`, or a regular expression for matching a specific type
1137
1102
1103
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1104
+
1138
1105
##### Response Object Examples
1139
1106
1140
1107
Response of an array of a complex type:
@@ -1257,7 +1224,8 @@ A container for possible out-of band callbacks from an operation. A callback may
1257
1224
Field Pattern | Type | Description
1258
1225
---|:---:|---
1259
1226
<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
1260
-
<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.
1227
+
1228
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1261
1229
1262
1230
1263
1231
##### Callback Object Example
@@ -1382,7 +1350,8 @@ operationId | string | the name of an _existing_, resolvable OAS operation, as d
1382
1350
parameters | Link Parameters Object | an Object representing parameters to pass to an operation as specified with `operationId` or identified via `href`.
1383
1351
headers | Link Headers Object | an Object representing headers to pass to the linked resource.
1384
1352
description | string | a description of the link, supports [CommonMark syntax](http://spec.commonmark.org/).
1385
-
^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.
1353
+
1354
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1386
1355
1387
1356
Locating a linked resource may be performed by either a `href` or `operationId`.
1388
1357
In the case of an `operationId`, it must be unique and resolved in the scope of the OAS document.
@@ -1793,11 +1762,7 @@ Field Name | Type | Description
1793
1762
<a name="headerEnum"></a>enum | [*] | See http://json-schema.org/latest/json-schema-validation.html#anchor76.
1794
1763
<a name="headerMultipleOf"></a>multipleOf | `number` | See http://json-schema.org/latest/json-schema-validation.html#anchor14.
1795
1764
1796
-
##### Patterned Objects
1797
-
1798
-
Field Pattern | Type | Description
1799
-
---|:---:|---
1800
-
<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.
1765
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1801
1766
1802
1767
##### Header Object Example
1803
1768
@@ -1827,10 +1792,7 @@ Field Name | Type | Description
1827
1792
<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.
1828
1793
<a name="tagExternalDocs"></a>externalDocs | [External Documentation Object](#externalDocumentationObject) | Additional external documentation for this tag.
1829
1794
1830
-
##### Patterned Fields
1831
-
Field Pattern | Type | Description
1832
-
---|:---:|---
1833
-
<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.
1795
+
This object can be extended with [Specification Extensions](#specificationExtensions).
1834
1796
1835
1797
##### Tag Object Example
1836
1798
@@ -2004,11 +1966,7 @@ Field Name | Type | Description
2004
1966
<a name="schemaExamples"></a>examples | Any | An array of free-formed properties to include examples for this schema.
2005
1967
<a name="schemaDeprecated"></a> deprecated | `boolean` | Specifies that a schema is deprecated and should be transitioned out of usage.
2006
1968
2007
-
##### Patterned Objects
2008
-
2009
-
Field Pattern | Type | Description
2010
-
---|:---:|---
2011
-
<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.
1969
+
This object can be extended with [Specification Extensions](#specificationExtensions).
2012
1970
2013
1971
###### Composition and Inheritance (Polymorphism)
2014
1972
@@ -2410,11 +2368,7 @@ Field Name | Type | Description
2410
2368
<a name="xmlAttribute"></a>attribute | `boolean` | Declares whether the property definition translates to an attribute instead of an element. Default value is `false`.
2411
2369
<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`).
2412
2370
2413
-
##### Patterned Objects
2414
-
2415
-
Field Pattern | Type | Description
2416
-
---|:---:|---
2417
-
<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.
2371
+
This object can be extended with [Specification Extensions](#specificationExtensions).
2418
2372
2419
2373
##### XML Object Examples
2420
2374
@@ -2983,11 +2937,7 @@ Field Name | Type | Validity | Description
2983
2937
<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.
2984
2938
<a name="securitySchemeScopes"></a>scopes | [Scopes Object](#scopesObject) | `oauth2` | **Required.** The available scopes for the OAuth2 security scheme.
2985
2939
2986
-
##### Patterned Fields
2987
-
2988
-
Field Name | Type | Description
2989
-
---|:---:|---
2990
-
<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.
2940
+
This object can be extended with [Specification Extensions](#specificationExtensions).
2991
2941
2992
2942
##### Security Scheme Object Example
2993
2943
@@ -3052,11 +3002,7 @@ Field Pattern | Type | Description
3052
3002
---|:---:|---
3053
3003
<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).
3054
3004
3055
-
##### Patterned Objects
3056
-
3057
-
Field Pattern | Type | Description
3058
-
---|:---:|---
3059
-
<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.
3005
+
This object can be extended with [Specification Extensions](#specificationExtensions).
3060
3006
3061
3007
##### Scopes Object Example
3062
3008
@@ -3120,7 +3066,11 @@ petstore_auth:
3120
3066
3121
3067
While the OpenAPI Specification tries to accommodate most use cases, additional data can be added to extend the specification at certain points.
3122
3068
3123
-
The extensions properties are always prefixed by `"x-"` and can have any valid JSON format value.
3069
+
The extensions properties are implemented as patterned fields that are always prefixed by `"x-"`.
3070
+
3071
+
Field Pattern | Type | Description
3072
+
---|:---:|---
3073
+
<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.
3124
3074
3125
3075
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