How to get what email got bounced via API? | XM Community
Skip to main content

Hi Community,

I’m curently using Get Directory Contact History api.qualtrics.com/f30cf65c90b7a-get-directory-contact-history to get Email status of a specific Distribution. However, the API is running supper slow and it’s slowing down the whole process.

Is there any other way to get all the Email that Bounce, Block, Error of a Distribution (Not how many failed email but what email failed)?

If I still have to use Get Directory Contact History, how can I speed this up?

Thank you!

@Nam Nguyen As far as I know, this is the only available one. Do you route the requests via the most appropriate data center? And what is „super slow“ for you? 

If its a specific distribution, then you should probably be looking up the distribution history: https://api.qualtrics.com/8840efb2c71a8-list-distribution-history

 

If its a specific distribution, then you should probably be looking up the distribution history: https://api.qualtrics.com/8840efb2c71a8-list-distribution-history

 

@ahmedA I’m curently asking the IT team to try this. Wish we have a way to get just the failed one.

Overread the distribution detail… @ahmedA is totally right. The status property of the result should provide the information that is searched for.

@Nam Nguyen As far as I know, this is the only available one. Do you route the requests via the most appropriate data center? And what is „super slow“ for you? 

@chackbusch My client did route it through the most appropriate data center. I think supper slow mean they have to scroll through every contact and JSON pages to find the right distribution status.

@Nam Nguyen in the GUI there’s now an option to have the weekly distribution history emailed to you. This has to be done per survey. Maybe look at that as archival tool for faster lookups in the future.

@Nam Nguyen in the GUI there’s now an option to have the weekly distribution history emailed to you. This has to be done per survey. Maybe look at that as archival tool for faster lookups in the future.

@ahmedA Great idea, but our client wants everything to be automatically from their side, Intergrated with their system

Leave a Reply


Terms & Conditions