If postman wants to synchronize, it will cost money, and the functions are not complete enough. I think each interface folder should at least have the display of the submitted person and the modified person, and the interface should be able to easily export into documents, test code, etc.
The most important thing is to synchronize collaborators and creators
The reason why postman is mentioned is that it is very convenient to use it, and you can see the response and request headers. It can be used for real-time testing, testing after it goes online, and testing during development. Postman can also cooperate with the chrome postman plug-in recording request to automatically record cookies and other messy headers into postman. You can also edit the request to upload the file using raw body binary system, and upload the file as you want.
This is the function of swagger and git, and has nothing to do with postman
You can see this article I sorted out before: https://segmentfault.com/a/11... See if there's anything you need.
It's OK to have an apizza, http://apizza.cc/. A better way is to recommend using apidoc to generate documents through annotations, and then publish the documents to the self built gitlab in the continuous deployment of gitlab
I used to be a postman, but later I used apipost for teamwork( https://www.apipost.cn/ )。 Very good, too!
You can try apipost, the enhanced version of postman. The free content is enough to satisfy you, and there is a strong team to update the tool regularly. Problems can be well solved( https://www.apipost.cn/ ))