The API Measurement Secret: Know What Metrics Matter

Adam DuVander, August 2nd, 2012

Among the keys to a great API is one that is managed or measured. One of the common questions we get at ProgrammableWeb is “how should I measure my API?” Usually the problem behind the question is that there’s no shortage of things API providers can track. The secret to how great APIs measure is that they prioritize the metrics that matter.

Traffic Metrics

  • Total calls
  • Top methods
  • Call chains
  • Quota faults

Developer Metrics

  • Total developer count
  • Number of active developers
  • Top developers
  • Trending apps
  • Retention

Service Metrics

  • Performance
  • Availability
  • Error rates
  • Code defects

Marketing Metrics

  • Developer registrations
  • Developer portal funnel
  • Traffic sources
  • Event metrics

Support Metrics

  • Support tickets
  • Response time
  • Community metrics

Business Metrics

  • Direct revenue
  • Indirect revenue
  • Market share
  • Costs

These are just a sampling of the metrics that might be important to your API. What do you track and why is it important?

For other tips, see what makes a great API.

Photos by purplemattfish and William Warby

Tags: Issues
Both comments and pings are currently closed.

Comments are closed.

Follow the PW team on Twitter

ProgrammableWeb
APIs, mashups and code. Because the world's your programmable oyster.

John Musser
Founder, ProgrammableWeb

Adam DuVander
Executive Editor, ProgrammableWeb. Author, Map Scripting 101. Lover, APIs.