Great question! We actually have a community page dedicated to answering questions just like this one, which you can find here: community.postman.com Please submit your question and a link to this video there, so that it can reach the greater Postman Developer Community.
I really want to use the api builder feature but the validation issue is keeping me off. Validation works when done as shown the video but if i create another schema say "audio" and then change $ref on the path to "audio" and save it and try to validate it, it doesn't detect any changes at all. This is really frustrating and only way to get those changes would be to generate new collection and mockserver. It be really nice if any changes on the spec would reflect on the collection too.
@@arlemii I had a similar issue. There are even times that if change any metadata or names in path in openapi and run validation, Postman can't detect any changes at all.
According to this video we can create mock servers, environments and documents inside the Postman API. But latest version is not showing that feature. Because of that we need to copy the collection into workspace and then need to create a mock server. And also if do any changes to API definition it is not reflected to the collection. Again we need to create a collection using that definition and copy that collection to workspace and create mocks server again. Any thoughts on this?
In v10, the engineering team simplified this workflow. If you have specific feedback or a feature request, perhaps you can chime in on this issue (github.com/postmanlabs/postman-app-support/issues/11345) or this one (github.com/postmanlabs/postman-app-support/issues/6722) or create a new one.
You can use the same one, but splitting it allows: - better organization - testing against production instead of a mock - docs to reflect the prod URL instead of the mock URL
How come the mock servers know what to send as response? As a PM just want to know how the server side is created - as in the video it is not clear how the mock server knew the responses.Are we creating any mock DB at the mock server where response's key value pairs are stored?
The mock server will use the example responses from the collection, these can be created either: - when generating the collection from an OpenAPI definition - by sending requests to the API then saving the response as an example More info in the Postman's Learning Center: learning.postman.com/docs/designing-and-developing-your-api/mocking-data/mocking-with-examples/#step-3-save-a-response-as-an-example
Hi, I need to validate swagger schema which is in json formag with my API response..Can you please help me with that
Great question! We actually have a community page dedicated to answering questions just like this one, which you can find here: community.postman.com
Please submit your question and a link to this video there, so that it can reach the greater Postman Developer Community.
I really want to use the api builder feature but the validation issue is keeping me off. Validation works when done as shown the video but if i create another schema say "audio" and then change $ref on the path to "audio" and save it and try to validate it, it doesn't detect any changes at all. This is really frustrating and only way to get those changes would be to generate new collection and mockserver. It be really nice if any changes on the spec would reflect on the collection too.
Thanks for the feedback! Is your issue similar to this one? If so could you please add your use-case there as well? This will help us triage and fix.
I forgot the link to the issue: github.com/postmanlabs/openapi-to-postman/issues/309
@@arlemii I had a similar issue. There are even times that if change any metadata or names in path in openapi and run validation, Postman can't detect any changes at all.
According to this video we can create mock servers, environments and documents inside the Postman API. But latest version is not showing that feature. Because of that we need to copy the collection into workspace and then need to create a mock server. And also if do any changes to API definition it is not reflected to the collection. Again we need to create a collection using that definition and copy that collection to workspace and create mocks server again. Any thoughts on this?
In v10, the engineering team simplified this workflow. If you have specific feedback or a feature request, perhaps you can chime in on this issue (github.com/postmanlabs/postman-app-support/issues/11345) or this one (github.com/postmanlabs/postman-app-support/issues/6722) or create a new one.
Any reason why you wouldn't use the same collection generated for the mock server for tests and docs?
You can use the same one, but splitting it allows:
- better organization
- testing against production instead of a mock
- docs to reflect the prod URL instead of the mock URL
How come the mock servers know what to send as response? As a PM just want to know how the server side is created - as in the video it is not clear how the mock server knew the responses.Are we creating any mock DB at the mock server where response's key value pairs are stored?
The mock server will use the example responses from the collection, these can be created either:
- when generating the collection from an OpenAPI definition
- by sending requests to the API then saving the response as an example
More info in the Postman's Learning Center: learning.postman.com/docs/designing-and-developing-your-api/mocking-data/mocking-with-examples/#step-3-save-a-response-as-an-example
Great presentation! Please, next time use a microphone closer to your mouth to avoid sound reverberation.
The user interface has changed so much that your videos are so out of date and not very useful.