QUERY method: OpenAPI 3.2 and RFC 10008 are both out now #15839

sss1889 · 2026-06-25T06:39:30Z

sss1889
Jun 25, 2026

Pinging from #12965 — @Kludex said to open a Discussion once OpenAPI supports QUERY.

OpenAPI 3.2 shipped last September with QUERY support, and RFC 10008 went final earlier this month. Looks like we're unblocked.

I took a shot at implementing this locally, and found a couple of spots that are easy to miss because CI won't catch them:

PathItem in openapi/models.py defines explicit fields for get through trace, but not query. It works anyway because of extra="allow", but there's no type checking on it and nothing fails to tell you it's missing.
test_operations_signatures.py has a hardcoded list of method names to check signature consistency between APIRouter and FastAPI. If you forget to add "query" there, mismatches between the two classes just silently pass.

Swagger UI doesn't render it yet, but the JSON output is correct.

I have a PR ready if you want it.

YuriiMotov · 2026-06-25T08:11:48Z

YuriiMotov
Jun 25, 2026
Collaborator

Thanks!

We track this internally and will implement this once we have time

2 replies

felipebmendes Jul 13, 2026

Thanks for the discussion! Is there any estimated timeline for this feature, or is it still too early to say? We'd like to know whether we should wait for native support or implement a workaround for now.

YuriiMotov Jul 13, 2026
Collaborator

Unfortunately no ETA..

alexNMD · 2026-06-29T13:19:24Z

alexNMD
Jun 29, 2026

A new RFC about that has been release : https://datatracker.ietf.org/doc/html/rfc10008

1 reply

joar Jul 3, 2026

That's the RFC that "RFC 10008" from the title of the discussion refers to.

YuriiMotov · 2026-07-08T09:38:25Z

YuriiMotov
Jul 8, 2026
Collaborator

a-maliarov
Jul 20, 2026

+1

0 replies

N1ntek · 2026-07-28T14:31:48Z

N1ntek
Jul 28, 2026

+1

0 replies

Johandielangman · 2026-08-12T04:20:46Z

Johandielangman
Aug 12, 2026

+1

Tnx for the amazing work you guys are doing!

0 replies

Raymondo97 · 2026-08-27T20:06:44Z

Raymondo97
Aug 27, 2026

Hey! I've been looking into this as well. Just wanted to report on some findings.

Swagger UI officially supports OpenAPI 3.2 now, so that is not a blocker.
FastAPI still ships ReDoc 2 as a backup UI. ReDoc 2 does not support OpenAPI 3.2. In fact, its parser behavior is explicitly gated around 3.1. Its validation seems to be more permissive, so it may not outright reject an OpenAPI 3.2 document. However, regarding the QUERY method, ReDoc would not classify it as an operation. The combination of these facts could make ReDoc documentation very buggy, incomplete, or broken if FastAPI adopted OpenAPI 3.2.

Given that, it seems like ReDoc may be one of the remaining pieces to resolve before FastAPI can move its default OpenAPI version to 3.2. I can also understand why that makes it difficult to give a more precise ETA for QUERY support.

One thing I'm curious about: is ReDoc CE 3 something FastAPI is intentionally waiting on before moving to OpenAPI 3.2, or would the maintainers consider moving to OpenAPI 3.2 independently and treating ReDoc compatibility separately? I mainly ask because that seems to determine whether there's useful prerequisite work contributors could help with in the meantime. I don't intend to add to the abundant noise these features are already creating.

5 replies

Raymondo97 Aug 31, 2026

Also, it looks like Starlette just added some support for it. Granted, I don't know if that will be incorporated into v0, since that is what FastAPI uses. I'm curious if that was another aspect of this that was needing to be resolved first.

YuriiMotov Aug 31, 2026
Collaborator

I don't know if that will be incorporated into v0, since that is what FastAPI uses

FastAPI pins Starlette as >=0.46.0. So, v1 is supported

Raymondo97 Sep 2, 2026

FastAPI pins Starlette as >=0.46.0. So, v1 is supported

Thanks for the clarification. I do remember seeing that once. I just didn't know if this kind of a change would get in the way of that.

YahelBaram Sep 25, 2026

Hi
Several days ago starlette released 1.7.0 that added QUERY support. Does it mean it is now possible to implement QUERY in FastAPI?

Raymondo97 Sep 28, 2026

Hi Several days ago starlette released 1.7.0 that added QUERY support. Does it mean it is now possible to implement QUERY in FastAPI?

I can't speak for the maintainers. But from the research I've done, that is only a portion of what may have been blocking it. It is good that starlette supports it. And as mentioned by @YuriiMotov, FastAPI does have support for v1+, which would include v1.7.0.

The other aspect is that a key feature of FastAPI is the documentation that is generated from an application's code. The documentation packages behind this feature (i.e. Swagger and ReDoc) would need to fully support QUERY as a valid route, so the documentation looks clean, consistent, and accurate. Some of those packages may have implemented the necessary changes already. But there are a lot of other changes beyond QUERY included with those updates, that FastAPI would need to account for.

In summary, for FastAPI to implement QUERY, it needs to support it for both the documentation and runtime aspects of its code. It also has to support the other features/fixes shipped alongside the QUERY support. So it is a larger undertaking than most of us realize. This is why the original issue was closed.

Glaedr304 · 2026-09-29T19:06:21Z

Glaedr304
Sep 29, 2026

+1

0 replies

8thgencore · 2026-10-24T07:44:41Z

8thgencore
Oct 24, 2026

Update on the ReDoc blocker mentioned above: Redoc 3.0.0 was released on 2026-10-14 with OpenAPI 3.2 support (additionalOperations, querystring parameters, itemSchema for streaming media types, nested tags):
https://github.com/Redocly/redoc/releases/tag/redoc%403.0.0

So both bundled UIs (Swagger UI and ReDoc) now support 3.2.

A few things to note for migrating get_redoc_html from redoc@2:

The UMD bundle is gone; the standalone bundle is now an ES module, so the <script> tag needs type="module".
Anonymous OpenTelemetry telemetry is on by default (disableTelemetry option), which FastAPI probably wants to turn off.
The theme option was removed in favor of CSS variables, and some options were renamed. This could affect users who pass a custom redoc_js_url.

This would also fix the current mismatch where FastAPI emits itemSchema (a 3.2 field) in a document declared as 3.1.0 (#15328).

0 replies

Icaro0310 · 2026-10-28T03:48:51Z

Icaro0310
Oct 28, 2026

PathItem is the visible one, two others got me when I tried the same thing.

There's a METHODS_WITH_BODY set in openapi/constants.py that gates whether get_openapi_path() emits a requestBody. QUERY isn't in it, so routes would silently lose their body in the generated spec even after you add the PathItem field. And get_openapi() still stamps openapi: "3.1.0" on output, where a query operation isn't a valid PathItem member, so the version string (or the serializer) needs to know it's targeting 3.2.

Also the pinned swagger-ui bundle in openapi/docs.py won't render the operation even with a correct spec, needs a build with 3.2 support. Routing itself is fine, Starlette just uppercases whatever methods you pass, and client.request("QUERY" ...) works in httpx for tests.

—
Related work of mine: github.com/Icaro0310 · Website: icaro0310.github.io

0 replies

QUERY method: OpenAPI 3.2 and RFC 10008 are both out now #15839

Uh oh!

Replies: 10 comments · 8 replies

Uh oh!

YuriiMotov Jun 25, 2026 Collaborator

Uh oh!

Uh oh!

YuriiMotov Jul 13, 2026 Collaborator

Uh oh!

Uh oh!

Uh oh!

YuriiMotov Jul 8, 2026 Collaborator

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

YuriiMotov Aug 31, 2026 Collaborator

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Replies: 10 comments 8 replies

YuriiMotov
Jun 25, 2026
Collaborator

YuriiMotov Jul 13, 2026
Collaborator

YuriiMotov
Jul 8, 2026
Collaborator

YuriiMotov Aug 31, 2026
Collaborator