Sorry you’re having issues. Jeff here, one of the Particle engineers. Just to clarify, the cURL request you posted above is a sample. You will need to add your user and organization’s information for this to work. I’m sure you knew this, but just wanted to double check:
organization should be set to neighbour Authorization: Bearer XXXXX should include a real access token
There is a possibility that the access token that you see in build has not been updated to include the correct permissions. I will direct message you a token that I know has the correct permissions. We are working on an improvement to update all existing access tokens with organization permissions when you create an org, but this is not in production.
If you are choosing Simple, be sure to pass scope=create_customer when creating your OAuth client. This ensures that your client can only create customers for security purposes
Yes, I had replaced the dummy arguments. I have received the new key and I still get the same result. I have reset my access key and also tried with this key - same result.
OK, next step - create a customer. I presume the Bearer token is the same token I used to create the auth client (the one you sent me)? I am now getting this error:
{
“ok”: false,
“error”: “Organization not found.”
}