As a back-end, being urged by the front-end to require interfaces has become a daily hassle in my work; and when the front-end jointly debugged, I found that the data of my mock did not match the back-end, which was even more frustrating.
When the backend has not yet provided a real interface, it is very important to first get a data structure of the simulated response, which is what we call the interface document.
How to write such a dynamic document that is clear and standardized and can be updated in real time? No need to do it yourself, we can use Apipost, a research and development collaboration artifact, to quickly and automatically generate an ideal interface document!
As a back-end, being urged by the front-end to require interfaces has become a daily hassle in my work; and when the front-end jointly debugged, I found that the data of my mock did not match the back-end, which was even more frustrating.
When the backend has not yet provided a real interface, it is very important to first get a data structure of the simulated response, which is what we call the interface document.
How to write such a dynamic document that is clear and standardized and can be updated in real time? No need to do it yourself, we can use Apipost, a research and development collaboration artifact, to quickly and automatically generate an ideal interface document!