- Installation and updates
- Sending your first request
- Navigating Postman
- New button
- Creating the first collection
- Postman account
- Keyboard Shortcuts
- Troubleshooting In-app Issues
- Authorizing requests
- Working with Tabs
- Visualize API responses
- Validating Requests Against Schema
- Generate code snippets
- Using GraphQL
- Making SOAP requests
- Capturing HTTP requests
- Debugging and logs
- Troubleshooting API requests
- Intro to collections
- Creating collections
- Sharing collections
- Commenting on collections
- Managing collections
- Version Control for Collections
- Using Markdown for descriptions
- Importing and exporting data
- Working with OpenAPI
- Collaborating in Postman
- Roles and permissions
- Managing your team
- Requesting access
- Team Settings
- Audit logs
- Your private API network
- Intro to scripts
- Pre-request scripts
- Test scripts
- Test examples
- Branching and looping
- Postman Sandbox API reference
- Intro to collection runs
- Starting a collection run
- Using environments in collection runs
- Building workflows
- Running multiple iterations
- Sharing collection runs
- Working with data files
- Debugging a collection run
- Command line integration with Newman
- Integration with Jenkins
- Integration with Travis CI
- Newman with Docker
- Documenting your API
- Authoring your documentation
- Publishing your docs
- Viewing documentation
- Custom documentation domains
- Intro to mock servers
- Setting up a mock server
- Mocking with examples
- Mocking with the Postman API
- Matching algorithm
- Intro to Monitoring
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Running Postman monitors using static IPs
- Troubleshooting monitors
- FAQs for monitors
- Intro to Workspaces
- Creating Workspaces
- Using Workspaces
- Managing Workspaces
- Viewing changelogs and restoring collections
- Using the API Builder
- Managing and Sharing APIs
- Versioning APIs
- Viewing and analyzing APIs
- Validating API Elements Against Schema
- Customizing Postman
- Find and Replace
- Purchasing Postman
- Onboarding Checklist
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Configuring Microsoft AD FS with Postman SSO
- Setting a custom SAML in Azure AD
- Setting up custom SAML in Duo
- Setting up custom SAML in GSuite
- Setting up custom SAML in Okta
- Setting up custom SAML in Onelogin
- Setting up custom SAML in Ping Identity
- Intro to Integrations
- Custom Webhooks
- Microsoft Flow
- Microsoft Teams
A proxy server acts as a security barrier between your internal network and the Internet, keeping others on the Internet from accessing information on your internal network.
In basic web speak, a client makes a request to the server, and the server sends back a response.
A proxy server is an application or system that acts as an intermediary between your computer and the internet, or more specifically, the client and server. The proxy makes requests on your behalf to websites, servers, and other internet services.
The proxy can reside on your local machine, somewhere in your network, or at any point between your client and the destination server on the internet.
Similar to the way parents might speak to each other through a child, the child is a proxy relaying all communications between the 2 parents.
Parent 1: Ask your father if he can pick you up after school.
Timmy: Can you pick me up after school.
Parent 2: Yeah.
Timmy: Dad says yeah.
In this analogy, the child forwards the information on behalf of each parent. Besides just relaying information, proxies can do much more.
- Record all traffic between your machine and the internet
- Reveal the contents of all requests, responses, cookies, and headers
- Route traffic to specified internet locations
- Security from direct attacks
- DevOps load balancing
A proxy acts like a go-between to perform various functions. Postman has a built-in web proxy to capture API requests, the Postman Interceptor to intercept network traffic, and proxy settings to direct API requests.
This article describes how to configure the proxy settings in Postman to direct all requests made in the Postman app to route through a proxy server. This is different from capturing network traffic with the built-in proxy which allows Postman to intercept network traffic.
Postman's native apps for Mac, Windows, and Linux support configuring proxies. You can either specify to use a custom Global proxy or to use the system proxy defined in the operating system.
Use the Global proxy if all of your applications need to use the same proxy. Turn Global proxy on if you want to direct the requests from Postman go through a custom proxy server. Turning it off will direct the requests to not use the proxy server.
To configure the proxy settings, click the wrench icon on the right side of the header toolbar, choose “Settings”, and select the Proxy tab.
Postman allows you to configure Global Proxy Configuration that direct Postman to forward your HTTP or HTTPS requests through a proxy server. In other words, this will route all requests sent via the Postman app through a proxy server of your choosing.
- The Postman app is the client that sends a request through the selected proxy.
- The proxy server sends the request to the server.
- The server returns a response back through the proxy server.
Global proxy settings are disabled by default and can be turned on using the toggle switch.
Choose the type of proxy server by checking the appropriate checkboxes beside Proxy Type. By default, both
HTTPS are checked. This means that both HTTP and HTTPS requests will go through the proxy server.
The first field under Proxy Type is Proxy Server. Here, enter the host or IP address (without protocol) of the proxy server. The next field to Proxy Server is where the port of the proxy server is provided.
The Field below Proxy Server is Proxy Auth, turning this on makes the requests use Basic Authentication method, which requires a username and a password.
The Proxy Bypass setting lies below the Proxy Server option. A number of comma separated hosts can be provided here for which the requests do not use the proxy settings.
The Use System Proxy option allows Postman to use the system's default proxy configuration. It contains an
option to use
NO_PROXY environment variables of the said system.
If all of your applications need to use the same proxy, you might have a default proxy configured at the Operating System level. Use the system proxy settings to forward your HTTP or HTTPS requests in Postman through your OS’s default configuration. In other words, you are telling the Postman app and all requests sent using Postman to follow your OS's default configuration.
- The Postman app is the client that sends a request through your Operating System’s default configuration, which forwards the request to the proxy server.
- The system proxy server sends the request to the server.
- The server returns a response back through the proxy server.
System proxy settings are enabled by default. Any request made through Postman will go through the system proxy.
You can turn this setting on and off using the toggle switch. When turned off, all the requests are made directly. However, regardless of the proxy setting in the app, Postman will still use the system proxy if there is an environment variable set.
Note: If the Use System Proxy and the Global Proxy Configuration are both turned on, then the Global Proxy Configuration will take precedence.