Delete your own account

Danger zone. Unlike a one-account-per-company product, a Booking org can have several members, so deleting YOUR account does not always take the workspace with it:

• Last member standing: nobody would be left who could ever sign in and manage or delete the org, so the whole workspace is deleted too.
• Teammates remain: only this user's membership and personal data go; the workspace is shared, not owned.
• Sole admin with staff remaining: refused with 400. Promote a teammate first. This mirrors the "cannot remove the last admin" rule on DELETE /api/members/{id}, so an admin cannot self-delete into an org nobody can administer.

When the workspace does go, its live Stripe subscriptions are cancelled immediately, before the database cascade, and that cancellation has to succeed for the deletion to proceed (see the 502). The Stripe customer and its invoices are deliberately NOT deleted: Australian tax law requires seven years of sales records, so erasure covers the account and retention covers the invoices.

This route is exempted from the onboarding redirect in middleware so a mid-onboarding account can still delete itself.

Response BodyCopy Anchor Link

curl -X DELETE "https://example.com/api/account" \  -H "Content-Type: application/json" \  -d '{    "confirm": "DELETE"  }'

{  "ok": true}