If you have a set of integration tests for internal API testing using Insomnia, you can upload your Insomnia test collections to Dotcom-Monitor for API testing from 40+ global locations.

Dotcom-Monitor supports a variety of options, such as alerting on errors that occur while monitoring, specifying monitoring locations, as well as configuring your monitoring scheduler, and filters, and setting up reporting on monitoring results. With monitoring checks scheduled from every minute to every 3 hours, your team will gain a high level of flexibility in the monitoring setup.

Before You Start

Insomnia Request Collections and Design Documents

Before you begin the device configuration, note that Dotcom-Monitor supports import of both Insomnia Request Collections and Design Documents. However, there is a difference in the way we process imported Design Documents and Request Collections.

To upload an Insomnia Collection or Document to Dotcom-Monitor, make sure to export Insomnia data to a JSON file.

When you upload an Insomnia Design Document to Dotcom-Monitor and run a monitoring test, we execute only the first suite from the test suite list. All other test suites in the Document are ignored.

When you upload an Insomnia Request Collection to Dotcom-Monitor, we execute the Collection and verify the response for any network and response code errors like 404, 401, 500, etc.

Setting Up an Insomnia Collection Monitoring Device 

For a quick overview of how to create a monitoring device, please read the Creating a Monitoring Device Knowledge Base article. 

If you are going to set up monitoring for a group of Insomnia Collections, we recommend you set one collection per device. For details, see the Limitations of Multi-Target article of our wiki.

An HTTP request in the collection represents a separate monitoring task and will be charged according to your package. See also the approximate Pricing Matrix for WebView Monitoring Knowledge Base article. Please contact your Dotcom-Monitor Account Executive with any questions.

If you want Dotcom-Monitor to generate alerts and send alert notifications when any condition set by tests is not met or any network errors were detected while the Collection execution, make sure to configure device alerting settings.

Importing Insomnia Collection & Design Document

Click Import and select a JSON file with an Insomnia Collection or Document to upload. The Insomnia script will be displayed in the Collection Requests section.

Collection Timeout

The Collection Timeout, measured in seconds, determines the duration the device should wait for the Insomnia requests and tests to complete before terminating the task and raising an error.

Prepare Script

See the Using Prepare Script article.

Secure Data in Requests

Please see how to protect sensitive information sent along with Insomnia requests in the Secure Sensitive Data in Insomnia Requests with Dotcom-Monitor article.

Ignore Network Errors

Network errors may include DNS resolution errors, TCP connection timeouts/errors, or instances where the server terminates or resets the connection with a 4xx or 5xx response status code (and no data)By default, Dotcom-Monitor generates errors and sends alert notifications on Insomnia network  errors that occurred during execution. If network errors are not your concern or it’s an expected system behavior, you can configure your Insomnia Collection monitoring device to filter out this type of error.

If the Ignore Network Errors option is set to Yes, Dotcom-Monitor will not raise an error on failed requests from the Insomnia Collection and change the device status to Alerting. However, you will see HTTP errors in monitoring session reports. In this scenario, the Collection test suite is going to be used to verify the response validity.

Generally, it is recommended to enable the Ignore Network Errors option if you want to receive monitoring results that are fully based on the tests imported with your Insomnia Collection.

Let’s say we have an Insomnia Document checking for 401 Error Code in response to incorrect login information input.

If the Ignore Network Errors option is set to Yes in Dotcom-Monitor and the 401 Unauthorized response status code is received in the response, the system will ignore the error and interpret the monitoring check as passed successfully.

If the Ignore Network Errors option is set to No for the same Insomnia Collection monitoring device, the system will raise an error on all network errors received while running the collection, including the 401 Unauthorized response. The device status will be set to Alerting.

Ignore Error Codes

Please see Ignore Web Request Errors for Web Services and Internet Infrastructure Monitoring

Monitoring OAuth 2.0-based APIs

In general, a Service API call using OAuth 2.0 includes two steps executed sequentially: first, obtaining an API access token using the Bearer Token authentication mechanism. Second, using the awarded bearer token to request custom data from the service.

However, due to an unresolved Insomnia issue with retrieving OAuth access tokens in new environments, this token-based authentication fails upon import to Dotcom-Monitor. In other words, the second request loses its reference to the bearer token obtained with the first request.

As a workaround, an API call that requires a bearer token can be handled in a single request within Insomnia.

To import and monitor your Insomnia collection with Dotcom-Monitor, avoid requesting an authentication token in the first API call of your collection. Instead, set up authentication directly in your data request using the OAuth 2 authentication type.


This way, the Insomnia collection will be imported and executed correctly in Dotcom-Monitor.