Top 35 Postman
Interview Questions

Postman is an interactive, collaborative API development and testing platform. Originally built as a browser extension, it has evolved into a comprehensive desktop application that allows engineers to design, build, test, mock, and document REST, SOAP, GraphQL, and WebSocket APIs.

To send a GET request: 1) Open a new request tab, 2) Select 'GET' from the HTTP method dropdown list, 3) Enter the target endpoint URL in the address box, 4) Add query parameters in the 'Params' tab if needed, and 5) Click 'Send'.

Postman supports all standard HTTP methods: GET (retrieve data), POST (create data), PUT (replace data), PATCH (partially update data), DELETE (remove data), HEAD (retrieve headers only), OPTIONS (inspect allowed methods), and custom methods if needed.

You add query parameters by navigating to the 'Params' tab directly underneath the URL bar. Enter your key-value pairs in the grid, and Postman will automatically encode and append them to the end of the URL starting with a '?' symbol.

Params (Query Parameters) are part of the URL query string, usually used in GET requests to filter, sort, or paginate data. Body is the payload content sent inside the HTTP request stream, typically used in POST/PUT/PATCH requests to transmit complex data structures.

To export, click the three dots (...) next to a Collection, select 'Export', choose 'Collection v2.1 (Recommended)', and save the JSON file. To import, click the 'Import' button in the top left of the workspace and drag-and-drop the exported JSON file, folder, or link.

Workspaces are collaborative environments that organize API assets (collections, environments, integrations, and monitors). They act as shared workspaces where developers and QAs can collaborate in real-time, preventing resource duplication.

Collections are logical groups of related API requests. They are used to organize testing workflows, save request history, execute batch automation runs (using the Collection Runner), parameterize variables, and set up dynamic pre-request/test scripts.

To send a JSON POST request: 1) Select 'POST' as the method, 2) Navigate to the 'Body' tab, 3) Select the 'raw' radio button, 4) Choose 'JSON' from the dropdown list, and 5) Input your raw JSON schema inside the editor.

To pass headers, navigate to the 'Headers' tab below the URL bar. Enter your custom header fields in the key-value grid (e.g. key: `Content-Type`, value: `application/json`). Postman also automatically generates hidden auto-generated headers, which can be viewed by clicking '7 hidden'.

Environments are key-value sets of variables that represent target server deployment zones (e.g., Dev, QA, Staging, Production). You toggle between environments using the environment dropdown in the top right, allowing you to run the same test suite against different endpoints without modifying request URLs manually.

Postman uses variable scopes to manage configurations at different levels: Global (accessible across all collections in a workspace), Environment (active only when a specific environment file is selected), and Collection (active across all requests within a specific collection).

You write test scripts inside the 'Tests' tab using JavaScript and Postman's native `pm` library. These scripts execute automatically as soon as a response is received back from the server, allowing you to assert status codes, response times, headers, and body payloads.

Pre-request Scripts execute *before* the HTTP request is sent to the server. They are used to generate dynamic data, set headers dynamically, or sign requests. Tests scripts execute *after* the response is received, primarily used to run assertions and handle data storage for request chaining.

The Collection Runner is a built-in Postman utility that executes all requests within a collection in a sequence (or a custom order). It supports configuring iteration counts, importing external CSV or JSON test data files, pausing between calls, and exporting comprehensive execution reports.

Postman natively supports standard authentication protocols: Inherit Auth from Parent (default), No Auth, API Key, Bearer Token, Basic Auth, Digest Auth, OAuth 1.0, OAuth 2.0, Hawk Authentication, AWS Signature, and NTLM Authentication.

In the 'Authorization' tab, select 'OAuth 2.0'. In the configuration panel, input the Auth URL, Access Token URL, Client ID, Client Secret, Scope, and Grant Type. Click 'Get New Access Token' to trigger the auth flow, and Postman will automatically fetch and apply the bearer token for your subsequent API calls.

API automation in Postman is achieved by combining three elements: 1) Writing JavaScript test assertions inside the 'Tests' tab of your requests, 2) Grouping requests in structured Collections, and 3) Running them headlessly in CI/CD pipelines via the Newman CLI.

Newman is the official, open-source command-line collection runner for Postman. It is built on Node.js and allows you to run Postman collections headlessly directly from your command-line interface, terminal, or build machine without opening the Postman desktop application.

You validate JSON responses inside the 'Tests' tab by parsing the response body into a JavaScript object via `pm.response.json()`, and writing assertions using the bundled Chai assertion library.

The 'Tests' tab is the execution playground for post-request scripts. It runs automatically inside a sandboxed JavaScript environment immediately after a request finishes, serving as the central hub for executing assertions, validating schemas, logging parameters, and setting environment variables.

You check response status codes using Postman's built-in `pm.response` assertion helpers. You can check for exact numbers, use semantic name validation, or verify a range of allowed codes.

Request chaining is achieved by: 1) Sending a request to retrieve data, 2) Extracting the target value in its 'Tests' script, 3) Saving it as an environment or collection variable, and 4) Referencing that variable using double curly braces `{{variableName}}` in the URL, header, or body of subsequent requests.

Dynamic values are handled using Postman's built-in dynamic variables (prefixed with a `$`) directly in your endpoints/bodies, or by using JavaScript's native generators (like `Math.random()`, `Date.now()`, or the bundled `uuid` library) in your Pre-request Scripts.

A Postman Mock Server is a cloud-hosted simulator that returns preconfigured mock responses (based on saved request Examples). It allows frontend developers or QA engineers to execute tests against a realistic simulated backend before the actual API is built or when the staging server is offline.

Postman is integrated into CI/CD pipelines by running the Newman CLI runner inside your pipeline scripts (e.g., Jenkinsfile, GitHub Actions yaml, GitLab CI yaml). The pipeline fetches code, installs Node.js and Newman, executes the test suite, and generates XML reports that the CI system parses for pass/fail checks.

Postman Monitors are cloud-based cron triggers that execute collections at scheduled intervals (e.g. hourly, daily) in the Postman cloud. They monitor API availability, latency, correctness, and performance from multiple geographic regions, sending alerts via Slack or Email on failure.

Postman automatically generates web-based API documentation directly from your Collections. By adding clear descriptions to collections, folders, and individual requests (supporting Markdown formatting), and saving successful response Examples, you can generate a professional, interactive public/private API portal with a single click.

To test SOAP APIs in Postman: 1) Set the HTTP method to 'POST', 2) Set the 'Content-Type' header to `text/xml` (or `application/soap+xml`), 3) Navigate to the 'Body' tab, select 'raw' and choose 'XML', and 4) Input the full SOAP envelope (with body and parameters) inside the XML editor.

Handling error responses involves writing assertions that verify the API fails gracefully when negative inputs are supplied. You should assert the appropriate 4xx/5xx status code, verify the error header type, and validate the structural schema of the returned error payload.

To debug API requests: 1) Open the 'Postman Console' (View -> Show Postman Console or click 'Console' in the bottom left), 2) Inspect the detailed execution flow, including raw request/response headers, sent body payloads, and connection logs, and 3) Inject logging commands like `console.log()` into Pre-request/Tests scripts.

Scripts in Postman refer to Pre-request and Tests JavaScript files that execute within sandboxed VM execution contexts. They enhance API testing by allowing teams to automate token handshakes, encrypt payloads, write complex data validations, and control collection execution flows dynamically.

To test GraphQL in Postman: 1) Open a new request, 2) Select 'POST' as the method, 3) Select the 'Body' tab, 4) Choose the 'GraphQL' radio button, and 5) Input your GraphQL Query or Mutation on the left editor panel, and pass variables on the right variables JSON panel.

To handle file uploads: 1) Select 'POST' as the method, 2) Navigate to the 'Body' tab, 3) Select the 'form-data' radio button, 4) Enter a key name, hover over the right side of the key field, and select 'File' from the dropdown list, and 5) Click 'Select Files' to upload a file from your local filesystem.

Postman's primary advantages include: 1) A highly visual, premium user interface that reduces the barrier of entry for manual QAs, 2) Seamless real-time collaboration with workspaces, 3) Robust JavaScript scripting for complex automation, 4) Headless Newman runner for CI/CD, and 5) Built-in mock servers and API documentation portals.