How to check and remove false-positive email suppressions via AutoSend Suppressions API?

Email Deliverability
1

We recently had an incident where a client’s corporate mail server temporarily rejected incoming emails during an internal server migration, causing multiple recipient addresses to hard-bounce and get added to our AutoSend suppression list.

Now that their server issue is resolved, transactional emails (such as verification codes and password resets) sent to those addresses are still getting automatically dropped by AutoSend due to the suppression record.

Is there a programmatic way to check if an email address is currently suppressed and remove or unsuppress it using the AutoSend API (without having to manually search and delete entries in the dashboard)?

2

Resolving False-Positive Email Suppressions Programmatically

When a recipient’s mail exchanger temporarily fails or misconfigures MX/DNS records, incoming emails may generate hard bounce events, automatically adding those addresses to your AutoSend suppression list to protect your sender reputation. Once the recipient’s mail server is healthy again, you can check suppression status and remove the addresses directly via the AutoSend REST API.

1. Check if an Email is Suppressed

To inspect the suppression entries or groups associated with a specific recipient email address, query the POST /v1/suppression-groups/email/entries endpoint:

// Check suppression groups for a specific email
const res = await fetch("https://api.autosend.com/v1/suppression-groups/email/entries", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.AUTOSEND_API_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    email: "client.admin@company.com"
  })
});

const data = await res.json();
console.log("Suppression Status:", data);

You can also search entries across a specific suppression group with date and reason filters via POST /v1/suppression-groups/entries:

curl --request POST \
  --url 'https://api.autosend.com/v1/suppression-groups/entries' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "reason": "BOUNCE",
    "page": 1,
    "limit": 20
  }'

2. Remove / Unsuppress Addresses on Demand

To clear false-positive suppressions and resume email delivery to the affected recipients, call the Bulk Unsuppress endpoint (POST /v1/suppression-groups/emails/unsuppress).

Unsuppressing Globally:

Pass isGlobal: true to clear global bounce or complaint suppressions across your account:

const unsuppressRes = await fetch("https://api.autosend.com/v1/suppression-groups/emails/unsuppress", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.AUTOSEND_API_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    emails: ["client.admin@company.com"],
    isGlobal: true
  })
});

const result = await unsuppressRes.json();
// Returns: { success: true, data: { unsuppressed: 1 } }
console.log(`Successfully unsuppressed ${result.data?.unsuppressed} address(es).`);

Scoped Group Unsuppress:

If the user was unsubscribed from a specific list or campaign category, pass the specific groupId:

await fetch("https://api.autosend.com/v1/suppression-groups/emails/unsuppress", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.AUTOSEND_API_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    emails: ["user@example.com"],
    groupId: "grp_product_updates"
  })
});

:light_bulb: Best Practice for Customer Support Portals

You can wire this unsuppress endpoint directly into your internal admin dashboard or customer support chatbot. When a customer reaches out saying they aren’t receiving verification emails, your support tool can automatically check suppression records and trigger an unsuppress call without requiring manual dashboard access.

Relevant Documentation