Switching from UptimeRobot

The easiest way: a read-only API key

1. In UptimeRobot, open Integrations & API → API and create a Read-only API key for the whole account.
2. Paste the key into digiWatcher and press Preview import. The key isn’t stored; it’s used only to load the list through the official API v3.
3. Review the warnings and select the websites you want. digiWatcher also checks the plan limit and duplicates when you save.
4. After the import, open each monitor’s details, check its settings and alert contacts, and start the checks.

One load handles up to 1,000 monitors. The preview is valid for 15 minutes. If UptimeRobot limits your requests, wait at least a minute.

Import from a file

If you use UptimeRobot’s official CLI with an API key already set up, save the list with this command:

uptimerobot monitors list --limit 200 --json > monitory.json

The CLI doesn’t load further pages by itself. If the JSON contains nextCursor, download the further pages with --cursor and merge all items entries into one JSON array. digiWatcher rejects a file that points to a missing next page, so some websites don’t get lost without warning. Loading directly through the API handles pagination for you.

We accept a JSON array of monitors, an object with items from the CLI, or a full API v3 response with data. The file limit is 2 MB. CSV and the older API v2 format aren’t supported. The file can contain sensitive details about the monitored websites; after the transfer, store it securely or delete it.

What we transfer

Name, HTTP(S) address or host, TCP port, interval, timeout, method (GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, or QUERY), expected HTTP statuses, redirects, and up to ten tags. We support HTTP, Ping, TCP Port, and keyword monitors with case sensitivity explicitly turned off. We shorten long names to 80 characters; we round the interval up to a supported value and the plan minimum. The preview shows the changes.

We also transfer HTTP Basic authentication, custom headers including Authorization, a JSON or form request body, and TLS verification settings. We keep passwords and multi-line bodies exactly as they are. The preview doesn’t show sensitive details; until you save, they’re kept in an encrypted preview that’s valid for 15 minutes.

Each source monitor has its own identity: two checks of the same address are transferred separately, and importing the same monitor again doesn’t create another copy. For older imports without a source ID, we compare the name and settings, not the address alone.

The import doesn’t support Digest authentication, DNS, or Heartbeat yet. For Bearer authentication, the export must contain the full Authorization header. Incomplete or unsupported settings stay in the preview with a specific reason; such an import isn’t complete. We don’t send headers with secrets on a redirect to another domain, and we reject redirects with a body to another domain.

Before you start

Uptime history, alert contacts, scheduled maintenance, status pages, monitoring locations, and alert rules aren’t transferred. Check advanced configuration manually. digiWatcher uses two failed checks to confirm an outage. The new history starts only once you start the checks.

Once started, a monitor with no assigned alert contacts uses all active alert contacts in the account. Set up the channels you need beforehand and verify that they deliver.

Keep the external monitor that watches digiWatcher itself with an independent service. For client websites, turn off the original checks only after you’ve verified that digiWatcher measures and delivers alerts correctly.