Mashery API Reporting Screenshots

Mashery's reporting engine gives you a quick snapshot of how your API is being used, and allows you to drill down to the details of which developers are using it, when and how much. We also give you analytics on the growth of your developer community and the reach of your API distribution channel.

Usage Reporting Dashboard

Start on the API tab for an overview of the day's calls. The little graphs are called "sparklines" and either show a general trend of the data in question or break it down into shorter timeframes. In this case, the sparklines show the hourly numbers during the date in question

Sparklines expand

Click on a sparkline, and it zooms in to show you the detailed data. In this case, the Average Calls per Developer on an hourly basis.

7 Day View

Click on the "7 Day" tab to view a full week's data.

Developer Tab

This tab gives a quick overview of the most active developers during the period in question, and the new developer signups. You can see how many new users also registered for developer keyss, and how many of those new keys actually started making calls to the API. You can also see which users have reached their limits and had access restricted (shown by the red dot).

Raw Developer Data

Want to see all developers who were active during a given week? Click on the "Raw Data" tab, select the week you want to see, and get the developer-by-developer data for that week.

API Analytics

The "System Status" tab shows a breakdown of the responses we have returned to API requests. Possible error responses include both API errors (when our proxy was unable to reach the API server, or that server returned an error) and excess or improper developer usage (over usage or query-per-second usage; invalid API key, etc.). Mashery allows each API provider to specify the error code and message that is returned for each type of error an API call can generate. Some of our clients return a "200 OK" for all calls and, if there is an error, indicate that in the body of the response, while others elect to have a "403" or other error code that includes the reason for the error in the header. We also show mean API server response time, along with the range of response times from highest to lowest.

Easily view historical data

Click on the calendar to navigate to any previous period, where you can view by day or by 7-day period.