Overview

11 Monitoring and analytics: Measuring API product metrics

Monitoring and analytics in API delivery are presented as continuous feedback mechanisms that help teams improve both product outcomes and technical reliability. The chapter connects these practices to DevOps and APIOps by showing that metrics should not be collected for their own sake, but used to study what is happening in production, validate improvement ideas, and guide the next iteration of the product. Product analytics is framed as especially important because it reveals how the API is contributing to business goals, not just how the system is performing technically.

The chapter emphasizes that API product metrics should follow the developer journey, since developers are the primary users of an API product. A journey map helps teams identify meaningful touchpoints from discovery through evaluation, build, production usage, and scaling, and then attach metrics at the moments where developers experience value. The main metric categories discussed are discovery, engagement, acquisition, activation, retention, and experience, with examples such as visitors to the developer portal, time to first call, daily active users, time to first transaction, user retention, conversion rate, and top users by production usage. The overall message is to use a focused set of leading indicators that support a north-star business metric rather than trying to measure everything.

The chapter also distinguishes product analytics from API monitoring for technical health. Monitoring focuses on latency, traffic, error rates, saturation, and related infrastructure and service-level signals, with the RED method highlighted as a practical framework for microservices. It explains the importance of alerts, synthetic monitoring, rate limits, and service concepts such as SLIs, SLOs, and SLAs so teams can detect failures quickly and maintain a predictable user experience. Together, product analytics and operational monitoring give API teams the visibility they need to improve adoption, reduce friction, and keep the API healthy over time.

API monitoring and product analytics are in the operation stage of the API product delivery life cycle.
figure
API product improvements as PDSA cycle
figure
The beginning of a developer journey map, showing the job the developer seeks to fulfill at each stage
figure
Extending the developer journey map with touchpoints
figure
Extending the developer journey map with API product metric categories
figure
A section of the developer journey map showing how the API team has defined metrics they want to capture to drive improvements in the Product Catalog API
figure
The workflow file simulates user sign-ups to a developer portal and API calls to the gateway. It sends the associated user action events and API call events to Moesif.
figure
Creating a dashboard to save your analytics reports
figure
Event stream to Moesif
figure
Creating a time series report to view new user sign-ups in Moesif
figure
Bar chart showing the trend of sign-ups over the past three days
figure
Report criteria for the report on recently signed-up users
figure
Details of recently signed-up users
figure
TTFHW value on the lookup report for recently signed-up users
figure
Setting the criteria for TTFHW funnel analysis
figure
In this example run, the TTFHW for the group of six users who went on to make API calls after signing up is 6 minutes 19 seconds.
figure
DAU criteria to show active users as those making API calls with an /api base path
figure
Example DAU time series chart
figure
Add an additional criteria step, First Production Call, to the User Funnel Analysis report to update it to show the TTFT value.
figure
Updating the User Funnel Analysis chart to show the TTFT
figure
Setting the user retention chart criteria
figure
User retention chart
figure
The User Funnel Analysis report shows the conversion rate of users who make a production API call.
figure
Criteria to show the top five API users in production criteria based on the number of API calls they make
figure
Top API users by usage
figure
Example latency chart in Moesif, tracing the 90th percentile latency of two endpoints /messages/:id and /groups/id
figure
Time series report showing requests per minute and a rate limit marker
figure

Summary

  • API product metrics provide a basis for decision-making and benchmarking API product improvement goals.
  • A developer journey map visualizes the process that developers go through to discover and use your API. Drawing a developer journey map helps you define the important product metrics to capture at each stage in order to paint a picture of the developer experience.
  • Using an API product analytics tool helps you capture, visualize, and share important product metrics with your team. These product metrics include new user sign-ups, TTFHW, DAU, TTFT, user retention, conversion rate, and top API consumers.
  • The RED method is a popular monitoring formula that can be applied to API technical performance monitoring. It captures the request rate, error rate, and duration.
  • Rate limits indicate the saturation point of your API, and you should set them to protect your API from excessive usage that can lead to a poor user experience.
  • To set monitoring and alerting, you need to define the SLOs for your API.

FAQ

What is the difference between API product analytics and API monitoring metrics?API product analytics measure how developers discover, evaluate, adopt, retain, and value your API product from a business perspective. API monitoring metrics focus on the technical health of the API, such as latency, traffic, and error rates, to help detect and diagnose operational issues.
Why are API product metrics important in the operation stage of the API life cycle?They provide continuous feedback on how the API is performing as a product in production. This helps the team understand whether changes are improving adoption, activation, retention, and overall business outcomes.
What is the PDSA cycle, and how does it apply to API product development?PDSA stands for Plan, Do, Study, Act. In API product development, teams plan an improvement, implement it, study the product metrics to validate the result, and then act on the learning before starting the next iteration.
What is a developer journey map?A developer journey map shows the path a developer takes from discovering an API to using it in production and at scale. It helps teams identify key touchpoints where product metrics can be collected to measure the developer experience.
What are the main categories of API product metrics?The chapter groups API product metrics into six categories: discovery, engagement, acquisition, activation, retention, and experience metrics. Each category measures a different part of the developer journey and supports product improvement decisions.
What is Time to First Call (TTFC) or Time to First Hello World (TTFHW)?TTFC or TTFHW is the time it takes a new user to make their first API call after signing up. It is an acquisition metric that indicates how quickly a developer can get started with the API.
What is Daily Active Users (DAU) for an API?DAU is the number of unique users making API calls in production within a day. For API products, this is often based on production API keys or tokens and is used as a key activation metric.
What is Time to First Transaction (TTFT)?TTFT is the time it takes a user to make their first API call in production. In some cases, it may mean the time to complete the first meaningful business transaction, not just the first request.
Why are retention metrics useful for API products?Retention metrics show whether developers keep coming back to use the API over time. They help measure loyalty, stickiness, and churn, often by analyzing repeat requests or cohort behavior over a 7-day or 30-day window.
What are RED metrics in API monitoring?RED stands for Request rate, Error rate, and Duration. These metrics help teams monitor service throughput, failed requests, and request latency, especially in microservice and API environments.

pro $24.99 per month

  • access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
  • choose one free eBook per month to keep
  • exclusive 50% discount on all purchases
  • renews monthly, pause or cancel renewal anytime

lite $19.99 per month

  • access to all Manning books, including MEAPs!

team

5, 10 or 20 seats+ for your team - learn more


Close
choose your plan

team

monthly
annual
$49.99
$499.99
only $41.67 per month
  • five seats for your team
  • access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
  • choose another free product every time you renew
  • choose twelve free products per year
  • exclusive 50% discount on all purchases
  • renews monthly, pause or cancel renewal anytime
  • renews annually, pause or cancel renewal anytime
  • Automating API Delivery Automating API Delivery ebook for free
Close
choose your plan

team

monthly
annual
$49.99
$499.99
only $41.67 per month
  • five seats for your team
  • access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
  • choose another free product every time you renew
  • choose twelve free products per year
  • exclusive 50% discount on all purchases
  • renews monthly, pause or cancel renewal anytime
  • renews annually, pause or cancel renewal anytime
  • Automating API Delivery Automating API Delivery ebook for free
Close
choose your plan

team

monthly
annual
$49.99
$499.99
only $41.67 per month
  • five seats for your team
  • access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
  • choose another free product every time you renew
  • choose twelve free products per year
  • exclusive 50% discount on all purchases
  • renews monthly, pause or cancel renewal anytime
  • renews annually, pause or cancel renewal anytime
  • Automating API Delivery Automating API Delivery ebook for free