Announcing public workspace metrics
We’re obsessed with helping developers get successful API calls. A successful API call is often the first signal that something you have built is working, and tens of thousands of companies already use the Postman API Network to create better developer experiences for their APIs, helping more than 30 million users get to their first successful API call faster.
API publishers on the Postman API Network already get monthly metrics on the adoption of their APIs—like the number of views, forks, and watchers—but how do they know if their developers can actually use their APIs successfully?
Today, we are excited to announce the launch of public workspace metrics in Postman. These metrics give API publishers visibility into how successfully developers can use their APIs and offer actionable insights to optimize the developer experience. API publishers with public workspaces can find a new tab in the Postman Reports section dedicated to public workspace metrics.
Key metrics on developer engagement
Postman’s new public workspace metrics feature will include the following metrics for your public collections:
Collection views: The total number of views or unique users viewing your public collection. You can use this to see how the total traffic on your public workspace has changed over time.
New collection forks: The number of new forks or the number of unique users forking collections in your public workspace.
Response code distribution: The number of API calls users make from collections forked from your public workspace. You can also see a distribution based on the response code classes (200s, 400s, etc.). You can use this to gain insight into how successful developers are at using your APIs. For example, a high number of 400s may indicate users cannot form valid requests, which you can address by improving documentation.
Total users vs. users facing authorization issues: The number of users facing friction in getting to a successful API call because of authorization issues. Postman also gives you recommendations to reduce this friction, such as setting up easier API authentication for your APIs.
You can choose to view these metrics month over month or week over week, and you can also filter these metrics down to specific workspaces and collections. Finally, you can also see these metrics and recommended improvements in summary emails sent to public workspace owners.
Putting public workspace metrics to use
“Postman’s new public workspace metrics gives us unparalleled insights into how users consume our APIs. This feature helps us tailor our content so that we deliver the best developer experience with detailed documentation and relevant examples.” says Philippe Ozil, Principal Developer Advocate at Salesforce.
“At PayPal, prioritizing the developer experience is fundamental to our mission. Our APIs are designed to empower hundreds of millions of customers to effortlessly execute global payment transactions every day,” says Mudita Tiwari, senior director of product at PayPal. “Utilizing public workspace metrics from Postman, we’re now equipped to pinpoint and address the challenges developers face, ensuring a smoother path to a 200 OK as quickly as possible.”
A.J. LaPorte, senior operations architect of HubSpot developer relations adds: “HubSpot is dedicated to helping our customers grow better by enabling developers that are building on our platform with a streamlined developer experience. Public workspace metrics enable us to get a pulse on how developers use our APIs and how we can better set them up for success with more relevant technical content.”
What’s more, public workspace metrics are available across all Postman plans. So what are you waiting for? Check out these reports today and help your API consumers get to a successful API call faster.
Don’t have a public workspace yet? See our simple guide to building your first public workspace, and if you are looking for inspiration, readd this blog post for APIs with the best developer experience in Postman.