chichepoFrequent ContributorJoined 3 years ago140 Posts39 LikesLikes received14 SolutionsView All Badges
ContributionsMost RecentMost LikesSolutionsSwagger JSON Format URL does not work using /v1/ Hello Until today, when displaying the swagger file in json format we use a URL like this: https://MySwaggerhubServer.mydomain/v1/MyOrg/MySwagger/1.0.0 However, we are trying to install a new server, but this URL convention, does not work. So I found that this one will do the job: https://MySwaggerhubServer.mydomain/apiproxy/registry/MyOrg/MySwagger/1.0.0 I wonder If we missed a proxy definition somewhere. Does anyone already faced such kind of issue? thank you Re: Hide some api from users in my organization beAPI Hi It's a little bit complex since organization team member's are supposed to have a minimum level of access, at least read level. You can define your API in a separated Org and manage the access by using the "Share and collaborate" link. Then, the link will grant an individually access to the API spec. according to your needs. Let us know if you get a solution Re: About publishing and deleting data entered online ma-inoue nothing is left on the server side Re: About publishing and deleting data entered online ma-inoue this is my understanding and it is quite obvious. But someone from @smartbear should confirm. Re: About publishing and deleting data entered online Hi ma-inoue My understanding: Question 1. Is there a possibility that it will be disclosed to a third party? Not possible as far as I know. You must export the spec and send it to the third party. Question 2. Will the data remain on the cloud side? If any remain, please delete them. *Reply request: October 18th As far As I know, it is saved on the client side. You can clear it by clearing your client local storage: Modification recorded in the local storage: After clearing the storage and refresh: Re: resloved yaml is having 3 dashes "---" as first line, is removing all comments + adding linebreaks Hello adriaanbastien I am not sure about the reasons behind the modification of your file when resolving the specification. Resolved file is intended to be injected to any "Programmatic" system and it obviously requires to flatten the file before. So it may depend on your "resolving" engine" When using SwaggerHub resolve option, I got such kind of result: on the left, the resolved file. Like you see I am using MD language for return characters: let us know Re: API response type backwards compatible? Hi jbao81 Your changes seems to be correct in order to address your new requirement. Be aware that the response is not validated against any rules and can include unwanted data. Re: Create New API in SwaggerHub gives http 405 dlambert Try to connect from another network (home/wifi/etc.) It's not an issue related to SwaggerHub as far as I can understand Re: Generating OAS from Code Hi shobhit-sl Have you tried to look on the net for such kind of converter? Are you interresed in a commercial/free tool? Re: Create New API in SwaggerHub gives http 405 Hi dlambert It's obviously something linked to the connection. Are you working with on-premise edition? Can you open the network console on the browser ans send it?