# Cloud API: breaking changes without version bump?

**URL:** <https://community.particle.io/t/cloud-api-breaking-changes-without-version-bump/51449>\
**Category:** Cloud\
**Created:** [July 30, 2019, 3:53am UTC](https://community.particle.io/t/cloud-api-breaking-changes-without-version-bump/51449 "2019-07-30T03:53:30Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![incorvia](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/incorvia/32/10961_2.png) [@incorvia](https://community.particle.io/u/incorvia)\
**Post date:** [July 31, 2019, 2:09am UTC](https://community.particle.io/t/cloud-api-breaking-changes-without-version-bump/51449/4 "2019-07-31T02:09:52Z")

</div>

I also would like to check if a breaking change may have broke our app. We use this endpoint to create customers with a secure random hash as the user ID. The endpoint we would use is: [https://api.particle.io/v1/products/PRODUCT\_ID/customers](https://api.particle.io/v1/products/PRODUCT_ID/customers). It seems that the API now expects an email address formatted identifier which used to not be the case. Can I confirm that Particle has changed this behavior and is now enforcing email addresses as customer identifiers? @jvanier

I should add that this changed caused some orders to not go through and are now unrecoverable resulting in thousands of unrecoverable lost dollars. I agree that breaking changes need to be announced and please let us know where to find these announcements.

Original conversation: [Particle Customer Email](https://community.particle.io/t/particle-customer-email/26410/4)

---

_[View the full topic](https://community.particle.io/t/cloud-api-breaking-changes-without-version-bump/51449)._