Single API definition file for both v1 and v2 Confluence Cloud APIs

Is it possible to get a single OpenAPI/Swagger definition which includes both the v1 and v2 APIs?

This is what we currently see:

We currently use the v1 definition to automatically generate clients to access the API; as part of our migration to v2, it would be really helpful for there to be a single definition including both APIs. They seem to be intended to work in tandem anyways, as v2 is not a full replacement for v1.

5 Likes