If I am using two-legged authentication, and the Particle API is truly opaque to my customers why must I supply an email address when creating a new product scoped customer?
In the Particle documentation it states:
The Particle shadow customer should be created at the exact time that the customer is created in your system.
My thinking goes like this. I would like to create some sort of email validation system to ensure that my users are creating valid email accounts within my web application. If I create a customer before I validate their email there is a chance that the email will be wrong. The Particle API doesn’t seem to let you view customers after they are created or delete customers, it seems their only value is to be a handle for creating tokens and claiming devices. This leads me to think, why can’t I just create a unique identifier (e.g. “abcdefg12345”) that I pass instead of an email address and store that as my particle_customer_id. Is there any real reason that this actually needs to be an email address? The documentation seems to all request a email address, is there any harm in just supplying a GUID instead?
Using this system I can truly create my customer before they have validated their email and I can manage their email address in my application without worrying about what the presentation of that is in Particles.