Prospeo 'Bad Request' Issue: Any Updates on Fixing? | Clay

·

Prospeo is coming back with 'bad request' about 80% of the time and has been happening for nearly 2 months. Any update on fixing this? (Table)

Clay Team
APP
·
·
Hi, thanks for getting in touch!
Clay Team
APP
·
·
Based on previous engineering responses. Prospeo is unable to check the MX records for some of those domains so it just errors out. That's something specific they havehttps://prospeo.io/api/email-finder#::~~::text=The%20domain%20name%20you%20submitted%20is%20not%20reachable%20or%20does%20not%20have%20valid%20MX%20records
Keethu R.
·
·
Hi Owen L., working on updating the error messaging here so the exact error is clearer
Owen L.
·
·
Thanks for the updates Juan P. & Keethu R. - In the table above I had the error coming back for 80 - 90% of the rows, is that common?
Clay Team
APP
·
·
we will see how the fix affects this
Keethu R.
·
·
I think it really depends on your data but sometimes it is possible - with the update though, you'll be able to see what the exact error is and sometimes it's an input issue that you can tweak so that may help! The error update is live but you'll have to add new Prospeo columns to see those changes
Keethu R.
·
·
Let me know if you have any questions!
Owen L.
·
·
Thanks for updating that Keethu R.. That makes sense regarding the data quality and the inputs.