Skip to content


Postman provides an interactive application for issuing REST APIs calls to a server and reviewing responses.

Basically a REST API is an application program interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. The call is made using a URL - just like requesting a web page from your browser. In fact, when you request a web page from your browser, the browser is issuing a GET HTTP request for the page.

REST APIs for services such as the open metadata and governance services of Egeria use the full range of HTTP requests as follows:

  • GET - retrieving simple structures.
  • POST - creating, updating, deleting complex structures and retrieving long lists of information with paging.
  • DELETE - deleting simple structures.

With Postman it is possible issue these HTTP requests and experiment with what they do. The Egeria dojos use Postman collections to illustrate the calls and save you typing in the full URLs (which can be quite long :).

Egeria by default uses https:// requests with a self-signed certificate. Any Postman users therefore will need to go into settings->general and turn off 'SSL certificate verification' or requests will fail.

Setting up Postman

Postman is a free download with optional enterprise licenses for teams. It includes a wide variety of tutorials to help you go from novice to expert. Familiarity with Postman will help you get the most value from the Egeria tutorials.

Install Postman from the Postman downloads site . At the time of writing, 10.11.1 is current and recommended.

Once Postman is installed, start up the application. You should see an initial page that looks something like this (shown on an Intel-based Mac with Postman version 10.11.1):

Postman initial display

Initial overview displays an empty workspace

Setting up Postman with Egeria data

We will import two types of information from Egeria's code repository on GitHub:

  • Collections - these define the REST API calls to issue.
  • Environments - these define the values of replaceable variables in the API calls, such as host and server names.

Follow through these steps to configure your Postman environment:

Create a new workspace

Creating a workspace for egeria helps keep everything we'll work with together. If you mess up your postman files later, you can just create a new environment again to work with

Select the workspace menu at the top of the Postman interface and click 'Create Workspace'

Create Workspace

Enter 'Egeria dojo' into the Name field, add a summary into the Summary field, select the 'Personal' visibility option, and click 'Create Workspace'

Enter workspace name and summary

Your new workspace should display an 'Overview' tab with the new workspace name and summary displayed

New workspace overview

Importing Egeria Postman data

We now will individually import the Egeria Postman collections required for this dojo:

Click 'Import' and select 'Link' as the source

Select collection import source

Paste the URL found below for the 'Egeria-admin-services-operational' collection and click 'Continue'

Enter collection import link
In the 'Import Elements' tab, confirm the collection to be imported and click 'Import'

Confirm Collection to import

Confirm the 'Import Elements' tab displays 'Import Complete'

Collection imported successfully

Repeat the same procedure for the following Egeria collections:







Once all collections are imported, your workspace should display all of the imported collections to the left of the Overview:

Show all imported collections

All imported collections displayed

We must now import the environment required for this dojo:

Again, click 'Import' and select 'Link' as the source

Select environment import source

Paste the sample environment URL found below and click 'Continue'

Enter environment import link
In the 'Import Elements' tab, confirm the environment to be imported and click 'Import'

Confirm environment to import

Confirm the 'Import Elements' tab displays 'Import Complete'

Environment imported successfully

Updating Postman settings

Egeria uses secure connections. However the demo environment has self-signed certificates which Postman will not see as valid without further configuration. To simplify this process we will turn off certificate validation in postman:

In the upper right hand corner select the gear dropdown menu and click 'Settings'

Select Settings

Ensure 'SSL certificate verification' option is switched off

Disable certificate validation

Egeria Environment settings

The Import process will have imported some Egeria environment settings.

In general you can leave the values as default except for hostnames which should be pointed at the relevant Egeria platform. Tutorial content will walk you through this explicitly.

Let's make the Egeria environment the default in this workspace:

In the upper right hand corner of the Postman interface, click on the dropdown menu which currently lists 'No Environment' and select 'Egeria'

Select Egeria environment

To the right of the environment dropdown menu, click the 'Environment quick look' icon

Select environment quick look

You should be able to view your current environment configuration

View environment configuration


Postman is now ready to be used with Egeria. Refer back to the tutorials for specific examples, or experiment!

Instructions for contributing new Postman collections are located in the developer-resources .

Raise an issue or comment below