Monitoring Your API’s Uptime Using the API Science API

My previous post talked about what you can do when a massive cyber attack brings down APIs (your own, or external APIs) that are critical for your product.

The API Science API includes a Monitor Reports component that lets your product’s operational software integrate your API monitoring into the ongoing creation of your product. The product you present to your customers changes depending on the status of the APIs that provide the data your product provides to your customers. You need to monitor all APIs that are critical for your product if you are to know when customers might be seeing outages.

One way to do this is to send alerts to your team whenever a critical API goes down. If the outage is not that significant, your team can address the issue and ensure that your customers know you are coping with the outage.

But, in a situation where there is a massive geographical outage, sending an endless succession of alerts to your team may be inadequate…

Continue reading

Modifying Groups of API Monitors Using Tags

In recent posts, I’ve described how you can use API Science’s API to evaluate API monitor checks, detect failed checks, and use tags to group API monitors. If you’ve integrated the monitoring of your product’s performance and availability using the API Science API, it’s also possible to take the next step of modifying your monitors […]

Continue reading

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