Anonymous ← Tell Us What You Think My feedback 1 result found Revert recent change regarding 400 Bad Request on non-working email addresses 24 votes Vote Vote Vote We're glad you're herePlease sign in to leave feedback Signed in as (Sign out) Close Close Vote We’ll send you updates on this idea 3 comments · General Feedback » API · Delete… · Admin → How important is this to you? Not at all You must login first! Important You must login first! Critical You must login first! We're glad you're herePlease sign in to leave feedback Signed in as (Sign out) Close Close An error occurred while saving the comment Anonymous commented · Nov 19, 2018 · Delete… I completely agree that this breaks HTTP standards. A 400 error should be returned for a badly formed request to the API, not also for a bad email - those are two separate things. I thought you could perform a separate call to track the email's progress through the system? As outlined here: https://bradgignac.com/2014/05/12/sending-email-with-python-and-the-mailgun-api.html How am I meant to properly test or log these API calls when I can't distinguish a badly formed request from an invalid email? Save Submitting... Anonymous supported this idea · Nov 19, 2018
Anonymous
I completely agree that this breaks HTTP standards. A 400 error should be returned for a badly formed request to the API, not also for a bad email - those are two separate things.
I thought you could perform a separate call to track the email's progress through the system? As outlined here: https://bradgignac.com/2014/05/12/sending-email-with-python-and-the-mailgun-api.html
How am I meant to properly test or log these API calls when I can't distinguish a badly formed request from an invalid email?