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 readingHow 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 readingIntroduction 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 readingDeleting API Science Global Variables
In previous blog posts, I described how API Science monitors could be used to create global variables and retrieve and verify them. In this post, we’ll create a new monitor that deletes an API Science global variable, then study what effect this has on the earlier monitors. My “Set Dog and Meal” monitor sets the […]
Continue readingRetrieving and Verifying API Science Global Variables
In my last blog post I showed how to set API Science variables using my “Set Dog and Meal” API monitor. In this post, I show how to create a new monitor that reads and verifies the status of those parameters. The “Set Dog and Meal” monitor runs every 60 minutes, setting the following parameter/value […]
Continue readingIntroduction 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 readingUsing 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 readingUsing 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 readingImporting 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 readingImporting HTTP Archive (HAR) Files to Create API Monitors
The HTTP Archive (HAR) format is a JSON file format that records the interactions of a web browser and web pages. HAR files can be used, for example, as a means for customers to record interactions with a web service, to record recurring problems and send them to a troubleshooting team. The HAR format can […]
Continue reading