Skip to main content

NationBuilder not compliant with s3.2.4 of RFC 2822

PUTting a payload like this: {"person": {"email1": "example&example@xtra.co.nz"}} To the /people/:id endpoint (and I assume others) returns: { "code": "validation_failed", "message": "Validation Failed.", "validation_errors": [ "email 'example&example@xtra.co.nz' should look like an email address" ] } This is due to the ampersand and is not in line with section 3.2.4 of RFC 2822 (https://www.ietf.org/rfc/rfc2822.txt). It means some of our members' email addresses can't be used with NationBuilder.

considering

Email addresses cannot include ampersands in NationBuilder. This is not specific to our API; it is also not possible to manually add an email address through the control panel with this symbol. 

I've moved this post (originally submitted through our API developers forum) over to our Suggest page as a feature request to allow the submission of email addresses with '&' symbols.

Official response from

Share this post

Showing 2 reactions

How would you tag this suggestion?
Please check your e-mail for a link to activate your account.