Read your legacy deletion request while its login is still valid
Requires a valid original login and forbids impersonation. Better Auth sessions are removed at completion; use the separate private receipt from /v1/me/account/deletion for post-deletion status. No account is created and no patient or receipt selector is accepted.
Authorization
bearer In: header
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/me/passport/deletion-request"{ "deletionRequest": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "status": "pending", "requestedAt": "2019-08-24T14:15:22Z", "processingAt": "2019-08-24T14:15:22Z", "completedAt": "2019-08-24T14:15:22Z", "failedAt": "2019-08-24T14:15:22Z", "failureCode": "string", "policyVersion": "string", "scope": "medbuk_app_data", "retained": [ "string" ], "notProcessed": [ "string" ], "notice": { "version": "string", "en": "string", "ms": "string" } }}Your private latest readings and chronological timeline GET
Latest readings exclude hidden and superseded records. Timeline is newest first; follow nextCursor for older readings. Use visibility=hidden for the owner's restorable hidden records. Full immutable history remains in private export and record history.
Request deletion of your private health passport POST
Legacy request endpoint. Creates an auditable pending request and returns 202 Accepted. Repeated requests return the existing open request. New clients use /v1/me/account/deletion to preserve a private status receipt after Better Auth credentials are removed. Processing uses the privileged deletion worker; clinical, financial/safety/audit records and backups are handled separately.