Runscope API Monitoring    Learn More →

Keep Your Account Safe: Two-Factor Authentication with Google Authenticator

Keep Your Account Safe: Two-Factor Authentication with Google Authenticator

By Heitor Tashiro Sergent on .

Security is a top priority for us at Runscope. It's important for us to make sure that your data is always safe, and to also empower you with any tools that we can to allow you to protect your companies' data.

We added support for two-factor authentication back in July of 2015. Users could enable 2FA in their accounts via SMS, or by using the Authy app. But, we understand that sometimes users can have different apps that handle 2FA, such as Google Authenticator and other TOTP compliant apps that require a QR code.

So, last week we've added support for Google Authenticator and other apps as two-factor authentication options for Runscope users! [...]

Read More →

Categories: announcements, howto, security, product

Taking a Timeout from Poor Performance

Taking a Timeout from Poor Performance

By Phil Sturgeon on .

Our Featured Guest Series is back! In this post, Phil Sturgeon warns about ripple effects that can take out entire applications, through making HTTP calls to unstable systems. Learn about using timeouts, retries, and circuit breakers to avoid this happening to you!

If you're interested in contributing to the Runscope blog, go to for more information.

In a system-oriented architecture, it is crucial to communicate with other systems. In an ideal world each service knows enough information to satisfy its clients, but often there are unfortunate requirements for data to be fetched on the fly. Broker patterns, proxies, etc., or even just a remote procedure being triggered synchronously, like confirming an email has been sent successfully. 

All of these things take time. Frontend applications (desktop, web, iOS, Android, etc.) talk to services, and services talk to other services. This chain of calls can stack up, as service A calls service B, unaware that system is calling service C and D… So long as A, B, C and D are functioning normally, the frontend application can hope to get a response from service A within a “reasonable time”, but if B, C or D are having a bad time, it can cause a domino effect that takes out a large chunk of your architecture, and the ripple effects result in a slow experience for the end users.

Slow applications can cost you a lot of money. A Kissmetrics survey suggests that every 1s slower a page loads, 7% fewer conversions will occur. This article explains how you can make your applications remain performant when upstream dependencies are not, using timeouts and retries. [...]

Read More →

Categories: microservices, featured guest series, apis

Using Snippets and Script Libraries to Monitor AWS APIs

By Heitor Tashiro Sergent on .

One of the most common programming principles that we learn as developers is to generally avoid repeating yourself, or DRY. Copy-pasting the same lines of code is replaced with creating abstractions in the form of methods or functions that can be used and re-used in multiple places across a project, which in turn will make your code easier to understand and modify.

That same idea of avoiding repeating code can be applied to Runscope API monitors by using our Snippets and Script Libraries feature.

A few months ago we added the aws4.js library to our script-libraries repository and...

Read More →

Categories: howto, tutorial, monitoring

Design Thinking and Wicked Problems for APIs

Design Thinking and Wicked Problems for APIs

By Ash Hathaway on .

This is a post from our Featured Guest Series! Ash Hathaway shares her experience as a former developer turned product manager for APIs, and how design thinking has helped her team solves difficult technical problems.

If you're interested in sharing your knowledge on our blog, check out our Featured Guest Series page for more details.

You may have heard of design thinking or even participated in a workshop using lots of sticky notes. Done correctly design thinking is an insanely fun way to generate tons of ideas with your team, create buy-in, and leapfrog ideas all centered around your user. So, what is it? And why does it matter for APIs?

Design thinking is a way to solve complex and multidimensional problems smarter together. The roots of design thinking are in human-computer interaction design which evolved into a framework to innovation. More specifically it touts methods to find overlap in business strategy, technological feasibility, and user needs. It is a “process for creative problem solving,” according to IDEO, an international design consulting firm and large proponent (some might say the OG) of design thinking in mainstream tech today. 

Why design thinking makes sense for APIs

So what does this have to do with APIs? APIs are like super technical and deal with code. That has zero to do with...

Read More →

Categories: featured guest series, community, apis

How to Sync your OpenAPI Schema in Stoplight with GitHub and Runscope

How to Sync your OpenAPI Schema in Stoplight with GitHub and Runscope

By Glen Semino on .

This is a post from our Featured Guest Series! Glen Semino shows how to combine Stoplight and GitHub APIs with Runscope to keep your OpenAPI Schema always versioned and up to date.

If you're interested in sharing your knowledge on our blog, check out our Featured Guest Series page for more details.

About a month ago after I and part of the SYNQ team attended the APIDays SF conference, we reflected on what we had learned at the conference. One of the things we realized was that our API spec documentation needed quite a bit of improvement. And among the tools discussed in the conference was Stoplight, which helps one design, document, mock, and test APIs. 

We decided to give Stoplight a try to rewrite and edit our API spec. Once we started, I noticed that I was often manually syncing our Open API spec (OAS) file that Stoplight generates with our GitHub repo. I wanted a way to automate this process so that regardless of what gets edited/changed in Stoplight, Stoplight and GitHub are always in sync. 

This is where Runscope came to save the day. Using the export function Stoplight offers in addition to GitHub’s API, I was able to automate syncing our Stoplight OAS spec file with our GitHub repo every minute using Runscope. In this tutorial, we're going to walk through this workflow step-by-step so that you can do it too!

The Setup

These are the things you will need to do to create the necessary API requests in Runscope to automate the syncing process...

Read More →

Categories: code samples, howto, monitoring, openapi

Runscope is Joining CA Technologies!

By John Sheehan on .

Today I’m excited to announce that Runscope has been acquired by CA Technologies. We’re bringing our market-leading API monitoring tools to CA to further our shared mission of equipping developers with the tools they need to deliver and operate mission-critical APIs powering the modern enterprise.

Five years ago, Frank and I saw an opportunity to build a new class of developer tools for modern, API-driven applications. We were joined by a fantastic group of investors and team members passionate about building great products driven by an obsession with customer success.

Today, Runscope is used by over 1,200 customers to run 17,000,000 API uptime and data validation checks every day. Companies of all sizes...

Read More →

Categories: announcements

Everything is going to be 200 OK®