Hi,

I came across MR !714 [1] and issue #560 [2] and wanted to express strong support for this feature.

I'm also working on integrating with HyperKitty's REST API, and the lack of a machine-readable schema has been a significant pain point. Right now, I have to read the source code to figure out: - What endpoints are available - What request formats each endpoint expects - What the response structure looks like - Which fields are required vs optional [image: image.png] An OpenAPI schema would solve all of these issues and make third-party integrations much easier to build and maintain.

The MR looks well-crafted: it adds zero backward compatibility impact, all tests pass, and drf-spectacular is the officially recommended tool for Django REST Framework.

I'd love to see this merged. Happy to help test if needed.

[1] https://gitlab.com/mailman/hyperkitty/-/merge_requests/714 [2] https://gitlab.com/mailman/hyperkitty/-/issues/560

Thanks, TomNewChao