---
title: "Submit Data Request"
method: POST
path: "/v1/auth/tenants/{tenant_id}/data-requests"
tags: ["auth"]
---

# Submit Data Request

`POST /v1/auth/tenants/{tenant_id}/data-requests`

## Request

- Base URL: `https://api.elaan.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.elaan.io/v1/auth/tenants/{tenant_id}/data-requests`
- Auth: none declared

Ask us to export or delete this tenant's data.

**Owner only.** Deleting a tenant is not an administrative chore, it ends the
relationship — so this uses the same gate as rename/archive rather than the
admin+ gate that covers member management. An admin can invite people; only
an owner can ask for the tenant to be erased.

## Path parameters

- `tenant_id` string, required

## Headers

- `authorization` string, nullable

## Request body

- DataRequestBody
  - `kind` 'export' | 'deletion', required: What is being asked for. `export` requests a copy of everything in the account; `deletion` requests that the account and its data be erased. Both are actioned by a human, so neither takes effect immediately and submitting one changes nothing about the account.

## Response `202`

Successful Response

- DataRequestResponse: No id, because nothing is stored to have one. The console shows the acknowledgement and the address to chase, which is all a caller can act on.
  - `kind` 'export' | 'deletion', required
  - `contact_email` string, required: Where to follow up, and where to write if this ever fails.

## Other responses

- `403`: Not a member, or not the owner, of that tenant
- `422`: Validation Error
- `503`: Could not be filed; the caller should email support instead

---

[API](https://skmtc.dev/elaan/apis/elaan-api.md) · [All operations](https://skmtc.dev/elaan/apis/elaan-api/llms.txt) · [OpenAPI document](https://skmtc.dev/elaan/apis/elaan-api/revisions/c96a7e6399aa?raw)