Skip to content

Postman API Testing

Postman is a free API testing tool which you can use to quickly set up API requests and modify them accordingly, after reviewing the server's response. It is currently one of the most popular tools used in API testing. With Postman, you can test your API by visually creating your own requests and viewing the results. Some would say that Postman is the GUI version of cURL.

Learn by example

Check out our example Postman repository.

Getting Started

This guide will get you started with using Postman to test API endpoints and importing your own results to Calliope.

To make your very first request, you will first have to select what HTTP response status code. and the body of the response. You can customise data such as the request here..

Postman interface


APIs use authorisation to ensure that clients who request data have the correct permissions to request said data. You can pass authorisation details along with any request you send in Postman. It is recommended you use the Authorization tab in Postman to include your API key.

For example, to interact with the Calliope API you would select the type as API key, with as key 'x-api-key', along with your API key as its value. This will automatically generate a header called x-api-key with your API key as its value for this request.

It is recommended you either use environment variables or that you set up authorisation in the parent collection. The benefit of setting up authorisation in the collection rather than each individual request is that all requests in the collection automatically know how to authorise.

GET Requests

A GET request is one of the most common and straightforward types of requests. It often only contains information about who's making the request. For example, GET requests often contain information about the browser that the client uses, and in our example above, the request included an API key for authorisation of the client.

Anytime you visit a website, no matter how basic, your browser is making a GET request to a server, and the server is responding with the HTML, CSS, and JS files that the webpage stores. When you make a GET request in Postman, the server does not specifically know that you are using Postman to make this request, and will respond the same as if you were to visit it with for example Mozilla Firefox.

POST Requests

POST requests are slightly more complicated than GET requests as they often have a request body used, for example, to tell the server to add an entry to the database. Often this is raw JSON data with a content-type of application/json.

In the context of importing test results to Calliope using POST requests it is useful to know that Calliope does accept JSON but prefers to receive multipart/form-data with file[] as the key for the request body and then select your test result files as the value.

The difference between these two methods is that contrary to a raw JSON body, the uploaded file(s) will include their metadata which Calliope uses to improve your test results.

Postman Request Body


To be able to start using your Postman scripts in an automated process, click here. You can read more about how Calliope supports Newman JSON output here.

Calliope Collection

The Calliope Collection is a full set of requests that you can use with the Calliope API. To get started with trying out the Calliope API using our Postman Collection, follow the steps below.

  1. Download our Postman Calliope Collection here.
  2. Import the Calliope Collection, called "Calliope Collection.postman_collection.json".
  3. Right-click the Calliope Collection and click edit then click the Variables tab.
  4. Fill in your API key as the current value for apiKey.
  5. If you have no profiles yet, create a company, give it a group and create a profile.
  6. Now select your newly created profile. The URL will look something like
  7. Return to Postman and for the groupId current variable enter the number that's behind /groups/ in your URL, in our example it's 1.
  8. Now for the profileId current variable enter the number that's behind /profiles/ in your URL, in our example it's 2.
  9. Make sure that the baseURL in your request represents the environment you're working on. So sometimes needs to change to to make the request work.
  10. The Calliope Collection is now set up and ready to go. Click any request and you should be able to fire a request by clicking Send. Import requests require you to select a file first in the Body tab of the request. The ZIP file you downloaded earlier includes an example file for each supported format, at the time of writing.

Integrating with Calliope Gitlab CI

Renaming uploaded file before uploading to Gitlab

After you have made your changes in the Postman, you need to Export your collections by clicking on View More Actions on the collection and Click Export.

If you use Post request in your API Call, you need to rename your upload source:

  1. Right click and edit your postman collection with notepad++
  2. Search your Post scenario
  3. Rename your src file path, for example: C:/Projects/rootmyproject/upload/reports/myfile.json to upload/reports/myfile.json

gitlab-ci.yml setup

The file is where we tell GitLab what command to run when a job gets triggered. To integrate your Postman to gitlab you should use something like this. If you want to know more about our calliope gitlab integration, simply click this link


    name: postman/newman_alpine33
    entrypoint: [""]

    - test

    stage: test
      - apk add zip unzip
      - newman run <YOUR_COLLECTION>.json -r cli,json
      - ls
      when: always
      expire_in: 1 week
      - cd newman; zip -r ../ *.json; cd ..
      - ls
      - apk add curl
      - >
        curl -X POST
        -H "x-api-key: ${API_KEY}"
        -F file[]
        ""${PROFILE_ID}"/import" -k

The following variables are defined:

  • API_KEY: Required to import tests to Can be found on your account page
  • PROFILE_ID: Tests will be imported in one of your profiles on You can find the ID in the curl command (see below).

The 'script:' part is the command that is going to run when the job gets triggered.

  • newman run <YOUR_COLLECTION>.json -r cli,json runs all the Postman tests and stores the results in 'newman/{filename}.json'.
  • Because newman generate a randomly named file, we need to zip it first using zip -r ../ *.json this command.
  • curl -X POST ... will import the tests into the platform.