The Importance of Postman API Environment Files
I’m a big fan of Postman and the power of their development environment as well as their Postman Collection format. I think their approach to not just integrating with APIs, but also enabling the development and delivery of APIs has shifted the conversation around APIs in the last couple of years — not too many API service providers accomplish this in my experience. There are several dimensions to what Postman does that I think are pushing the API conversation forward, but one that has been capturing my attention lately are Postman Environment Files.
Using Postman, you can manage many different environments used for working with APIs, and if you are a pro or enterprise customer, you can export a file that represents an environment, making each of these API definitions more portable and collaborative. Managing the variety of environments for the hundreds of APIs I use is one of the biggest pain points I have. Postman has significantly helped me get a handle on the tokens and keys I use across the internal, as well as partner and public APIs that I depend on each day to operate API Evangelist. https://goo.gl/AQm2d7 #DataIntegration #ML
Swagger Generation With Spring Boot
#ICYMI: Ever thought about what could happen if you develop your Restful API’s but you are not able to document it for someone to refer to it? Or you develop your API’s and the front-end team needs to access it how they would know what your API’s contain or require as input?
The solution to the above question is using Swagger. Swagger is an open source framework where you can document your Restful API’s, access them, and test your services. But how do we do that? Let’s see through a working example. https://goo.gl/hZ63ff #DataIntegration #ML