- Installing and updating
- Navigating Postman
- Sending your first request
- Managing your account
- Syncing your work
- Discovering templates
- Creating your first collection
- Creating a workspace
- Setting up your Postman app
- Importing and exporting data
- Troubleshooting app issues
- Building requests
- Authorizing requests
- Receiving responses
- Grouping requests in collections
- Using variables
- Managing environments
- Visualizing responses
- Specifying examples
- Using cookies
- Working with certificates
- Generating client code
- Troubleshooting requests
- Scripting in Postman
- Writing pre-request scripts
- Writing tests
- Using the Collection Runner
- Scheduling runs with monitors
- Building request workflows
- Importing data files
- Working with your team
- Defining roles
- Requesting access
- Sharing your work
- Your private API network
- Commenting on collections
- Versioning APIs
- Using version control
- Using the API Builder
- Managing and sharing APIs
- Validating APIs
- Monitoring APIs
- 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
- Monitoring FAQs
- Analyzing with reports
- Documenting your API
- Authoring your docs
- Publishing your docs
- Viewing documentation
- Using custom domains
- Publishing templates
- Publishing to the API Network
- Submission guidelines
- Managing your team
- Purchasing Postman
- Configuring team settings
- Utilizing audit logs
- Onboarding checklist
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Microsoft AD FS
- Custom SAML in Azure AD
- Custom SAML in Duo
- Custom SAML in GSuite
- Custom SAML in Okta
- Custom SAML in Onelogin
- Custom SAML in Ping Identity
- Migrating to the current version of Postman
- Developing with Postman utilities
- Postman API
- Echo API
- Collection SDK
- Postman Runtime library
- Code generator library
- Postman Collection conversion
There are many possible reasons for your API requests not behaving as expected. You will see a message if Postman is not able to send your request, or if it does not receive a response from the API you sent the request to. The message will include an overview of the issue and a link to the Console, where you can access detailed info about the request.
Click View in Console to see the request detail in the Console and find out more about what went wrong.
- If Postman fails to send your request, you may be experiencing connectivity issues. Check your connection by attempting to open a page in your web browser.
- Some firewalls may be configured to block non-browser connections. If this happens you will need to contact your network administrators for Postman to work.
- If you are using a proxy server to make requests, check your configuration. By default, Postman uses the proxy settings configured in your operating system's network settings. The Postman Console will provide debugging information regarding proxy servers.
- You may experience issues using HTTPS connections. You can turn off SSL verification in the Postman Settings. If that does not help, your server might be using a client-side SSL connection, which you can configure in Postman Settings. Use the Postman Console to ensure that the correct SSL certificate is being sent to the server.
Incorrect request URLs
- If you are using variables or path parameters with your request, make sure the final address is structure correctly by opening the Console, which will display the URL your request was sent to when it executed. Unresolved request variables can result in invalid server addresses.
- Check whether you're accidentally using
http://in your URL (or vice versa).
- Check whether you're accidentally using
- It is possible that Postman might be making invalid requests to your API server. You can confirm this by checking your server logs (if available). If you believe this is happening, get in touch with the Postman team on the GitHub issue tracker.
Very short timeouts
- If you configure a very short timeout in Postman, the request could be timing out before completion, resulting in an error. Try increasing the timeout to avoid this issue.
- If your server sends incorrect response encoding errors, or invalid headers, Postman may fail to interpret the response.
Postman supports TLS version 1.2 or higher, which may not be supported if you are using an older browser or operating system.
The Postman console helps debug your requests when an API is not behaving as you expect. If you think the issue may be with Postman itself, the DevTools console provides internal debugging information you can also check out.
Every request sent via Postman is logged in the console, so you can view the detail of what happened when you sent a request.
The Postman console logs the following information:
- The primary request that was sent, including all underlying request headers, variable values, redirects, etc.
- The raw response sent by the server before it is processed by Postman
- The proxy configuration and certificates used for the request
- The network information such as IP addresses, ciphers, and protocols used
- Logs from
console.error()and asynchronous requests from test or pre-request scripts
Using log statements at appropriate locations in your test scripts will help you identify the source of any issues.
You can open the console from the button on the bottom left of Postman, by clicking
(CMD/CTRL + ALT + C), or selecting View > Show Postman Console.
The console pane will open. You will see network information, request and response headers and body for each request, together with any console output messages coming from your scripts.
You can filter by log message type, and toggle timestamps / network info.
Keeping the console open will increase the visibility of your network calls and log messages while debugging. The console will log the last 5K messages and 24 hours by default—you can also Clear the list.
The DevTools console provides additional internal debugging entries for the Postman app.
To access the DevTools console logs, open the View menu and select Show DevTools. In the DevTools window, click Console to see the app debug logs.
If you still can't get your requests to work, you can ask for help in the Postman forum. If you've tried troubleshooting and think the problem is with Postman, search the issue tracker on GitHub to check if someone has already reported the issue (and whether there is a known solution that you can use). If you're reporting a new issue, check out the guidelines. If you need to include confidential data, you can file a ticket with Postman support, including your console logs to help troubleshoot.