Export your data
Download your personal data or a full archive of your workspace data (GDPR data portability).
You can request an export at any time, delivered as a ZIP archive containing JSON files for each resource type, downloaded directly in the app. There are two kinds:
- Your personal data (GDPR Article 15): available to every workspace member, for their own data only.
- The full workspace export: owner/admin only, tenant-wide.
What is included
Personal export (any member): your profile (name, email, created date), notification and quiet-hours preferences, your on-call assignments (schedule memberships, overrides, unavailability), escalation-policy targetings that page you directly, support tickets you opened, and audit-log entries about your own actions.
Workspace export (owner/admin only):
| Resource | Format |
|---|---|
| Monitors | JSON array of all monitors with current configuration |
| Heartbeats | JSON array with configuration and last-ping timestamps |
| Incidents and alerts | JSON array with the name, summary, description, severity, status, start and resolve times, and — for an alert that arrived from one of your integrations — its source, fingerprint, labels and annotations |
| Status pages | JSON array with name, slug, and published state |
| Notification channels | JSON array (credentials excluded) |
| On-call schedules | Schedules, rotation layers and members, historical member ordering, temporary schedules, signup slots, overrides, unavailability, shift releases, and swap requests |
| Escalation configuration | Policies, ordered steps and targets, tenant default, monitor assignments, alert routing rules, and business-service policy/monitor bindings |
| Account | JSON with the requester's own profile details |
| Audit log | JSON array of the requester's own audit events |
Every archive contains manifest.json and README.txt, which identify whether it is a personal or workspace export and describe its content boundary. Workspace on-call files use stable paths under oncall/; rows are emitted in a stable order for downstream processing.
Credentials (API keys, webhook secrets, iCalendar bearer tokens, MFA/TOTP seeds) are never included in either export. Business-service policy, team, and monitor bindings are included, but free-form runbook URLs and runbook steps are omitted because customers may have embedded credentials in those fields. Raw per-probe check history is also not part of this ZIP: it is held in a separate metrics database and follows that database's own retention policy. The workspace archive contains the relational monitor configuration and incident/alert records listed above, not the raw result of every probe execution.
Steps
- Go to Settings > Account > Danger zone.
- Click Request export under "Export your data" (every member) or "Export workspace data" (owner/admin only).
- Confirm the action. A background job is queued, and the page updates automatically as it moves from queued to processing to ready.
- Once ready, click Download ZIP. A lifecycle email can tell you that the job is ready, but it never contains the archive or a bearer download link; the archive is retrieved only after authentication in the app.
Export links expire after 48 hours. Request a new export if the link has expired.
Rate limit
You can request at most one export per 24 hours per user, per kind (a personal export request never blocks, or is blocked by, a workspace export request). If you need more frequent exports, use the API directly: POST /api/v1/account/export/personal (personal) or POST /api/v1/account/export (workspace, owner/admin only) to start a job, then GET /api/v1/account/export/{job_id}?download=1 to download the archive once its status is completed.
Export an SLA report as CSV
The full-workspace ZIP above is the account-wide GDPR export. Separately, the Analytics area can export a per-monitor SLA report as CSV. This is the uptime/SLA summary you can hand to stakeholders.
From the app, open Analytics, select your date range, and click Export CSV. Or fetch it directly from the API:
curl -X GET "https://api.example.com/api/v1/analytics/sla-report?format=csv&from=2026-06-01&to=2026-06-30" \
-H "Authorization: Bearer howlops_abc123..."
Query parameters:
format:json(default) orcsv.from/to: the reporting window, as ISO 8601 (YYYY-MM-DDor full RFC 3339). Required unless you useperiod.period=last_month: shorthand for the first to last day of the previous month (used instead offrom/to).monitor_ids: optional comma-separated list to limit the report to specific monitors. Omit to include all.
The CSV contains one row per monitor with these columns:
| Column | Meaning |
|---|---|
| Monitor Name | The monitor's display name |
| Monitor URL | The monitored URL |
| Uptime % | Uptime percentage over the window |
| Total Checks | Number of checks run |
| Down Checks | Number of failed checks |
| Downtime (hours) | Total downtime |
| Incidents | Incident count |
| MTTR (minutes) | Mean time to recovery |
A summary block (average uptime, total incidents, total downtime, average MTTR) is appended at the end of the file.
Delete account / workspace
If you want to delete your account or workspace entirely rather than just export, go to Settings > Account > Delete workspace. Deletion is scheduled with a 30-day grace period: the workspace is soft-deleted immediately and permanently removed after 30 days. During the grace window the deletion can still be reversed; after it elapses, removal is irreversible. An export is recommended before deletion.
See also
Was this page helpful?