README — DELETE /api/v1/me
Delete the account (after a 30-day grace period)#
DELETE /api/v1/me · Operation ID: eraseMePurpose and app behavior#
This is a Handwrite app/website session operation, not an outside developer key operation. Direct the user to account controls for intentional account deletion. It disables the account immediately and schedules purge after 30 days. API keys and OAuth tokens receive 403. Never use this as a smoke test or as routine OAuth disconnect.Schedules the account for deletion: it is disabled and signed out everywhere at once, and every credential then gets 403 account_deleted. After 30 days its sign-in and all Handwrite Cloud data are erased: documents, files, shares, keys, OAuth apps, organisations it owns, usage, settings, webhooks and stored Idempotency-Key responses. Until then support@handwrites.io can restore it. Repeating the call answers the same 202. Only with an app or website session; API keys and OAuth tokens get 403. (Earlier versions erased at once and answered 204.)Authentication#
Handwrite app/website session only; developer keys and OAuth tokens are rejected.Example request#
Replace all REPLACE_* placeholders and environment values with data for your authorized test account. Use a new UUID in IDEMPOTENCY_KEY for each logical action where shown; use the actual latest revision for If-Match. Examples of writes change real data if run.curl --fail-with-body -X DELETE 'https://handwrites.io/api/v1/me' \
-H "Authorization: Bearer $HANDWRITE_SESSION_TOKEN"
Responses#
| Status | Meaning | Body format |
|---|
| 202 | Scheduled. | application/json |
| 401 | unauthorized: no token, or it's invalid, revoked or expired. | application/json |
| 403 | insufficient_scope, forbidden (you can see it but not do this), app_test_restricted, account_deleted (the account is scheduled for deletion; any request). | application/json |
| 429 | rate_limited (burst or daily cap) or quota_exceeded (no characters left). | application/json |
| 500 | internal_error. | application/json |
Use the paired API reference for complete request/response schemas. See API specification notes for rate limits, error handling, safe retries and additional policy/plan failures. For binary or empty responses, do not call a JSON parser.Modified at 2026-10-26 12:59:15