# API - Email is invalid error (email is spam but technically a valid email)

**URL:** <https://forum.mautic.org/t/api-email-is-invalid-error-email-is-spam-but-technically-a-valid-email/25905>\
**Category:** Product Support\
**Created:** [November 1, 2022, 12:12am UTC](https://forum.mautic.org/t/api-email-is-invalid-error-email-is-spam-but-technically-a-valid-email/25905 "2022-11-01T00:12:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tornmarketing](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/tornmarketing/32/11603_2.png) [@tornmarketing](https://forum.mautic.org/u/tornmarketing)\
**Post date:** [November 1, 2022, 12:12am UTC](https://forum.mautic.org/t/api-email-is-invalid-error-email-is-spam-but-technically-a-valid-email/25905/1 "2022-11-01T00:12:58Z")

</div>

**Your software**  
My Mautic version is: v4.4.3

Currently doing a contact sync via API (n8n) and getting a hard error “Error: Request failed with status code 400” with invalid email.

Fairly big headache

Email address example is obviously spam but to me is still technically a valid email address  
email: **[w.s.y.1.2.3.4.@hotmail.com](mailto:w.s.y.1.2.3.4.@hotmail.com)** is invalid.

Question 1  
Is there a means of turning off validation rules for API?

Question 2  
Where would 1 find all these rules, definitions and errors you could potentially hit via API

Question 3  
Is there a means of running these validation rules before an create/update contact via API?

---

<div class="post-metadata">

**Author:** ![tornmarketing](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/tornmarketing/32/11603_2.png) [@tornmarketing](https://forum.mautic.org/u/tornmarketing)\
**Post date:** [November 1, 2022, 3:11am UTC](https://forum.mautic.org/t/api-email-is-invalid-error-email-is-spam-but-technically-a-valid-email/25905/2 "2022-11-01T03:11:04Z")

</div>

Decided to break it down the flow into batches and then ignore any errors.  
Workaround and makes me question what else it is throwing but yeah 🙂 … power on

---

<div class="post-metadata">

**Author:** ![robm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/robm/32/260_2.png) [@robm](https://forum.mautic.org/u/robm)\
**Post date:** [November 1, 2022, 9:15am UTC](https://forum.mautic.org/t/api-email-is-invalid-error-email-is-spam-but-technically-a-valid-email/25905/3 "2022-11-01T09:15:45Z")

</div>

This is interesting. I use n8n extensively to bring new contacts to Mautic and have had no such issues. Unless I am not looking in the right place.

To be clear the API is not querying a spam data base somehow, its actually the email structure that is failing the validity test for an email. In your example to many periods in the email address?