Migrating from StatusCake to Lemwatch

StatusCake exposes both halves of a migration through its public API: GET /v1/uptime lists every uptime test on the account, and GET /v1/uptime/{test_id}/history returns that test's recorded history.

Exporting your monitors

Call GET /v1/uptime (ListUptimeTests) against the StatusCake API with a bearer token. The same call is what StatusCake's own Go client library wraps, so the field names you get back match their documented schema exactly.

Exporting your history

GET /v1/uptime/{test_id}/history (ListUptimeTestHistory) returns per-test history. There is no documented CSV endpoint, so you loop the test IDs from the list call and store the JSON yourself.

Things that catch people out

• History is per test, not per account — you make one history call per uptime test, which matters if you are running dozens and hit rate limits mid-export.
• StatusCake does not publish a data-retention or post-cancellation policy page we could verify on 4 August 2026, so assume history disappears when the account closes and export first.
• Test IDs are StatusCake-internal, so keep the exported JSON as your mapping record if you need to reconcile old incidents against the new tool later.

Export mechanics verified on 2026-08-04 against StatusCake's own documentation.