Hi everyone,
I am developing a registration system that needs to programmatically activate user accounts (is_active=True
) after registration, ideally through the official Open edX REST API.
I have reviewed the accounts API documentation, and although the is_active
field appears in the user schema, sending a PATCH request to update it returns a success status but does not actually change the value of is_active
(the user remains inactive).
- Is it possible to update
is_active
via the API out of the box in current Open edX releases (Palm, Quince, Sumac, etc.)? - If not, is there an officially recommended way to activate users programmatically, other than directly updating the database or using Django admin?
- What is the current best practice for activating (or deactivating) user accounts in an automated workflow, especially for onboarding flows managed from external systems?
I have read historical discussions about the ambiguity of is_active
(email verification vs. account disabling), but I am looking for a clear, maintainable way to activate users after registration that will not break with future Open edX upgrades.
Any guidance or updated best practices would be greatly appreciated!
Thanks in advance.