--- title: "Delete Current User" method: DELETE path: "/users/me" tags: ["accepts-api-key"] --- # Delete Current User `DELETE /users/me` ## Request - Base URL: `https://api.tellers.ai` (the document declares no server; this is the origin it was published from) - URL: `https://api.tellers.ai/users/me` - Auth: none declared Preview — or, with ``dry_run=false``, carry out — deleting your own account (SSE). **This previews by default.** ``dry_run`` is true unless you say otherwise, so a call that forgets the parameter reports what deleting the account *would* take and touches nothing. The ``done`` event carries ``preview`` with the counts — assets, chats, assistants, groups, the Stripe subscriptions that would be cancelled, whether the Firebase login would go too — for showing the user what they are about to lose. A caller that means it passes ``dry_run=false``. That runs the same purge as ``POST /admin/delete_account`` and streams the same events: the Stripe subscriptions, every asset the user created with its renditions and keyframes, their chats, the assistants they authored and the media those carry, the groups they solely own, the SQL row, the S3 objects and — in production only — the Firebase account. **A client that means to delete must check what it got.** Both modes answer 200 and end in a ``done`` event; only ``dry_run`` and the counters distinguish them. Reporting "your account is deleted" off the status code alone would be wrong for the default call, which deleted nothing. It streams rather than answering once because a large account takes longer to delete than a load balancer will hold an idle connection open; the progress events are what keep it open. A caller that disconnects does not stop the purge, and calling again finishes whatever was left. The email keeps its signup-history row, so registering again with the same address earns no second signup grant. ## Query parameters - `dry_run` boolean: Defaults to **true**: the call previews and deletes nothing. Pass `dry_run=false` to actually delete the account. Check the `done` event's `dry_run` field to see which of the two you got. ## Headers - `x-api-key` string, nullable - `authorization` string, nullable ## Response `200` Server-sent events. `progress` events report each stage as it happens; the final `done` event is the object below — a summary of what was deleted, or, on a dry run, a `preview` of what would be. ## Other responses - `422`: Validation Error --- [API](https://skmtc.dev/tellers/apis/tellers-api.md) - [All operations](https://skmtc.dev/tellers/apis/tellers-api/llms.txt) - [OpenAPI document](https://skmtc.dev/tellers/apis/tellers-api/revisions/fdaa0fa44a26?raw)