StatusPage.me Help Center

Popular topics: creating a status page, connecting monitors, automatic incidents, custom domains, integrations and billing.

StatusPage.me Jul 24, 2026 Account & Billing

Resetting Your Workspace

Workspace reset is for starting again without closing your StatusPage.me account. It is useful for testing a new setup or changing how you use the service.

It is not account closure. Your profile, sign-in settings, API keys, plan, purchases, subscriptions, and billing records remain unchanged.

What Is Reset

Reset removes your personal operational workspace, including status pages, domains, components, monitors and their history, incidents, maintenance windows, heartbeats, notification configuration, metrics, runbooks, on-call configuration, and related integrations and analytics data.

Shared teams and memberships are not deleted. A reset does remove your status pages from shared-team access because those pages no longer exist; the team itself remains intact.

Reset and Restore

  1. Open Account Settings → Reset workspace, or go to /user/account/reset.
  2. Select Review reset scope to see the records that will be removed.
  3. Type RESET MY ACCOUNT and verify your identity with your password, authenticator code, or backup code.
  4. Confirm the reset.

Before clearing the workspace, StatusPage.me creates a private snapshot. Snapshots remain available for 30 days on the same screen.

Restoring a snapshot replaces your current workspace. Anything created after the reset is removed as part of that restore, so export it first if you need to keep it. Your current plan limits still apply after restore.

API Reset

Automation can reset a workspace with POST /user/api/v1/account/reset.

This endpoint is deliberately stricter than normal write endpoints:

  • use a full-access API key, or a restricted key explicitly created with the account:reset scope;
  • send an Idempotency-Key header; and
  • treat the response snapshot ID as the restore point for the next 30 days.

Browser sessions cannot call this endpoint; use the dashboard confirmation flow instead.

Was this article helpful?