Cancel a scheduled deletion
Needs `me:write`. Recorded as `user.deletion_cancelled`.
/v1/deletionNeeds me:write. Recorded as user.deletion_cancelled.
Authorization
bearer An access token from this issuer for its account API (resource=<issuer>/me).
In: header
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
curl -X DELETE "https://example.com/v1/deletion"{ "sub": "string", "email": "string", "email_verified": true, "username": "string", "name": "string", "given_name": "string", "family_name": "string", "picture": "string", "locale": "string", "deletion_scheduled_for": "2019-08-24T14:15:22Z", "created_at": "2019-08-24T14:15:22Z"}The apps the signed-in person allowed GET
What they allowed each app that isn't the brand's own, oldest first: signing in to it again doesn't ask again for that. Needs `me:read`.
Schedule the signed-in person's account for deletion POST
It is deleted 30 days later. Their sessions end at once, and each app they had signed in to that registered a `backchannel_logout_uri` gets a logout token; they can't sign in meanwhile. Someone who owns a Synq org hands it over or deletes it first. Needs `me:write`. Recorded as `user.deletion_scheduled`.