Creating a New Customer (two legged auth) - Now Working


@Kevin were you able to get this working? Your cURL request looks good. scope is the key and would be the value of the query param for use in a form.

If you are still having problems, DM me your org name, customer email, and client ID you are using and I can look into it more.



Hi there, I am getting the error “Organization not found.” when trying to create a customer using curl. After reading above, I think I’m probably entering my organization in the URL incorrectly.

Can someone please tell me where I can find my “:orgSlug”?


Hey Dan,

Your confusion is totally valid – in our recent update to the console, we have since abstracted the concept of organizations from the front-end. If you created the product pre-console, then you created an organization and set its name. The slug would just be the downcased and dasherized version of the name (i.e. “Jeff Organization” => “jeff-organization”).

If you just created your product, the slug of the organization is the same as the slug of the product. You can find this in the console, when you navigate to any product-specific URL. It is the downcased/dasherized version of the product name + the product version. For example, on the devices page for a product called “Foo” with version “v1”, the URL would look like:, and the slug would be “foo-v1”.

Does this help?


Tutorial for a simple web app

Yes, thankyou for the clarification - that makes a lot more sense now. The docs probably should mention this!


Hey @jeiden,

Adding a customer via the API now seems to work for me, with a response similar to what I was expecting. However, even after waiting a day to update, I still cannot see any of the added customers in the console. Is there something I’m missing?


Hey @dan.s,

The customers will actually appear when they have claimed ownership of a device. This is definitely confusing, and something we have a ticket to improve. It would make more sense to show those customers as soon as they are created.

For now though, claim a product device and you’ll see the customer appear.


Issues adding customers to a product

Sorry to exhume this post. I’m working through this process for simple auth. My end goal is to get a basic prototype going destined for an ionic app (angular). I am having trouble working out the curl commands to go through creating a client; customer; token etc in an effort to gain a clear understanding of what all the steps are. There is great information but it’s scattered between the guide, the reference and the community forum. Take this post. This is the only reference anywhere that explains what organization is, or where to find it. However, copying the string straight from the browser console, when I try:

curl -X POST -H “Authorization: Bearer 1234” -d name=“IonicMobileApp” -d type=installed organization=mXXXXp-v1

curl: (6) Could not resolve host: organization=mXXXXp-v1

although it does return an otherwise sensible looking object:


And when I try:

curl -X POST -u ionicmobileapp-8868:1234 -d email="" -d password=“myPAssWrd”
{“ok”:false,“error”:“Not Found”}

I’m more from the hardware world, so I know much of this may seem obvious. I don’t suppose anyone could point me at a guide that might help. It’s just not fitting together. ANd after this I’ll have to figure out how to squeeze this into Angular 2 for more fun and games?

Unless someone has done this in Angular 2 already. Would be nice to cut out the middle man!

Thanks forum.



Hey @monkey - this reference documentation should be helpful to you:


Edit to my own question, in the hope that this might be helpful for others.

If like me, you’re having trouble creating customers or tokens, with errors like: {"ok":false,"error":"Organization not found for user's role."} or {"ok":false,"error":"Not Found"} refer to rickkas7 s post. There is an very succinct explanation of tokens and scope, which is not covered in the documentation.




Can we incorporate this into the docs? @rickkas7?


I’m trying to get a product through initial prototyping but I’m struggling with the js api. I used a test email address to create an account and claim a device etc etc to test out the process. All worked fine. I’m now expanding it into an ionic app. But as soon as I enter a new ‘test’ email address pretending to be a new customer, I run into problems. If I create a user with the product client id & secret (with limited scope), that works. This is the method given in the docs. But I can’t subsequently login as that user using the same client id & secret? (Why is this?) Strangely, I can log in using id+secret=particle-api or anything else for that matter. But the killer is that I can’t then generate a claim code, at all?! What’s going on? This is so confusing. I would expect to create a Particle object; pass my product specific client credentials into the constructor and use this for everything. What reason if any is there to use blank/generic client id&secret. And is there a case where more than one Particle objects will be needed within an app?

I’m using ionic by the way, so as far I can gather, I need to use the restricted scope client credentials approach. I’ll keep working on it in the meantime, but I’d really appreciate some expert advise.




@monkey — as always, specific code snippets will help our team get a better understanding of where the problem lies.

I’m not exactly sure how your requests look, but I’ll recap the process from our docs. After a customer (remember that customers are different than users) is created and the device claimed, the only remaining piece is authenticating API requests correctly to interact with that customers’ devices. To do this, you’ll need to generate access tokens scoped to the customer. This will allow you to do things like call a function, check a variable, etc. on behalf of the customer from your server or mobile/web app.

Here is our API reference documentation on how to create customer-scoped access tokens using your OAuth credentials:

It is also described in the Two-legged auth guide here:

Good luck,



Yes, it works! Customers are different than users. Because the notion of customers was not included in the javascript api, I made the assumption / oversight that users were equivalent to customers. Having corrected that assumption, it now works. Thanks.