as far as I know it’s not possible to change the password using api, but I guess you can use roles and permissions to allow or prevent the user from using the device.
I think I understand what you propose, but I basically want to create 1 user per device (and then give a person access by giving him/her the password that is valid at the time they have booked a house).
If I would have to create a user for each person using the house I would end up creating (and deleting) 1000’s of users each year…
Okay, you can create an account for example myorganizationuser1@gmail.com and share this account with the user, after 1 month for example you can change the account password and give it to another user, you got the idea right ?
yup, that is the idea I had. But this cannot be a manual action, some hire a house for a weekend, some for three weeks etc. And then (hopefully if the orders keep coming in) for hundreds pr maybe thousands of houses… Don’t wanna be resetting 100 accounts by hand each weekend So looking for an automated process…
Hello. That’s the interesting use case. At the moment you can’t automate it. But this is something we gonna have in the nearest future for sure (OAuth 2 API for orgs and users)