Skip to main content

UptimeRobot - Setup Guide

Overview

The UptimeRobot source syncs monitor metadata, status, timing information, and uptime ratios into Daspire.

Prerequisites

  • An UptimeRobot account.
  • A read-only or account API key from Integrations & API > API in UptimeRobot.

Daspire only calls the read-only getMonitors endpoint. A read-only key is preferred when the source does not need account-wide write access.

Configuration

FieldRequiredNotes
API KeyYesStored as Daspire secret material and never returned in records, state, or logs.
Acquisition MethodYesChoose Periodic or Manual. Existing configurations without this field use a one-day periodic window.
DaysPeriodic onlyNumber of days included in the uptime-ratio window. Must be at least 1.
Start DateManual onlyFirst UTC calendar day in the fixed range, formatted YYYY-MM-DD.
End DateManual onlyLast UTC calendar day in the fixed range, formatted YYYY-MM-DD. The day is included.
Page SizeNoDefaults to 50, which is the provider maximum.

Supported Streams

StreamSync ModePrimary KeyDescription
getmonitorsFull refreshidMonitor name, URL, type, status, interval, timeout, creation time, and uptime ratios for the selected acquisition window.

Large accounts are read in pages. Daspire saves the current acquisition window and offset so a bounded read can continue without skipping monitors.

Rate Limits and Troubleshooting

UptimeRobot applies plan-based API limits and returns HTTP 429 when the quota is exhausted. Daspire honors provider retry hints and retries transient rate-limit, timeout, and server failures with bounded backoff.

ErrorAction
Authentication failedReplace or re-authorize the UptimeRobot API key.
Rate limit exceededWait for the provider reset window or reduce the sync frequency.
Invalid manual rangeEnsure both dates use YYYY-MM-DD and End Date is not before Start Date.
Empty resultsConfirm the API key can read monitors and the account contains monitors.

Additional Resources