Publisher analytics gives you a full view into how developers engage with your public Postman content, from discovery to adoption. It’s your hub for insights into API visibility, usability, and engagement.
Each section includes a top content sidebar showing your most viewed, forked, or called assets, so you can quickly identify what’s performing well and why.
To access these metrics, navigate to the Postman API Network and, in the left sidebar, click Analytics in the Publish section.
Analytics provides the following metrics and insights.
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.
Views reflect how often developers are discovering and engaging 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.
To increase views, consider the following:
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:
Adding Run in Postman buttons can significantly boost forks and accelerate onboarding by letting developers get started wherever they discover your API.
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.
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:
Publisher analytics isn’t just about tracking, but about growth as well. Use this report to accomplish the following:
Need help improving your public presence? Explore the API Network Publishing Guide.
Last modified: 2025/08/05