_id, name, is_default are preserved). Use this when a sandbox entity has drifted or you simply want a clean slate for testing.can_edit_entity or wildcard * ACL access to the live entity that the sandbox shadows. The reset is blocked while a create/reset is already in progress for the same sandbox (activation_status is pending). During the reset, activation_status is set to pending, then to completed on success or failed if provisioning on the remote sandbox server fails.curl --location '/entity-sandbox-resets' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"entity_sandbox_id": "01JABC1234567890ABCDEFGHIJ"
}'{
"message": "Entity sandbox reset successfully",
"status": "success",
"data": {
"id": "01JABC1234567890ABCDEFGHIJ",
"entity_id": "01JXYZ9876543210ZYXWVUTSRQ",
"name": "Default sandbox",
"is_default": true,
"activation_status": "completed",
"sandbox_entity_id": "sbx_ent_7f3a9c1d"
}
}