Start (or return the in-flight) DSGVO Art. 15 export job.
Idempotent: a pending export for the caller short-circuits and
returns the existing notification. Terminal-state notifications
(ready / failed / expired) don’t block; a fresh POST creates a new
notification + job, leaving the prior history intact.
Allowed under both UI-session and API-key auth — export is read-only and a legitimate programmatic flow (compliance tooling, backups, data migrations). Also allowed for soft-deleted users in the 30-day grace window so they can retrieve their data before erasure.
Documentation Index
Fetch the complete documentation index at: https://docs.roughy.ai/llms.txt
Use this file to discover all available pages before exploring further.
Either your Supabase session JWT (UI flows) or an API key minted via POST /api-keys (programmatic flows). Pass it as Authorization: Bearer <token>. The server inspects the token format and routes to JWT or API-key verification automatically.
Successful Response
API projection of a data_export_ready-type notification.
Used by POST /api/v1/users/me/export (returns 202 with this body)
-- the typed payload lets the frontend render the right state
variant straight from the discriminated union.
"data_export_ready"Export requested; arq job not yet started or in flight.
{
"requested_at": "2026-05-02T08:54:52.423000Z",
"status": "pending"
}