Jun 30, 2023 · Jun 29, 2023 · Jun 29, 2023 · Jun 29, 2023 · Jun 29, 2023 · Jun 29, 2023
diff --git a/docs/en/docs/advanced/additional-responses.md b/docs/en/docs/advanced/additional-responses.md

 To see what exactly you can include in the responses, you can check these sections in the OpenAPI specification:

 * <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#responsesObject" class="external-link" target="_blank">OpenAPI Responses Object</a>, it includes the `Response Object`.
 * <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#responseObject" class="external-link" target="_blank">OpenAPI Response Object</a>, you can include anything from this directly in each response inside your `responses` parameter. Including `description`, `headers`, `content` (inside of this is that you declare different media types and JSON Schemas), and `links`.
 * <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#responsesObject" class="external-link" target="_blank">OpenAPI Responses Object</a>, it includes the `Response Object`.
 * <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#responseObject" class="external-link" target="_blank">OpenAPI Response Object</a>, you can include anything from this directly in each response inside your `responses` parameter. Including `description`, `headers`, `content` (inside of this is that you declare different media types and JSON Schemas), and `links`.
diff --git a/docs/en/docs/advanced/behind-a-proxy.md b/docs/en/docs/advanced/behind-a-proxy.md

 ```JSON hl_lines="4-8"
 {
    "openapi": "3.0.2",
    "openapi": "3.1.0",
    // More stuff here
    "servers": [
        {

 ```JSON hl_lines="5-7"
 {
    "openapi": "3.0.2",
    "openapi": "3.1.0",
    // More stuff here
    "servers": [
        {
diff --git a/docs/en/docs/advanced/extending-openapi.md b/docs/en/docs/advanced/extending-openapi.md

 * `title`: The OpenAPI title, shown in the docs.
 * `version`: The version of your API, e.g. `2.5.0`.
 * `openapi_version`: The version of the OpenAPI specification used. By default, the latest: `3.0.2`.
 * `description`: The description of your API.
 * `openapi_version`: The version of the OpenAPI specification used. By default, the latest: `3.1.0`.
 * `summary`: A short summary of the API.
 * `description`: The description of your API, this can include markdown and will be shown in the docs.
 * `routes`: A list of routes, these are each of the registered *path operations*. They are taken from `app.routes`.

 !!! info
    The parameter `summary` is available in OpenAPI 3.1.0 and above, supported by FastAPI 0.99.0 and above.

 ## Overriding the defaults

 Using the information above, you can use the same utility function to generate the OpenAPI schema and override each part that you need.

 Then, use the same utility function to generate the OpenAPI schema, inside a `custom_openapi()` function:

 ```Python hl_lines="2  15-20"
 ```Python hl_lines="2  15-21"
 {!../../../docs_src/extending_openapi/tutorial001.py!}
 ```

 ### Modify the OpenAPI schema

 Now you can add the ReDoc extension, adding a custom `x-logo` to the `info` "object" in the OpenAPI schema:

 ```Python hl_lines="21-23"
 ```Python hl_lines="22-24"
 {!../../../docs_src/extending_openapi/tutorial001.py!}
 ```


 It will be generated only once, and then the same cached schema will be used for the next requests.

 ```Python hl_lines="13-1424-25"
 ```Python hl_lines="13-1425-26"
 {!../../../docs_src/extending_openapi/tutorial001.py!}
 ```

 ### Override the method

 Now you can replace the `.openapi()` method with your new function.

 ```Python hl_lines="28"
 ```Python hl_lines="29"
 {!../../../docs_src/extending_openapi/tutorial001.py!}
 ```

diff --git a/docs/en/docs/advanced/openapi-callbacks.md b/docs/en/docs/advanced/openapi-callbacks.md
 There are 2 main differences from a normal *path operation*:

 * It doesn't need to have any actual code, because your app will never call this code. It's only used to document the *external API*. So, the function could just have `pass`.
 * The *path* can contain an <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#key-expression" class="external-link" target="_blank">OpenAPI 3 expression</a> (see more below) where it can use variables with parameters and parts of the original request sent to *your API*.
 * The *path* can contain an <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#key-expression" class="external-link" target="_blank">OpenAPI 3 expression</a> (see more below) where it can use variables with parameters and parts of the original request sent to *your API*.

 ### The callback path expression

 The callback *path* can have an <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#key-expression" class="external-link" target="_blank">OpenAPI 3 expression</a> that can contain parts of the original request sent to *your API*.
 The callback *path* can have an <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#key-expression" class="external-link" target="_blank">OpenAPI 3 expression</a> that can contain parts of the original request sent to *your API*.

 In this case, it's the `str`:

diff --git a/docs/en/docs/advanced/openapi-webhooks.md b/docs/en/docs/advanced/openapi-webhooks.md
 # OpenAPI Webhooks

 There are cases where you want to tell your API **users** that your app could call *their* app (sending a request) with some data, normally to **notify** of some type of **event**.

 This means that instead of the normal process of your users sending requests to your API, it's **your API** (or your app) that could **send requests to their system** (to their API, their app).

 This is normally called a **webhook**.

 ## Webhooks steps

 The process normally is that **you define** in your code what is the message that you will send, the **body of the request**.

 You also define in some way at which **moments** your app will send those requests or events.

 And **your users** define in some way (for example in a web dashboard somewhere) the **URL** where your app should send those requests.

 All the **logic** about how to register the URLs for webhooks and the code to actually send those requests is up to you. You write it however you want to in **your own code**.

 ## Documenting webhooks with **FastAPI** and OpenAPI

 With **FastAPI**, using OpenAPI, you can define the names of these webhooks, the types of HTTP operations that your app can send (e.g. `POST`, `PUT`, etc.) and the request **bodies** that your app would send.

 This can make it a lot easier for your users to **implement their APIs** to receive your **webhook** requests, they might even be able to autogenerate some of their own API code.

 !!! info
    Webhooks are available in OpenAPI 3.1.0 and above, supported by FastAPI `0.99.0` and above.

 ## An app with webhooks

 When you create a **FastAPI** application, there is a `webhooks` attribute that you can use to define *webhooks*, the same way you would define *path operations*, for example with `@app.webhooks.post()`.

 ```Python hl_lines="9-13  36-53"
 {!../../../docs_src/openapi_webhooks/tutorial001.py!}
 ```

 The webhooks that you define will end up in the **OpenAPI** schema and the automatic **docs UI**.

 !!! info
    The `app.webhooks` object is actually just an `APIRouter`, the same type you would use when structuring your app with multiple files.

 Notice that with webhooks you are actually not declaring a *path* (like `/items/`), the text you pass there is just an **identifier** of the webhook (the name of the event), for example in `@app.webhooks.post("new-subscription")`, the webhook name is `new-subscription`.

 This is because it is expected that **your users** would define the actual **URL path** where they want to receive the webhook request in some other way (e.g. a web dashboard).

 ### Check the docs

 Now you can start your app with Uvicorn and go to <a href="http://127.0.0.1:8000/docs" class="external-link" target="_blank">http://127.0.0.1:8000/docs</a>.

 You will see your docs have the normal *path operations* and now also some **webhooks**:

 <img src="/img/tutorial/openapi-webhooks/image01.png">
diff --git a/docs/en/docs/advanced/path-operation-advanced-configuration.md b/docs/en/docs/advanced/path-operation-advanced-configuration.md

 ```JSON hl_lines="22"
 {
    "openapi": "3.0.2",
    "openapi": "3.1.0",
    "info": {
        "title": "FastAPI",
        "version": "0.1.0"
diff --git a/docs/en/docs/img/tutorial/metadata/image01.png b/docs/en/docs/img/tutorial/metadata/image01.png
diff --git a/docs/en/docs/img/tutorial/openapi-webhooks/image01.png b/docs/en/docs/img/tutorial/openapi-webhooks/image01.png
diff --git a/docs/en/docs/tutorial/first-steps.md b/docs/en/docs/tutorial/first-steps.md

 ```JSON
 {
    "openapi": "3.0.2",
    "openapi": "3.1.0",
    "info": {
        "title": "FastAPI",
        "version": "0.1.0"
diff --git a/docs/en/docs/tutorial/metadata.md b/docs/en/docs/tutorial/metadata.md
 | Parameter | Type | Description |
 |------------|------|-------------|
 | `title` | `str` | The title of the API. |
 | `summary` | `str` | A short summary of the API. <small>Available since OpenAPI 3.1.0, FastAPI 0.99.0.</small> |
 | `description` | `str` | A short description of the API. It can use Markdown. |
 | `version` | `string` | The version of the API. This is the version of your own application, not of OpenAPI. For example `2.5.0`. |
 | `terms_of_service` | `str` | A URL to the Terms of Service for the API. If provided, this has to be a URL. |
 | `contact` | `dict` | The contact information for the exposed API. It can contain several fields. <details><summary><code>contact</code> fields</summary><table><thead><tr><th>Parameter</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>name</code></td><td><code>str</code></td><td>The identifying name of the contact person/organization.</td></tr><tr><td><code>url</code></td><td><code>str</code></td><td>The URL pointing to the contact information. MUST be in the format of a URL.</td></tr><tr><td><code>email</code></td><td><code>str</code></td><td>The email address of the contact person/organization. MUST be in the format of an email address.</td></tr></tbody></table></details> |
 | `license_info` | `dict` | The license information for the exposed API. It can contain several fields. <details><summary><code>license_info</code> fields</summary><table><thead><tr><th>Parameter</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>name</code></td><td><code>str</code></td><td><strong>REQUIRED</strong> (if a <code>license_info</code> is set). The license name used for the API.</td></tr><tr><td><code>url</code></td><td><code>str</code></td><td>A URL to the license used for the API. MUST be in the format of a URL.</td></tr></tbody></table></details> |
 | `license_info` | `dict` | The license information for the exposed API. It can contain several fields. <details><summary><code>license_info</code> fields</summary><table><thead><tr><th>Parameter</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>name</code></td><td><code>str</code></td><td><strong>REQUIRED</strong> (if a <code>license_info</code> is set). The license name used for the API.</td></tr><tr><td><code>identifier</code></td><td><code>str</code></td><td>An <a href="https://spdx.dev/spdx-specification-21-web-version/#h.jxpfx0ykyb60" class="external-link" target="_blank">SPDX</a> license expression for the API. The <code>identifier</code> field is mutually exclusive of the <code>url</code> field. <small>Available since OpenAPI 3.1.0, FastAPI 0.99.0.</small></td></tr><tr><td><code>url</code></td><td><code>str</code></td><td>A URL to the license used for the API. MUST be in the format of a URL.</td></tr></tbody></table></details> |

 You can set them as follows:

 ```Python hl_lines="3-16  19-31"
 ```Python hl_lines="3-16  19-32"
 {!../../../docs_src/metadata/tutorial001.py!}
 ```


 <img src="/img/tutorial/metadata/image01.png">

 ## License identifier

 Since OpenAPI 3.1.0 and FastAPI 0.99.0, you can also set the `license_info` with an `identifier` instead of a `url`.

 For example:

 ```Python hl_lines="31"
 {!../../../docs_src/metadata/tutorial001_1.py!}
 ```

 ## Metadata for tags

 You can also add additional metadata for the different tags used to group your path operations with the parameter `openapi_tags`.
diff --git a/docs/en/docs/tutorial/path-params.md b/docs/en/docs/tutorial/path-params.md

 ## Standards-based benefits, alternative documentation

 And because the generated schema is from the <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md" class="external-link" target="_blank">OpenAPI</a> standard, there are many compatible tools.
 And because the generated schema is from the <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md" class="external-link" target="_blank">OpenAPI</a> standard, there are many compatible tools.

 Because of this, **FastAPI** itself provides an alternative API documentation (using ReDoc), which you can access at <a href="http://127.0.0.1:8000/redoc" class="external-link" target="_blank">http://127.0.0.1:8000/redoc</a>:
Original file line number	Diff line number	Diff line change
Expand Up		@@ -236,5 +236,5 @@ For example:

		To see what exactly you can include in the responses, you can check these sections in the OpenAPI specification:

		* <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#responsesObject" class="external-link" target="_blank">OpenAPI Responses Object</a>, it includes the `Response Object`.
		* <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#responseObject" class="external-link" target="_blank">OpenAPI Response Object</a>, you can include anything from this directly in each response inside your `responses` parameter. Including `description`, `headers`, `content` (inside of this is that you declare different media types and JSON Schemas), and `links`.
		* <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#responsesObject" class="external-link" target="_blank">OpenAPI Responses Object</a>, it includes the `Response Object`.
		* <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#responseObject" class="external-link" target="_blank">OpenAPI Response Object</a>, you can include anything from this directly in each response inside your `responses` parameter. Including `description`, `headers`, `content` (inside of this is that you declare different media types and JSON Schemas), and `links`.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -46,7 +46,7 @@ The docs UI would also need the OpenAPI schema to declare that this API `server`

		```JSON hl_lines="4-8"
		{
		"openapi": "3.0.2",
		"openapi": "3.1.0",
		// More stuff here
		"servers": [
		{
Expand DownExpand Up		@@ -298,7 +298,7 @@ Will generate an OpenAPI schema like:

		```JSON hl_lines="5-7"
		{
		"openapi": "3.0.2",
		"openapi": "3.1.0",
		// More stuff here
		"servers": [
		{
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -29,10 +29,14 @@ And that function `get_openapi()` receives as parameters:

		* `title`: The OpenAPI title, shown in the docs.
		* `version`: The version of your API, e.g. `2.5.0`.
		* `openapi_version`: The version of the OpenAPI specification used. By default, the latest: `3.0.2`.
		* `description`: The description of your API.
		* `openapi_version`: The version of the OpenAPI specification used. By default, the latest: `3.1.0`.
		* `summary`: A short summary of the API.
		* `description`: The description of your API, this can include markdown and will be shown in the docs.
		* `routes`: A list of routes, these are each of the registered path operations. They are taken from `app.routes`.

		!!! info
		The parameter `summary` is available in OpenAPI 3.1.0 and above, supported by FastAPI 0.99.0 and above.

		## Overriding the defaults

		Using the information above, you can use the same utility function to generate the OpenAPI schema and override each part that you need.
Expand All		@@ -51,15 +55,15 @@ First, write all your FastAPI application as normally:

		Then, use the same utility function to generate the OpenAPI schema, inside a `custom_openapi()` function:

		```Python hl_lines="2 15-20"
		```Python hl_lines="2 15-21"
		{!../../../docs_src/extending_openapi/tutorial001.py!}
		```

		### Modify the OpenAPI schema

		Now you can add the ReDoc extension, adding a custom `x-logo` to the `info` "object" in the OpenAPI schema:

		```Python hl_lines="21-23"
		```Python hl_lines="22-24"
		{!../../../docs_src/extending_openapi/tutorial001.py!}
		```

Expand All		@@ -71,15 +75,15 @@ That way, your application won't have to generate the schema every time a user o

		It will be generated only once, and then the same cached schema will be used for the next requests.

		```Python hl_lines="13-1424-25"
		```Python hl_lines="13-1425-26"
		{!../../../docs_src/extending_openapi/tutorial001.py!}
		```

		### Override the method

		Now you can replace the `.openapi()` method with your new function.

		```Python hl_lines="28"
		```Python hl_lines="29"
		{!../../../docs_src/extending_openapi/tutorial001.py!}
		```

Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -103,11 +103,11 @@ It should look just like a normal FastAPI path operation:
		There are 2 main differences from a normal path operation:

		* It doesn't need to have any actual code, because your app will never call this code. It's only used to document the external API. So, the function could just have `pass`.
		* The path can contain an <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#key-expression" class="external-link" target="_blank">OpenAPI 3 expression</a> (see more below) where it can use variables with parameters and parts of the original request sent to your API.
		* The path can contain an <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#key-expression" class="external-link" target="_blank">OpenAPI 3 expression</a> (see more below) where it can use variables with parameters and parts of the original request sent to your API.

		### The callback path expression

		The callback path can have an <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#key-expression" class="external-link" target="_blank">OpenAPI 3 expression</a> that can contain parts of the original request sent to your API.
		The callback path can have an <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#key-expression" class="external-link" target="_blank">OpenAPI 3 expression</a> that can contain parts of the original request sent to your API.

		In this case, it's the `str`:

Expand Down
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,51 @@
		# OpenAPI Webhooks

		There are cases where you want to tell your API users that your app could call their app (sending a request) with some data, normally to notify of some type of event.

		This means that instead of the normal process of your users sending requests to your API, it's your API (or your app) that could send requests to their system (to their API, their app).

		This is normally called a webhook.

		## Webhooks steps

		The process normally is that you define in your code what is the message that you will send, the body of the request.

		You also define in some way at which moments your app will send those requests or events.

		And your users define in some way (for example in a web dashboard somewhere) the URL where your app should send those requests.

		All the logic about how to register the URLs for webhooks and the code to actually send those requests is up to you. You write it however you want to in your own code.

		## Documenting webhooks with FastAPI and OpenAPI

		With FastAPI, using OpenAPI, you can define the names of these webhooks, the types of HTTP operations that your app can send (e.g. `POST`, `PUT`, etc.) and the request bodies that your app would send.

		This can make it a lot easier for your users to implement their APIs to receive your webhook requests, they might even be able to autogenerate some of their own API code.

		!!! info
		Webhooks are available in OpenAPI 3.1.0 and above, supported by FastAPI `0.99.0` and above.

		## An app with webhooks

		When you create a FastAPI application, there is a `webhooks` attribute that you can use to define webhooks, the same way you would define path operations, for example with `@app.webhooks.post()`.

		```Python hl_lines="9-13 36-53"
		{!../../../docs_src/openapi_webhooks/tutorial001.py!}
		```

		The webhooks that you define will end up in the OpenAPI schema and the automatic docs UI.

		!!! info
		The `app.webhooks` object is actually just an `APIRouter`, the same type you would use when structuring your app with multiple files.

		Notice that with webhooks you are actually not declaring a path (like `/items/`), the text you pass there is just an identifier of the webhook (the name of the event), for example in `@app.webhooks.post("new-subscription")`, the webhook name is `new-subscription`.

		This is because it is expected that your users would define the actual URL path where they want to receive the webhook request in some other way (e.g. a web dashboard).

		### Check the docs

		Now you can start your app with Uvicorn and go to <a href="http://127.0.0.1:8000/docs" class="external-link" target="_blank">http://127.0.0.1:8000/docs</a>.

		You will see your docs have the normal path operations and now also some webhooks:

		<img src="/img/tutorial/openapi-webhooks/image01.png">
Original file line number	Diff line number	Diff line change
Expand Up		@@ -97,7 +97,7 @@ And if you see the resulting OpenAPI (at `/openapi.json` in your API), you will

		```JSON hl_lines="22"
		{
		"openapi": "3.0.2",
		"openapi": "3.1.0",
		"info": {
		"title": "FastAPI",
		"version": "0.1.0"
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -99,7 +99,7 @@ It will show a JSON starting with something like:

		```JSON
		{
		"openapi": "3.0.2",
		"openapi": "3.1.0",
		"info": {
		"title": "FastAPI",
		"version": "0.1.0"
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -9,15 +9,16 @@ You can set the following fields that are used in the OpenAPI specification and
		\| Parameter \| Type \| Description \|
		\|------------\|------\|-------------\|
		\| `title` \| `str` \| The title of the API. \|
		\| `summary` \| `str` \| A short summary of the API. <small>Available since OpenAPI 3.1.0, FastAPI 0.99.0.</small> \|
		\| `description` \| `str` \| A short description of the API. It can use Markdown. \|
		\| `version` \| `string` \| The version of the API. This is the version of your own application, not of OpenAPI. For example `2.5.0`. \|
		\| `terms_of_service` \| `str` \| A URL to the Terms of Service for the API. If provided, this has to be a URL. \|
		\| `contact` \| `dict` \| The contact information for the exposed API. It can contain several fields. <details><summary><code>contact</code> fields</summary><table><thead><tr><th>Parameter</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>name</code></td><td><code>str</code></td><td>The identifying name of the contact person/organization.</td></tr><tr><td><code>url</code></td><td><code>str</code></td><td>The URL pointing to the contact information. MUST be in the format of a URL.</td></tr><tr><td><code>email</code></td><td><code>str</code></td><td>The email address of the contact person/organization. MUST be in the format of an email address.</td></tr></tbody></table></details> \|
		\| `license_info` \| `dict` \| The license information for the exposed API. It can contain several fields. <details><summary><code>license_info</code> fields</summary><table><thead><tr><th>Parameter</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>name</code></td><td><code>str</code></td><td><strong>REQUIRED</strong> (if a <code>license_info</code> is set). The license name used for the API.</td></tr><tr><td><code>url</code></td><td><code>str</code></td><td>A URL to the license used for the API. MUST be in the format of a URL.</td></tr></tbody></table></details> \|
		\| `license_info` \| `dict` \| The license information for the exposed API. It can contain several fields. <details><summary><code>license_info</code> fields</summary><table><thead><tr><th>Parameter</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>name</code></td><td><code>str</code></td><td><strong>REQUIRED</strong> (if a <code>license_info</code> is set). The license name used for the API.</td></tr><tr><td><code>identifier</code></td><td><code>str</code></td><td>An <a href="https://spdx.dev/spdx-specification-21-web-version/#h.jxpfx0ykyb60" class="external-link" target="_blank">SPDX</a> license expression for the API. The <code>identifier</code> field is mutually exclusive of the <code>url</code> field. <small>Available since OpenAPI 3.1.0, FastAPI 0.99.0.</small></td></tr><tr><td><code>url</code></td><td><code>str</code></td><td>A URL to the license used for the API. MUST be in the format of a URL.</td></tr></tbody></table></details> \|

		You can set them as follows:

		```Python hl_lines="3-16 19-31"
		```Python hl_lines="3-16 19-32"
		{!../../../docs_src/metadata/tutorial001.py!}
		```

Expand All		@@ -28,6 +29,16 @@ With this configuration, the automatic API docs would look like:

		<img src="/img/tutorial/metadata/image01.png">

		## License identifier

		Since OpenAPI 3.1.0 and FastAPI 0.99.0, you can also set the `license_info` with an `identifier` instead of a `url`.

		For example:

		```Python hl_lines="31"
		{!../../../docs_src/metadata/tutorial001_1.py!}
		```

		## Metadata for tags

		You can also add additional metadata for the different tags used to group your path operations with the parameter `openapi_tags`.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -83,7 +83,7 @@ And when you open your browser at <a href="http://127.0.0.1:8000/docs" class="ex

		## Standards-based benefits, alternative documentation

		And because the generated schema is from the <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md" class="external-link" target="_blank">OpenAPI</a> standard, there are many compatible tools.
		And because the generated schema is from the <a href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md" class="external-link" target="_blank">OpenAPI</a> standard, there are many compatible tools.

		Because of this, FastAPI itself provides an alternative API documentation (using ReDoc), which you can access at <a href="http://127.0.0.1:8000/redoc" class="external-link" target="_blank">http://127.0.0.1:8000/redoc</a>:

Expand Down