v1
latestOpenAPI 3.0.02026-07-267331140.7 KBSafe Management
Reset Safe Account
Permanently deletes the Safe account for the authenticated user. This operation is irreversible and should be used with caution.
Prerequisites for Safe Reset:
- Safe account must exist for the user
- Safe account must not be in a properly configured state (AccountIntegrityStatus.Ok)
- Safe account must not have transactions in the delay queue (AccountIntegrityStatus.DelayQueueNotEmpty)
- User must not have any active (non-voided) cards linked to the Safe
- Safe account must have zero token balance (all tokens must be withdrawn first)
Use Cases:
- Reset a Safe account that failed during deployment or setup
- Clean up a Safe account that is in an inconsistent state
- Remove a Safe account before creating a new one
Important Notes:
- This operation permanently deletes the Safe account record from the database
- The actual Safe contract on-chain is not affected by this operation
- Users will need to deploy a new Safe account after reset
delete/api/v1/safe/reset
Response
Successfully reset the Safe account
Example response
{
"message": "Safe account reset successfully"
}