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

Evaluating API Monitor Checks Using the API Science API

Your API monitoring team can be alerted when an API that’s critical for your product goes down using API Science’s alerts capability, which provides the ability to notify your team about problems using email, a URL, Slack, PagerDuty, and HipChat. These methods can be extended using tools like IFTTT (IF This Then That) such that […]

Continue reading

How to Use the Results From One API Call in Another API Call

In many cases, the availability of your product depends on a sequence of API calls (to both external and internal APIs). Information retrieved from one API may be a critical input for your subsequent call to a different API. If the first call fails, the second can’t return a valid result. So, a question is: […]

Continue reading

Introduction to API Monitor Local Variables

Recent posts have talked about the capability the API Science API monitoring platform provides for creating and working with global variables that are maintained across multiple monitors. In this post, we’ll look into the platform’s capability for creating local variables that are specific to an individual API monitor. The fact is, APIs change over time. […]

Continue reading

Introduction to API Science’s Global Variables

The API Science platform provides capability for saving, retrieving, and deleting global variables. The Parameters section on the API Science Help page provides this description: You can set any number of query string, POST, and PUT parameters using the Params input fields. Each time you add a new variable a new pair of Key/Value input […]

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

Importing Swagger, RAML, Postman, and HAR API Representations to Create API Monitors

The importance of APIs (Application Programming Interfaces) continues to grow, as established and start-up vendors recognize their utility both as the foundation of their own products and as a means by which they can sell their services to other companies as components of new products. Because of this, publishing representations of APIs has gained currency: […]

Continue reading