Current State:

Large organisations frequently encounter issues where users do not receive critical Atlassian emails (e.g. verification codes, password reset emails, Jira/JSM notifications). In many cases, the root cause is that the user’s email address has been suppressed by Atlassian’s email infrastructure (e.g. due to prior bounces or complaints).

Today, there is no customer-facing API that allows organisation administrators to programmatically check whether a given user/email is currently suppressed. This makes it difficult to:

• Diagnose “email not received” issues at scale

• Proactively monitor suppression across thousands of users

• Integrate suppression checks into internal support, onboarding, or compliance workflows

Proposed Future State:

Provide a public, authenticated API endpoint that allows organisation administrators to query the suppression status of users in their organisation.