Analyze developer engagement across your public APIs

Publisher analytics give you a full view into how developers engage with your public collections, forked collections, workspace updates, and your publisher profile, from discovery to adoption. You can view user activity over the last 6-month period by weeks or months. Use publisher analytics to show the impact of your presence on the Postman API Network, understand what’s working, and find where users get stuck.

To access these metrics, navigate to the Postman API Network and, in the left sidebar, click Analytics in the Publish section.

Key metrics and insights

Analytics provides the following metrics and insights.

Users

This section tracks how many developers interact with your content and how they engage with it. Use the user breakdown to measure how well your onboarding works and to find friction points.

• Active users — Anyone who viewed, forked, or made API calls during the selected time period. This is your broadest indicator of reach.
• API users — Active users who sent at least one request to your API with a Postman Collection. These users have progressed beyond interest to actual usage.
• New API users — Users calling your API for the first time. Tracking this metric helps you measure growth and new adoption.
• Successful users — Users who received at least one 2XX response. A 2XX response suggests these users have onboarded and can use your API.
• Error-only users — Users who made API calls but never received a successful response. High numbers can signal usability problems, often with auth setup or documentation.

Companies

Verified publishers see a breakdown of API calls and API callers by company, based on the email domain of the API users. Use it to understand usage trends in specific industries or among individual customers, and to see the reach of your content on the Postman API Network.

To see this data, get verified.

Views

Views reflect how often developers discover and engage with your content, which makes them a key indicator of visibility. Growing view counts suggest strong discoverability and interest. Drops may highlight content that needs promotion or updates. Views include public collections in your public workspaces and forked collections in users’ internal workspaces.

To change what a graph shows, click its data sources to turn them on or off. For example, in the views by content type graph, click Collections to hide the line for collections, then click it again to show it.

To increase views, consider the following:

• Getting verified improves visibility in search and explore.
• Publishing updates when collections change keeps your users informed.
• Promoting your content across docs, portals, and social media encourages developers to engage with it.

Forks

Forks are a strong signal that developers are ready to test and build with your API. When users fork one of your collections, they save a copy to their own workspace, where they can explore it and keep up with updates to the original collection.

Forks originate from the following places:

• Public workspaces — When developers discover and fork a collection directly from your public workspace.
• Run in Postman button — When users click a button embedded in your docs or website that forks a collection into their workspace.

API calls

API calls show how often developers are using your API through Postman. You’ll see the total call volume, which collections drive the most traffic, and where requests come from, including forks, your public workspace, notebooks, or autocomplete suggestions. Use this metric to understand which content leads to the most API activity.

API errors

This section surfaces issues that may block onboarding or API usage. You’ll see error rate trends over time and a list of collections with the most client-side (4xx) errors. High error rates may indicate gaps in documentation or auth configuration. Errors from new users often point to onboarding problems.

To reduce friction, you can do the following:

• Add a collection focused on authentication or setup.
• Use environment variables to streamline configuration.
• Enable Guided Auth to simplify user input.

To learn more about improving your public presence, see Publish your public APIs to the Postman API Network.