Skip to content

Clarify deprecation of built-in OpenAPI documentation #9874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
browniebroke merged 3 commits into from
Jan 24, 2026
+7 −6
Merged

Clarify deprecation of built-in OpenAPI documentation #9874

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d7b20f4
Fix section title and add note on OpenAPI packages
RispaJoseph Jan 20, 2026
5aab82e
Refine description of API documentation choices
RispaJoseph Jan 20, 2026
c677adc
Use warning admonition for OpenAPI deprecation notice
RispaJoseph Jan 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/topics/documenting-your-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,11 @@
>
> — Roy Fielding, [REST APIs must be hypertext driven][cite]

REST framework provides a range of different choices for documenting your API. The following
is a non-exhaustive list of the most popular ones.
REST framework provides a range of different choices for documenting your API. The following is a non-exhaustive list of some of the most popular options.

## Third party packages for OpenAPI support
## Third-party packages for OpenAPI support

REST framework recommends using third-party packages for generating and presenting OpenAPI schemas, as they provide more features and flexibility than the built-in (deprecated) implementation.

### drf-spectacular

Expand Down
Loading