View reports about workspaces

Workspace reports give you insights into how your team uses Postman across workspaces, including active users, active workspaces, API calls, and usage trends over time. Use these reports to understand how your team is using Postman, identify trends in your API usage, and make informed decisions about scaling your organization.

To access workspace reports, from your homepage, click Reports in the left sidebar. In the Reports dashboard sidebar, click Workspaces to view workspace reports.

You can also explore Postman’s analytics reports programmatically using the Analytics endpoints in the Postman API. For more information, see the Postman Public Workspace.

Workspaces overview

The workspace Overview report gives you a snapshot of high-level information about your team’s workspaces, including the number of active users, active workspaces, API requests, and usage trends over time. Current usage metrics (last 30 days) show you how your team is currently using Postman. Usage trends over time (last six months) help you understand how your team’s use of Postman is evolving, identify growth patterns, and spot potential issues or opportunities for improvement.

Current usage

• Active users — Users who used Postman at least once, with the percentage difference compared to the previous period, followed by the top five active users by API requests sent.
• Active workspaces — The number of workspaces with at least one action in the last 30 days, with the percentage difference compared to the previous period. Actions include views, edits, or sent API requests. This metric is followed by the top five active workspaces by API requests sent.
• API requests — The number of API requests made in the last 30 days, followed by the top five collections by API requests sent.

Usage trends over time

Usage is tracked over a period of six months, with partial data for the current month. You can hover over any data point in the charts to see the exact value for a given month.

• User distribution over time — Shows how your team’s user makeup and license usage change over time. This metric helps you understand who has access to your workspaces, how actively Postman is being used, and whether your available licenses are fully utilized.

  • Team member — Total The number of team members.
  • Active users — The number of team members actively using Postman.
  • Partner — The number of partner users invited to the team.
  • Guests — The number of guest users in the team.
  • Unused licenses — The number of unused team member licenses.

  Tracking these trends can highlight growth, unused capacity, or changes in collaboration patterns.

  To manage users and licenses effectively, consider the following actions based on user distribution trends:

  • Reviewing inactive users to ensure access is still needed.
  • Monitoring guest and partner access to maintain the right level of visibility.
  • Reassigning unused licenses as your team grows.
  • Watching changes over time to plan for future license needs.

• Team member engagement over time — Tracks user progression through the API adoption funnel, showing active users, API users, new API users, successful users, and error-only users. This helps teams understand user onboarding effectiveness and identify users needing support.

  • Active users — The number of users active in the selected month.
  • API users — The number of users who made at least one API call.
  • New API Users — The number of users making API calls for the first time.
  • Successful API users — The number of users whose API calls were mostly successful.
  • Error-only API users — The number of users who encountered only error responses. These metrics show how users interact with your workspaces and whether they’re able to make successful API calls.

  Tracking engagement over time can highlight onboarding gaps, usability issues, or opportunities to improve documentation and setup.

  To improve user engagement, consider the following actions:

  • Reviewing onboarding content for users who make API calls but don’t see successful responses.
  • Adding clear examples and documentation to help new users get started faster.
  • Monitoring trends over time to spot drops or improvements in API usage.
  • Comparing new users to successful users to identify where users get stuck.

• API requests by response code — Breakdown of API response codes (2xx, 4xx, 5xx) over time. Other errors are also captured here. However, these typically indicate technical issues within your API rather than usability problems.

  • 2xx (Success) — The number of successful API responses (2xx).
  • 3xx (Redirect) — The number of redirection responses (3xx).
  • 4xx (Request error) — The number of client error responses (4xx).
  • 5xx (Server error) — The number of server error responses (5xx).

  Tracking response codes over time can highlight improvements or regressions in API performance and usability.

  To reduce your 4xx rates, consider the following actions:

  • Creating an overview collection with step-by-step instructions for setting up auth.
  • Setting up Guided Authorization for your API domains.
  • Using environment variables to build the authorization into all of your requests from a single place.

• Active workspaces over time — Distribution of workspace types (team, private, partner, public) over time.

  • Internal workspace — The number of internal workspaces.
  • Partner workspace — The number of partner workspaces.
  • Private workspace — Count of internal private workspaces.
  • Public workspace — The number of public workspaces.

  Tracking active workspaces helps you understand how your team organizes work, collaborates internally and externally, and how workspace usage grows or stabilizes over time.

  An increase in active workspaces often reflects new projects or collaboration needs, while a stable or declining trend can indicate consolidation or cleanup.

  To manage workspaces effectively, consider:

  • Reviewing inactive or unused workspaces to reduce clutter.
  • Choosing the right workspace type based on collaboration needs.
  • Monitoring growth trends to plan governance and access.
  • Ensuring workspaces are clearly named and purpose-driven.

• Elements in workspaces over time — Total count of workspace elements (collections, environments, mocks and monitors) over time.

  • Collections — Groups of saved API requests you can run and reuse.
  • Environments — Sets of variables that let you switch between setups, like test and production.
  • Mocks — Simulated APIs that return example responses without calling a real server.
  • Monitors — Automated checks that run requests on a schedule to track API health.
  • Flows — Visual workflows that connect requests and logic without writing code.

  Workspaces are made up of different elements, each supporting a part of your API workflow. Viewing metrics for these elements helps you understand how your workspace is being used, where teams spend time, and which areas may need attention.

  High activity usually means an element is actively supporting development or collaboration. Low or declining activity can signal outdated setup, unused resources, or opportunities to simplify your workspace.

  Keep in mind that different elements naturally behave differently. For example, monitors run on schedules, while collections depend on manual use. Interpreting metrics in context helps you make better decisions.

  To improve workspace effectiveness, consider the following actions based on element activity:

  • Reviewing elements with little or no activity and archiving anything no longer in use.
  • Checking highly used elements to ensure they’re documented and easy to reuse.
  • Aligning environments and mocks with current development stages.
  • Making sure monitors and flows reflect your most important workflows.

Internal Workspaces report

View internal workspace metrics and team collaboration insights.

Current usage

• Active users — The total The number of users who have performed at least one action in a workspace in the last 30 days, with the percentage difference compared to the previous period, followed by top five active users by API requests sent.
• Active workspaces — The number of active workspaces in the last 30 days, with the percentage difference compared to the previous period. Actions include views, edits, or sent API requests. This metric is followed by the top five workspaces by API requests sent.
• API requests — The number of API requests made in the last 30 days, followed by the top collections by API requests sent.

Usage trends over time

Usage is tracked over a period of six months, with partial data for the current month. You can hover over any data point in the charts to see the exact value for a given month.

• Workspaces created over time — Distribution of internal workspaces created into team-shared and private categories.

  • Private workspaces — The count of internal private workspaces.
  • Shared workspaces — The count of internal team-shared workspaces.

  An increase in workspaces can indicate growing adoption or new projects, while slower growth may suggest consolidation into existing spaces. Looking at private and shared workspaces separately provides insight into how collaboration happens across your team.

  To better understand workspace growth, consider the following actions:

  • Reviewing whether new workspaces are created for clear purposes.
  • Encouraging shared workspaces when collaboration is needed.
  • Cleaning up unused or inactive workspaces to reduce clutter.
  • Watching trends over time to plan for team and project growth.

• Elements in workspaces over time — Total count of workspace elements (collections, environments, mocks, monitors, and flows) over time.

  • Collections — Groups of saved API requests you can run and reuse.
  • Environments — Sets of variables that let you switch between setups, like test and production.
  • Mocks — Simulated APIs that return example responses without calling a real server.
  • Monitors — Automated checks that run requests on a schedule to track API health.

  Workspaces are made up of different elements, each supporting a part of your API workflow. Viewing metrics for these elements helps you understand how your workspace is being used, where teams spend time, and which areas may need attention.

  High activity usually means an element is actively supporting development or collaboration. Low or declining activity can signal outdated setup, unused resources, or opportunities to simplify your workspace.

  Keep in mind that different elements naturally behave differently. For example, monitors run on schedules, while collections depend on manual use. Interpreting metrics in context helps you make better decisions.

  To improve workspace effectiveness, consider the following actions based on element activity:

  • Reviewing elements with little or no activity and archiving anything no longer in use.
  • Checking highly used elements to ensure they’re documented and easy to reuse.
  • Aligning environments and mocks with current development stages.
  • Making sure monitors and flows reflect your most important workflows.

• API requests by response code — Breakdown of API response codes (2xx, 4xx, 5xx) over time. Other errors are also captured here. However, these typically indicate technical issues within your API rather than usability problems.

  • 2xx (Success) — The number of successful API responses (2xx).
  • 3xx (Redirect) — The number of redirection responses (3xx).
  • 4xx (Request error) — The number of client error responses (4xx).
  • 5xx (Server error) — The number of server error responses (5xx).

  To reduce your 4xx rates, consider the following actions:

  • Creating an overview collection with step-by-step instructions for setting up auth.
  • Setting up Guided Authorization for your API domains.
  • Using environment variables to build the authorization into all of your requests from a single place.

• Collections with the highest error rates — Aggregated error metrics (4xx, 5xx responses) per collection, helping identify collections with the highest error rates.

  • 4xx Errors percentage — The number of 4xx responses for the collection in the selected period.
  • 5xx Errors percentage — The number of 5xx responses for the collection in the selected period.

  High error rates can signal issues with request setup, authentication, or API reliability, and they often point to friction for users trying to successfully use your APIs.

  Reviewing these collections helps you identify where users may be getting stuck and prioritize improvements that reduce errors and improve onboarding, testing, and overall API usability.

  To reduce error rates in collections, consider the following actions:

  • Reviewing request configuration, parameters, and headers.
  • Improving authentication setup and examples.
  • Adding clearer documentation or usage guidance within the collection.
  • Testing requests across environments to catch setup issues early.

Partner Workspaces report

View partner workspace metrics and external collaboration insights.

Current usage

• Needs attention — Click to view partners experiencing API issues or low activity in the last 30 days.
• API success rate — Click to view the percentage of successful API calls (2xx responses) across partner workspaces in the last 30 days.
• Pending invitations — Click to view the The number of pending invitations for partner workspaces.

Usage trends over time

Usage is tracked over a period of six months, with partial data for the current month. You can hover over any data point in the charts to see the exact value for a given month.

• Partner onboarding funnel — Tracks partner progression through the onboarding funnel, showing the The number of total partners, workspaces visited, viewed collections, requests sent, and successful API responses. Helps organizations measure the effectiveness of their partner programs and identify engagement opportunities.

  By viewing this funnel, you can identify friction points in the onboarding journey and focus improvements on the steps that matter most for helping partners get to their first successful API response.

  To improve partner onboarding, consider the following actions:

  • Reviewing steps with the biggest drop-offs to identify missing guidance or setup issues.
  • Improving documentation and examples for authentication and requests.
  • Providing clearer next steps after partners visit a workspace or view a collection.
  • Tracking progress over time to measure the impact of onboarding improvements.

• Partner API calls — Shows the The number of aggregated API call counts across workspaces. View the results, success rate, and last active status for each partner.

  This metric helps you understand how your partners are engaging with your APIs, which partners are most active, and where they may be encountering issues. It also provides insight into the success rates of partner API calls, which can indicate how well your APIs are working for external users.

  You can expand each partner to see a breakdown of their API calls by request, collection, error code, and timestamp. You can select specific partners from the Show all dropdown.

  You can also download this data for further analysis. This detailed view helps you identify specific requests or collections that may be causing issues for partners, allowing you to prioritize improvements that will have the biggest impact on partner success.

Public Workspaces report

Click Public Workspaces to access Publisher analytics. This report gives you a full view into how developers engage with your public collections, forked collections, workspace updates, and your publisher profile, from discovery to adoption.