Technically speaking, I&#x27;m a big fan of <a href="http:&#x2F;&#x2F;swagger.io&#x2F;" rel="nofollow">http:&#x2F;&#x2F;swagger.io&#x2F;</a>, especially since it&#x27;s turned in to the Open API Initiative. You (or your client) define an API in YAML, and then you can use the Swagger Codegen tool to automate building a client SDK and a mock server based on it. API changes are handled by simply rerunning the generator. I&#x27;ve found that the NodeJS&#x2F;Angular code that&#x27;s generated is good enough to use in production if you&#x27;re sensible.<p>As far as managing the process, the only way to do it is to make sure the customer understands that the lack of a working API test server (with good stubs to start with, and actual data further on in the project) will delay the project. Make sure that you tell them the app development will lag behind the API by at least a month.