Detecting Failed API Monitor Checks Using the API Science API

In my last post, I illustrated how we can use the API Science Checks API endpoint to gather the results of recent checks for an API monitor. In that post, the example check was a successful call for my “br Ireland” monitor, which queries the World Bank Countries API for information about Brazil from a server located in Ireland. My “br_Ireland” monitor has a validation setting that requires an HTTP Response code of “200” in order for the API check to be considered successful…

Continue reading

Using Slack, Zapier, HipChat, PagerDuty, IFTTT, and Todoist to Broadcast API Monitor Alerts

Today, many companies have employees that work from diverse locations around the globe. If your company’s product relies on APIs (internal and/or external), your team needs to know immediately when a critical API goes down or starts delivering invalid information. But how can you quickly communicate problems of this type to your global team? The […]

Continue reading

Using the Weekly API Science Report to Improve Customer Experience

Your API Science account automatically provides you with the “Weekly API Science Report” which is delivered by email to the email address associated with your account. Here’s an sample email for an account that runs two API Science monitors: The report proceeds from a performance overview for all of your monitors down to the details […]

Continue reading