3.6 KiB
Metadata and Docs URLs
You can customize several metadata configurations in your FastAPI application.
Title, description, and version
You can set the:
- Title: used as your API's title/name, in OpenAPI and the automatic API docs UIs.
- Description: the description of your API, in OpenAPI and the automatic API docs UIs.
- Version: the version of your API, e.g.
v2
or2.5.0
.- Useful for example if you had a previous version of the application, also using OpenAPI.
To set them, use the parameters title
, description
, and version
:
{!../../../docs_src/metadata/tutorial001.py!}
With this configuration, the automatic API docs would look like:

Metadata for tags
You can also add additional metadata for the different tags used to group your path operations with the parameter openapi_tags
.
It takes a list containing one dictionary for each tag.
Each dictionary can contain:
name
(required): astr
with the same tag name you use in thetags
parameter in your path operations andAPIRouter
s.description
: astr
with a short description for the tag. It can have Markdown and will be shown in the docs UI.externalDocs
: adict
describing external documentation with:description
: astr
with a short description for the external docs.url
(required): astr
with the URL for the external documentation.
Create metadata for tags
Let's try that in an example with tags for users
and items
.
Create metadata for your tags and pass it to the openapi_tags
parameter:
{!../../../docs_src/metadata/tutorial004.py!}
Notice that you can use Markdown inside of the descriptions, for example "login" will be shown in bold (login) and "fancy" will be shown in italics (fancy).
!!! tip You don't have to add metadata for all the tags that you use.
Use your tags
Use the tags
parameter with your path operations (and APIRouter
s) to assign them to different tags:
{!../../../docs_src/metadata/tutorial004.py!}
!!! info Read more about tags in Path Operation Configuration{.internal-link target=_blank}.
Check the docs
Now, if you check the docs, they will show all the additional metadata:

Order of tags
The order of each tag metadata dictionary also defines the order shown in the docs UI.
For example, even though users
would go after items
in alphabetical order, it is shown before them, because we added their metadata as the first dictionary in the list.
OpenAPI URL
By default, the OpenAPI schema is served at /openapi.json
.
But you can configure it with the parameter openapi_url
.
For example, to set it to be served at /api/v1/openapi.json
:
{!../../../docs_src/metadata/tutorial002.py!}
If you want to disable the OpenAPI schema completely you can set openapi_url=None
, that will also disable the documentation user interfaces that use it.
Docs URLs
You can configure the two documentation user interfaces included:
- Swagger UI: served at
/docs
.- You can set its URL with the parameter
docs_url
. - You can disable it by setting
docs_url=None
.
- You can set its URL with the parameter
- ReDoc: served at
/redoc
.- You can set its URL with the parameter
redoc_url
. - You can disable it by setting
redoc_url=None
.
- You can set its URL with the parameter
For example, to set Swagger UI to be served at /documentation
and disable ReDoc:
{!../../../docs_src/metadata/tutorial003.py!}