Runscope API Monitoring    Learn More →

Posts filtered by tag: on-prem

How to Test Private & Local APIs with the Runscope On-Premises Agent

By Ashley Waxman on .

Different teams need to access and test APIs in different environments and stages of the development lifecycle. Being able to reuse these tests across every stage is critical for effective collaboration and efficiency, and running tests against APIs during development or APIs that live behind a firewall should be just as easy as testing APIs in the public cloud. The Runscope On-Premises Agent downloads easily to your local machine and executes requests in the location that makes the most sense for your infrastructure, all while keeping your test management in the cloud.

In the video below, Neil Mansilla, VP of Developer Relations at Runscope, provides an in-depth demo of the On-Prem Agent and how you can leverage API testing in your organization, no matter where your APIs live. This video covers:

  • How to install the Runscope On-Premises Agent and instantly begin testing APIs behind the firewall
  • Different use cases for testing APIs in a local environment, including testing private APIs and testing APIs in the beginning of the development process
  • Ways to incorporate API testing into your continuous integration (CI) processes

The On-Prem Agent is available during the Runscope free trial and on any paid plan. Give it a try today to begin testing private and local APIs in minutes.

Categories: testing, howto, product, webinar

Introducing the On-Premises Runscope Gateway Agent for Capturing and Debugging Private and Internal API Traffic

By Neil Mansilla on .

Back in September, we introduced Runscope Radar Agent, an on-premises testing agent that you download and install on a host within your network. The remote agent appears along side Runscope's global cloud-based testing locations, allowing tests to be executed against APIs behind your firewall, or even those running on the same localhost. Radar Agent has been a huge success, and we're excited to extend the hybrid on-premises deployment model to another key area of Runscope.

Today, we’re announcing the release of the Runscope Gateway Agent. The same gateway software that powers Runscope's cloud infrastructure for making and logging API calls can now be installed on your local network. Deploying the Runscope Gateway Agent within your infrastructure will help to:

  • Capture API request and response data made to private or internal APIs that reside behind a firewall
  • Troubleshoot and debug those API calls using the Runscope Traffic Inspector
  • Increase network performance by keeping API traffic within your infrastructure
  • Create Runscope URLs (on your domain name) for services running on localhost
  • Access APIs that require a fixed client IP address (IP whitelisting)

How it Works

The agent works by creating a locally-hosted instance of the Runscope Gateway with your own hostname and TLS certificate. Instead of using our cloud-based Runscope Gateways (hosted on *, requests will use the configured hostname for your agent instead.


Inspecting traffic with the Runscope Gateway Agent uses a hybrid on-premises approach. The agent runs on a host within your infrastructure, but traffic data is stored in the Runscope cloud to make searching and collaboration easier. Traffic collected with the agent is available in the Traffic Inspector along with all other traffic made in the same bucket.

All communication from the agent to the Runscope cloud is made securely over outbound requests to the Runscope API via HTTPS on port 443. See Firewall Considerations for more information.

How to Get Started

Use of the Runscope Gateway Agent requires a Trial, Starter, Team, Business or Enterprise subscription. The agent is available for Mac OS X, Windows (64/32-bit) and Linux (64/32-bit). For complete download and implementation instructions, see the Gateway Agent documentation.

Categories: announcements, product, testing, debugging

Runscope 25 Kearny St San Francisco, CA, 94108 United States

Everything is going to be 200 OK®