You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2021. It is now read-only.
I don't know if this is the right place to submit this, but...
When subscribing an email to a list via the API which is already present, the server returns 400. 400 is not appropriate for a request that was correctly formed. It should respond with 409 Conflict instead. This would also make it easier for APIs to distinguish between a duplicate and an actual request error.
Just my 2 cents.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello
I don't know if this is the right place to submit this, but...
When subscribing an email to a list via the API which is already present, the server returns 400. 400 is not appropriate for a request that was correctly formed. It should respond with 409 Conflict instead. This would also make it easier for APIs to distinguish between a duplicate and an actual request error.
Just my 2 cents.
The text was updated successfully, but these errors were encountered: