New – This is where you will create a new request, collection, or environment.
Import – This is used to import a collection or environment. There are options such as importing from a file, folder, link, or pasting the raw text.
Runner – Automation tests can be executed through the Collection Runner. This will be discussed further in the next lesson.
Open New – Open a new tab, Postman Window or Runner Window by clicking this button.
My Workspace – You can create a new workspace individually or as a team.
Invite – Collaborate on a workspace by inviting team members.
History – Past requests that you have sent will be displayed in History. This makes it easy to track actions that you have done.
Collections – Organize your test suite by creating collections. Each collection may have subfolders and multiple requests. A request or folder can also be duplicated as well.
Request tab – This displays the title of the request you are working on. By default, “Untitled Request” would be displayed for requests without titles.
HTTP Request – Clicking this would display a dropdown list of different requests such as GET, POST, COPY, DELETE, etc. In Postman API testing, the most commonly used requests are GET and POST.
Request URL – Also known as an endpoint, this is where you will identify the link to where the API will communicate with.
Save – If there are changes to a request, clicking save is a must so that new changes will not be lost or overwritten.
Params – This is where you will write parameters needed for a request such as key values.
Authorization – In order to access APIs, proper authorization is needed. It may be in the form of a username and password, bearer token, etc.
Headers – You can set headers such as content type JSON depending on the needs of the organization.
Body – This is where one can customize details in a request commonly used in POST requests.
Pre-request Script – These are scripts that will be executed before the request. Usually, pre-request scripts for the setting environment are used to ensure that tests will be run in the correct environment.
Tests – These are scripts executed during the request. It is important to have tests as it sets up checkpoints to verify if the response status is ok, if retrieved data is as expected, and other tests.