Hi team, we have separate API versions with different functionalities. We noticed that we are stuck in importing our Swagger spec for the previous API version since Import option is disabled. Kindly look into this as it is crucial for us to maintain 2 versions at the same time.
Hi HamzaJD, Thanks for your feedback. We’ve noted this request and will consider it in future updates.
Hi Team, any development on this?
Hi HamzaJD, the version import feature is expected to be released next Friday.
Hi there, is this now supported?
Hi HamzaJD, it’s already supported. Please update and try it out.
Hi team,
We are trying to import to specific folders in the API version but unable to do so. Please look into this. I had communicated with the team that this feature is implemented but we are blocked due to this.
@urgent Md Mamunur Rashid
Hey HamzaJD, this is Joe, the PM of Apidog. We have launched the ‘module’ feature, which allows you to manage endpoints from multiple OAS files within a single Apidog project. You can try creating multiple modules, naming them as different versions, and importing the OAS into the designated module in the main branch for management.
Hi Joe, thanks for your response. We already have our API docs hosted for our customers on Apidog. I want to know if updating to new version 2.7.17 would cause any disruptions in it? My enpoint folders are located under Root folder.
I think it might be better to start a new project to try the way I recommended, if you have the time. Because at least this way it won’t affect the work you’ve already completed. Of course, upgrading to the latest version will not have any impact on existing data.
Thanks Joe, I’ll try it out and get back to you.
Hi Joe, hope you’re doing great. The module functionality looks great. Shoutout to the team for amazing feature.
I had been trying it out since you suggested testing it out in a new project. Our team is using Professional Licences so there is no limitations on Project count.
I was wondering since we were talking about treating modules as API versions. Is it possible to have a root slug for each Module. For example, two modules are created to maintain 2 versions of APIs. One is named “V2 APIs” and another “V1 APIs”. For scalability it would be great if the URL slug can be specified like “endpoints/v2/get-a-user” where “endpoints/v2/” is defined on the module. This way we can keep the same URL slug for the API name since we will be maintaining V1 in the same main branch. For example the equivalent V1 endpoint can have the same name “get-a-user” and there would be no collisions because the V1 module would be appending “endpoints/v1/” on it.
This will allow to use the same main project for multiple APIs and multiple versions.
For example,
“endpoints/v2/get-a-user”
“endpoints/v1/get-a-user” will both be maintained in the same main branch under 2 different modules with a room for a future v3 without any breaking changes.
Thank you for your feedback. We will consider optimizing this feature.
I am very glad that you succeeded in trying the new way. The requirement you mentioned about the slug makes sense, and we will support it in the future. Thank you again for working with us, HamzaJD!