Clean up expired guest accounts.
curl --request POST \ --url https://auth.example.com/api/admin/guest-users/cleanup \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "dry_run": true, "limit": 100 }'Reports expired browser resume credentials and existing deletion requests without mutation by default. With dry_run=false, resumes original deletion requests first, then processes at most 16 credential or job candidates per request. Pass next_cursor back as cursor to continue beyond held or pending candidates while has_more is true. A null next_cursor restarts the next sweep. Cursors expire when the verified storage inventory changes. complete=false includes pending work and legal holds; a partial response does not mean all guests are erased. A 503 reports unavailable or unverified storage rather than a successful empty cleanup.
Authorizations
Section titled “Authorizations ”Request Body
Section titled “Request Body ”object
Opaque selection position from next_cursor; it does not grant authority.
Example
{ "dry_run": true, "limit": 100}Responses
Section titled “ Responses ”Guest account cleanup response.
object
object
object
Example
{ "dry_run": true}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}