Runscope API Monitoring    Learn More →

Runscope and the BlazeMeter Continuous Testing Platform

By Heitor Tashiro Sergent on .

Today, we're really excited to talk about the release of the BlazeMeter Continuous Testing platform, and the integration of Runscope's API Monitoring capabilities as part of this new offering.

We have two great blog posts talking more about this new platform, why we're excited about it, and how we believe it'll help bring value and transform teams looking to shift-left and adopt modern testing practices:

For Runscope users, in addition to the API Monitoring features there's also some new exciting capabilities […]

Read More →

Categories: announcements, product, webinar

Runscope is joining BlazeMeter

By Heitor Tashiro Sergent on .

For the past couple years, Runscope has gone through a lot of changes. We were acquired by CA Technologies back in September 2017, and CA Technologies was acquired by Broadcom in November 2018. Our team has grown, and we have worked hard on improving the product and adding features such as Secrets Management, Role-based Access Control, and more. We have also done a lot of work behind the scenes to improve our infrastructure, and have grown from running 300 million API calls a month to running 1.2 billion API calls a month.

Coming soon, there are going to be even bigger changes happening to Runscope. We are going to be joining BlazeMeter, a market-leading product for Load Testing and Performance Testing.

BlazeMeter is a company that was also acquired by CA Technologies, back in 2016, and is now a part of Broadcom. They have an amazing team and product, and we're really excited to be joining our API Monitoring capabilities and expertise with their Performance and Load Testing knowledge […]

Read More →

Categories: announcements, product

New Runscope API Monitoring Locations with Google's Cloud Platform

New Runscope API Monitoring Locations with Google's Cloud Platform

By Heitor Tashiro Sergent on .

One of the biggest advantages of API monitoring is the ability to test and monitor your API from locations around the globe. This can help teams get an accurate measurement of the performance API users are seeing when working with their APIs, and help monitor and improve the user API experience.

That's why we offer multiple locations for our users to run their API tests from, and why we are excited to announce that we're expanding from 16 to 19 locations! The three new locations we've just added are:

  • US Iowa

  • US South Carolina

  • Finland

Another big part of this announcement is that […]

Read More →

Categories: announcements, monitoring, product

How to Integrate Runscope with ServiceNow

By Heitor Tashiro Sergent on .

ServiceNow is a flexible online platform that helps customers transform their digital workflows. One of the ways it can be used is to help IT departments with their incident management process.

By using Runscope's Advanced Webhooks, you can integrate API monitoring notifications to automatically trigger a ServiceNow workflow, and create a new incident based on Runscope's webhooks information.

We have added a step-by-step tutorial to our docs showing […]

Read More →

Categories: howto, integrations, tutorial

How to Merge OpenAPI Definition Files

By Heitor Tashiro Sergent on .


I recently saw a Twitter thread that started with a simple question: how to combine multiple OpenAPI 3 definition files back together? One of the answers on that Twitter thread came from Mike Ralphson, and he pointed out that speccy, an open-source project, could help with that.

Now, you might ask yourself, why would someone want to merge an OpenAPI definition file back together? Isn't the point of separating it into multiple files to have better organization? Well, merging a definition file back together into a single one can be useful if you have tooling that doesn't support definition files with references and requires a single one to be uploaded, whether that is for documentation tooling, a UI definition editor, or maybe for API Gateway support.


speccy is an open-source project written in Node.js, that allows the user to lint, merge, and visualize an OpenAPI definition in a human-readable format.

For our purposes, we're just going to focus on the merging aspect of it.

How to Merge OpenAPI 3 Files

To use speccy, first we need to have Node.js installed in our machine. You can either download it from the Node.js website, or open the terminal and run:

curl "${VERSION:-$(wget -qO- | sed -nE 's|.*>node-(.*)\.pkg</a>.*|\1|p')}.pkg" > "$HOME/Downloads/node-latest.pkg" && sudo installer -store -pkg "$HOME/Downloads/node-latest.pkg" -target "/"

Then, we can install speccy by opening the terminal and running:

npm install -g speccy@0.8.7

And finally, still in the terminal, go to the directory where your OpenAPI definition files are and run:

speccy resolve spec.yaml -o spec-output.yaml

`resolve` is the command to merge definition files back into one. It's followed by the path to the main definition file that includes references to other files you wish to merge. Next, we add the option flag -o to output the resulting definition to a new file named spec-output.yaml.

If you want to test this on a definition file that's broken up into separate files but you don't have one at the moment, you can use this example I set up using the Pet Store example:

And if you're curious about the way I split up this OpenAPI definition, I used this great blog post by Jack Skinner as a reference: Maintaining large design-first API specs.

And you're all set.

Note: you might have noticed that we are using a specific version of speccy, 0.8.7, in the install command. At the time of writing, there was a known issue with the latest version where the output flag for the resolve command was not working. I would recommend using the latest version if that bug has been fixed. And always be kind to open-source maintainers. :)

Categories: openapi, tutorial

How to Debug Common API Errors

By Heitor Tashiro Sergent on .


Debugging and troubleshooting APIs is something that any developer that works with APIs has to go through at some point. In an ideal world, APIs would always return a 200 OK with just the right data that we need, or in case of a failure, it would return us the perfect status code and error message allowing us to easily understand what went wrong.

In reality, APIs don't always work like that. API developers might have constraints that do not allow them to implement the most informative status code or error message, API errors can be triggered by real-world conditions that are hard to account or test for, and sometimes ourselves, as API users, can make requests with typos or mistakes that APIs just don't know how to handle.

In this post, we're going to focus on API users and what they can do to debug common API errors they might encounter when testing and working with APIs, whether these APIs are public or private […]

Read More →

Categories: testing, debugging, apis

Everything is going to be 200 OK®