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

**URL:** <https://community.developer.atlassian.com/t/single-api-definition-file-for-both-v1-and-v2-confluence-cloud-apis/73123>\
**Category:** Confluence Cloud\
**Tags:** rest-api-v2, open-api\
**Created:** [September 21, 2023, 5:08pm UTC](https://community.developer.atlassian.com/t/single-api-definition-file-for-both-v1-and-v2-confluence-cloud-apis/73123 "2023-09-21T17:08:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aprechtl](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/aprechtl/32/45430_2.png) [@aprechtl](https://community.developer.atlassian.com/u/aprechtl)\
**Post date:** [September 21, 2023, 5:08pm UTC](https://community.developer.atlassian.com/t/single-api-definition-file-for-both-v1-and-v2-confluence-cloud-apis/73123/1 "2023-09-21T17:08:02Z")

</div>

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

This is what we currently see:

- [Spec for v1](https://dac-static.atlassian.com/cloud/confluence/swagger.v3.json?_v=1.6556.0-0.1285.0)
- [Spec for v2](https://dac-static.atlassian.com/cloud/confluence/openapi-v2.v3.json?_v=1.6556.0-0.1285.0)

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.