Advanced dev
Testing Backend APIs with Postman

Using Collections in Postman

Learn how collections are used in Postman and import an existing collection into your client.

While being able to build requests using a GUI is nice, Postman really starts to shine when you use collections. Postman Collections are simply a collection of pre-built requests that can be organized into folders, and they can be easily exported and shared with others. Postman itself ships with a collection named Postman Echo which contains some sample requests to demonstrate how to build requests for common use cases such as authentication, cookies, customizing headers, etc.

Read the Postman documentation on Collections

The Postman documentation goes over how to create a new Postman collection. Requests can be saved to collections, which can then be further organized into folders (only one level deep) within the collection.

Importing a Collection into Postman

Import the Conduit Postman Collection into Postman

In the top bar of the Postman Client on the left side, click on the Import button.

Click on the Import From Link tab in the Import menu and paste in the following link to import:

https://raw.githubusercontent.com/gothinkster/realworld/master/api/Conduit.postman_collection.json

Once the collection is imported, you'll be able to see a folder named Conduit in the Collections tab of the left side panel in Postman. These are all the requests needed in order to test the back-ends of our ProductionReady tutorial series. The requests are organized by which feature they are testing. Before we can run the requests in this collection, we need to configure an environment first. In the next section, we'll go over what Postman Environments are and how they can be used to make your requests reusable between your development and production setups.