I'd like to scan our end users for identities that are undeliverable so that we can automate rudimentary bounce error reporting. The only method I can think of is to loop through each end user, then loop through their undeliverable count / deliverable value.
Is there a way to scan/filter for identities that have been marked undeliverable or that have an undeliverable_count > 0?
Hi @matthew14 did you ever figure this one out? Or find a solution to getting something similar to bounce email notifications.
@richard11 - I did not, the search API doesn't really think about things that way from what I have pieced together
You’re on the right track: the only place those bounce flags live is on the user’s email identity.
The Identities API exposes both deliverable_state and undeliverable_count for email identities, but there isn’t a global “search identities” endpoint, so you can’t filter across the whole account in one call.
You need to fetch identities per user and filter where deliverable_state = "undeliverable" or undeliverable_count > 0
To avoid looping over every user daily, pair it with the Incremental Users Export so you only process users that changed since your last run, then hit /users/{id}/identities for those and log alerts for anything undeliverable.
That keeps the job light and within rate limits while still catching fresh bounces (Incremental Exports)
If you also need event-level reasons for specific failed sends, the Email Notifications API can tell you why a message bounced, but that’s per-email delivery status, not a “who is undeliverable” directory.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Zendesk does not offer a direct API endpoint or filter to scan identities based on their undeliverable status or undeliverable count. To identify such identities, you need to programmatically loop through all users, fetch each user’s identities via the API, and then check the undeliverable boolean or undeliverable_count fields on each identity. This process can be automated but may require careful handling of API rate limits and could be optimized by checking only recently updated users. Overall, detecting undeliverable identities requires a custom solution that aggregates this data through multiple API calls and filters it on your side.