- 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
- Data formats
- Working with OpenAPI
- Collaborating in Postman
- Roles and permissions
- Managing your team
- Requesting access
- Team Settings
- Audit logs
- Intro to scripts
- Pre-request scripts
- Test scripts
- Test examples
- Branching and looping
- Postman Sandbox
- Postman Sandbox API reference
- Intro to collection runs
- Starting a collection run
- Using environments in collection runs
- Building workflows
- Running multiple iterations
- Sharing a collection run
- 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
- The API Workflow
- Managing and Sharing APIs
- Versioning APIs
- Viewing and analyzing APIs
- Validating Elements Against Schema
- Customizing Postman
- Find and Replace
- Purchasing Postman
- 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
- Publishing API documentation
Viewing and analyzing APIs
You can access reports on your APIs in the Postman web dashboard. API reports visualize data on API activities including creation, collection execution, test runs, and more, providing insights on performance, troubleshooting, and SLA adherence, as well as team and organization metrics.
To generate reports in Postman, first ensure you have carried out the following steps:
- Share your API
- Add a collection to the API
- Turn on Save Responses in History on the left of Postman
- Send a request from the collection
To view reports, in APIs on the left of the Postman app, select the API and click Reports.
The Team > Overview report provides organization level metrics, including new and active APIs, team size, and workspaces. Click to view more data on a particular metric.
Team reports provide the following information:
- Total number of APIs present in the team, including in private and public workspaces
- New APIs created within the team, not including new versions
- Active APIs having at least one request being sent through a linked collection in the Postman app request builder
- Team size as the number of user accounts in the team
- Empty workspaces with no collections in them
- Active workspaces with at least one revision during a recent period, not including personal workspaces
Team API requests are the count of requests sent over a period of time. The summary average is calculated by taking into account all days (even if no request is sent during a day).
In this example, 15 requests were sent on Jun 12. Over the next six days, no requests were sent. The 7-day average is 2.14 (15/7).
API reports provide a graphical representation of data and enable you to filter the data by collection and duration (last 7 or 30 days). You can view reports for any individual collections you have linked to an API.
Reports only track data from APIs you have shared to team workspaces. If your API is only shared to a personal workspace you will not see reports for it.
API reports provide the following information:
- Average response size of requests in bytes or kilobytes
- Average response time for your API to serve a request
- Number of error responses indicating error codes returned by your API
- Traffic in Postman indicating usage and API traffic for performance measurement
- Failed test runs indicating the number of failed tests in collection runs and monitors, for debugging and troubleshooting errors in your requests
The average response size is calculated based on the size of the response and the number of requests sent on a particular day.
In this example, the response size is shown for Jun 12. No request is sent on other dates in the graph.
The average response time is calculated based on the time taken to return the response of the request and the number of requests sent on a particular day.
In this example, the response time is shown for Jun 12. No response is received on other dates because no request is sent.
Summary average response size may not match the average of the graph, because raw data is accounted for when calculating averages. In order to determine an accurate average, Postman does not calculate averages using data from already derived averages.
Failed test runs are the number of failed tests for collection runs during a period of time. The summary average is calculated by taking into account all of the days in that time period (even if no requests are sent on certain days).
Reports are not generated in realtime. You may experience a lag of a few minutes to 24 hours in report data being available. You can view the last updated time for reports.
You cannot currently download or export your reports.
Postman reports track data sent only through the request builder, and not through Newman, collection runs, or monitors. However, failed test runs generate reports using collection runs.
You cannot view the details of entities you do not have access to.
If you don't see any data in your reports, or your data is incomplete (for example you have empty response times or sizes) this may be due to one of the following reasons:
- It's too early to check. The data refreshes every 24 hours.
- You may not have linked a collection to your API.
- You may not have sent a request—or you may have executed requests from monitoring, collection runs, or Newman, but not from the request builder in the Postman app.
- You may not have enabled Save Responses in the History tab in the Postman app.
- App sync is not successfully communicating with the Postman servers.
If none of the above reasons apply and you can't see your data, please file a GitHub issue.
You can use monitors to gain detailed insight into your APIs.