Kloudless Blog

Tutorials, case studies and how-tos from our experts

Wait a minute, Mr. Postman: Kloudless at the SF API Network Event

On April 23rd, Postman held a meetup at their San Francisco Headquarters and our own Customer Success Engineer, Chris Prochnow, led a walkthrough of the benefits that the Kloudless Postman Collection provides him in his role of assisting developers in accessing our Unified APIs.

Postman, for those unfamiliar with the company, offers a wide range of services to help developers connect to and test APIs through their GUI-based development environment. They do this by making the process of API consumption and testing straightforward and undemanding.

Before Postman, developers constructed or wrote lengthy cURL requests or used HTTP-request libraries to test API responses. Now, through the use of the Postman client, developers can vastly cut down on the time needed to test APIs by storing necessary pieces of their requests such as environmental variables and authentication parameters.

To further help with API testing, Postman released their Postman Collection feature; an API description format that offers organization of requests by folder, pre-request scripts, automated documentation generation, and more.  Chris created the Kloudless Postman Collection in February, so this event seemed like the perfect opportunity for him to go and show off his inside knowledge of working with the powerful testing toolkit.

With about 40 API enthusiasts on hand for the event, Chris began with a breakdown of Kloudless Unified APIs and what they provide for companies looking to solve their integration problems, before moving into the pivotal reasons for choosing to provide easy access to our services through a Postman Collection. Specifically, Chris noted that the collections allow Kloudless to “make it easier for users to work on our API with the development tools they are familiar with.”

By providing developers looking to test out our services a familiar and trustworthy piece of software as a means to do so, we can make their initial experience smoother and more forgiving. Much of this is due to the powerful pre-request scripts that Chris created to prompt a developer with what pivotal piece of a request they may be missing before attempting to send it.

Pre-request scripts are simply JavaScript functions that are called before a request is sent. Say, for example, a developer is missing a key parameter in their request, such as environmental variables or a piece of user ID information. Instead of the developer making the request and being met with a 403 error, the pre-request script will catch that missing parameter before the request is sent and log the developer a helpful message prompting them to what they are specifically missing from the request.

As Chris points out, “this makes devs testing our products out for the first time more likely to not encounter problems that might turn them off the API entirely.” This plays a major role in the deciding factors of whether a developer will continue to use our Unified APIs, as being met with an initial roadblock when testing out an API can sour one to a service quickly.

Chris also covered how the Postman OAuth 2.0 management feature helps developers save considerable time when testing out multiple endpoints of our APIs by storing their access tokens and automatically inserting them into each call. Small time-saving features like these can make all the difference in the world when a developer is making a decision to continue testing with our Unified APIs, and Chris was excited to see how many members of the audience were in agreement with this assessment.

Finally, Chris covered how the Kloudless Postman Collection can ease a developer’s initial testing by providing an automated documentation testing kit capable of generating requests in multiple languages and libraries on the fly. Using embedded OpenAPI Specifications, the collection will automatically create calls to each and every one of the endpoints supported in cURL, Python, Node, and more. So, no matter the testing language or environment a developer uses, they will feel right at home using the collection as an initial testing tool.

When it was all said and done, the audience walked away with a deeper understanding of how Postman Collections can not only help a developer consume an API in testing, but also help those like Chris who support customers throughout the process. By cutting down on the amount of support tickets generated by developers simply trying to access the API in the first place, Chris has more time to focus on new and exciting ways to support customers in the future.

The Kloudless Postman Collection is just one of the many new additions to Kloudless in Q1 of 2019. To get an in-depth look at all of the new additions to our software and APIs in the first quarter of the year, please check out our post on product updates here.

We are grateful to Postman for giving Chris the opportunity to speak to their audience about how the Postman Collections have helped our products, and we look forward to seeing what they introduce in the future to aid developers in API testing. To read more about using the Kloudless Postman Collection, please read Chris’ walkthrough on getting set up with the collection here.


Published By

David Hallinan

David Hallinan is Head of Content at Kloudless. He enjoys painting, JavaScript, vintage synths, drum machines and forcing his sports allegiances on his children.

View all posts by David Hallinan