The complement to Step 3: POST /allowlists/delete takes an email address off the allowlist. Useful for cleaning up test data, or for revoking an override when someone really shouldn't be receiving mail from you any more.

Try it

trim($_POST['email']), ]); // --------------------------------------------------------- if (!mandrill_is_error($result)) { $deleted = $result['decoded']['deleted'] ?? false; if ($deleted) { echo '

Removed. ' . h($_POST['email']) . ' is no longer on the allowlist.

'; } else { echo '

Nothing to remove. ' . 'The API returned deleted: false, which means the ' . 'address wasn\'t on the allowlist in the first place — not an error.

'; } } render_debug($result); } ?>

The call

$result = mandrill_call('/allowlists/delete', [
    'email' => 'user@example.com',
]);

if ($result['decoded']['deleted']) {
    echo 'Removed';
}

Response shape

{
    "email":   "user@example.com",
    "deleted": true
}

Same convention as add: deleted: true means the row was there and got removed, deleted: false means it wasn't there. Both are HTTP 200.

Heads up: removing from the allowlist does not add the address to the denylist. It just removes the override. The address will now be subject to Mandrill's normal rejection rules again.

→ Next: actually send an email