I was looking at the api endpoints documentation, but could not find it:
I’d like to deactivate users via the api. This way, I can deactivate their access to a portal based on various conditions in my database.
Don’t have it yet, my friend.
I’ve suggested it to the team to see if we can get something in the future. You could also try to turn off your caching so changes made in your DB reflect instantly? This could slow your application though.
I’m aware it’s not there yet, that’s why I raised this feature request to check if there’s more demand for this from the community 
I’m afraid I don’t understand completely what you mean by turning of the cache in this context? I’d would like to keep formerly active users in my AT database, but not counting as as an active Softr user. I can do this manually, but was looking for an automated solution via a possible api endpoint.
@stenkate did you consider changing user group defining attributes putting them into limited group instead ?
Thanks for thinking along 
I did and use a specific group defining attribute to limit options for them in the automation backend and Softr portal. But for this specific group I’d like to keep the data in the database, but just deactivate them for the portal so they also don’t count within the plan’s user limit.
+1
+1
Thanks for thinking along and notifying us about this new feature which I probably missed in one of the product updates.
It unfortunately does not cover my original request, since I don’t want to delete users in my database. They will get a specific status, hence my request to deactivate Softr users via the api so I can create some automations.
It looks like Softr’s new deactivation settings only facilitates this when I completely delete user records in the database?
Or can it also work when in Softrs sync settings I choose some selection rules, and when an users does not match that selection it’s seen ‘record get’s deleted’ and so the Softr user is deactivated? If so: will the user automatically be reactivated when the user record is matching the sync rules?
I believe that’s the case. I’d test it on a record to confirm.
I found the updated documentation which clarifies that this can work in line with my situation I think:
You can also control what happens to a user record if they even cease to meet the filtering criteria. For instance, if an employee leaves and you mark them as “Inactive” in your data source, you may want Softr to (…)
Deactivate their user account - deactivating a user retains their data source record and record in the Softr app, but they cannot login and they do not count towards your user limit. They can be reactivated at any time either manually or automatically by the sync rules.