---
title: "Delete the current user’s health data, scoped by category"
method: DELETE
path: "/api/health/data/me"
tags: ["Health"]
---

# Delete the current user’s health data, scoped by category

`DELETE /api/health/data/me`

## Request

- Base URL: `https://api.rewritelifestyle.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.rewritelifestyle.ai/api/health/data/me`
- Auth: HTTP bearer

Delegates to HealthDataDeletionService.deleteHealthData. Two independently-selectable groups: includeDeviceSynced covers health_samples, health_device_connections, health_sync_anchors, health_readiness_snapshots, user_source_preferences, health_baselines (the actual "synced health data" PP §2.3 refers to). Clearing health_device_connections returns health_last_synced_at in GET /users/profile to null, which mobile reads as "not yet synced". includeManualLogs covers bowel_movement_logs, digestive_symptom_logs, diary_entries, user_health_goals — never synced from a device. At least one must be true. If HealthKit/Health Connect permission is still granted at the OS level and includeDeviceSynced was selected, the next sync will re-pull that data — the mobile client is responsible for warning the user before they confirm.

## Query parameters

- `includeDeviceSynced` boolean
- `includeManualLogs` boolean

## Response `200`

- unknown

---

[API](https://skmtc.dev/rewritelifestyle/apis/rewrite-lifestyle-api.md) - [All operations](https://skmtc.dev/rewritelifestyle/apis/rewrite-lifestyle-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rewritelifestyle/apis/rewrite-lifestyle-api/revisions/28695827f27a?raw)
