Much of the code we write these days depends on the web. After all, why develop a new protocol when you can add a custom payload to HTTP? There’s no need to create a new layer in the networking stack when there’s already one that’s extensible, flexible, and secure. Instead we can take advantage of the GET and POST functions in HTTP and work with RESTful APIs.
Yes, that’s oversimplifying, but in practice very few occasions demand something completely new. HTTP is a simplification, yes, but it’s also an obfuscation. If everything we use is HTTP under the hood, how do we build testing and development tools that can work with those APIs?
Although the Open API Initiative and other approaches go a long way to codifying how we describe and implement HTTP-based APIs, we’re usually left cobbling together a mix of different tools to build and test our API calls. Postman is probably the most popular and most familiar tool out there, but it’s separate from both our development environments and our browsers, making it hard to be sure that we’re designing and testing HTTP calls in the context of our applications.