GET
Get GDPR export status

Overview

Polls a single gdpr_export_jobs row by id. Used by clients that want to show a “your data is being prepared” UI between export request and the email arriving. When the job reaches READY and the row has not yet expired (expiresAt > now), the endpoint mints a fresh 24h signed download URL on every call — so a user who lost the original email link can still download via this endpoint as long as the underlying row is alive.
The signed URL TTL is 24 hours. The email link uses the same TTL — but since the URL is re-minted on every poll, the practical download window for the user is as long as the gdpr_export_jobs row exists (up to 30 days, then it’s cleaned up by gdpr-erasure along with the underlying S3 object).

Authentication

Bearer <accessToken> (user scope) required. The route also gates on requireOnboarded. The job is scoped to the authenticated user — calling with another user’s jobId returns 404 NOT_FOUND (enumeration-safe — we never reveal that the job belongs to someone else).

Path parameters

Query parameters

None.

Request body

None — this is a GET.

Response — 200 OK

Example — PENDING

Example — READY

Example — FAILED

Error responses

Example error — 404 NOT_FOUND

Polling guidance

The export worker typically completes in seconds for a fresh account, up to a minute for a heavily-active user. Suggested client polling:
  • Initial wait: 2 seconds.
  • Then poll every 5 seconds until status === 'READY' or status === 'FAILED'.
  • Stop polling after 5 minutes — show the user “we’ll email you when it’s ready” and rely on the email.
The worker emails the user on READY with a one-shot 24h link, so a user who closes the page still receives their data.

See also

curl

Postman

See docs/postman/swappr.postman_collection.json → Me → Export Status.