Analyze developer engagement across your public APIs

Publisher analytics gives you a full view into how developers engage with your public Postman 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. It’s your hub for insights into API visibility, usability, and engagement.

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 deeply they engage. The user breakdown is especially useful for identifying onboarding effectiveness and potential 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. These users likely onboarded successfully and are able to 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.

Views

Views reflect how often developers discover and engage with your content. This is a key indicator of visibility. Consistently high or growing view counts suggest strong discoverability and interest, while drops may highlight areas that need promotion or updates. Views include public collections in your public workspaces as well as forked collections in users’ internal workspaces. You can click the different data sources on a graph to turn them on or off to get different views of the data. For example, in the views by content type graph, you can click Collections to hide the line representing views by 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 alert and informed.
Promoting your content across docs, portals, and social media incites engagement from developers and other potential users.

Forks

Forks are a strong signal that developers are ready to test and build with your API. By forking, your users save a copy of one of your collections to their own workspace so they can explore it, while simultaneously keeping up with the original collection updates.

Forks originate from the following places:

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

Adding Run in Postman buttons can significantly boost forks and accelerate onboarding by letting developers get started wherever they discover your API.

API calls

API calls show how often developers are using your API through Postman.

You’ll see the total call volume, which collections are driving the most traffic, and where requests are coming from, including forks, your public workspace, notebooks, or autocomplete suggestions.

This metric can help you understand what content leads to the most meaningful API interaction.

API errors

This section surfaces issues that may block successful onboarding or API usage.

You’ll view error rate trends over time and a list of collections with the most client-side (4XX) errors. High error rates, especially from new users, may indicate gaps in documentation or auth configuration.

To reduce friction, you can do the following: