Right now on my discourse set up, I have it set up to invite only, admin must approve users, and allow new registrations. The issue I am having though is when I create a user via my API I still have to log in and approve the user on the forum. So I was wondering if I had to uncheck any of those three to be able to make the user and they are auto created but I don’t have to log in to the discourse to approve them. I don’t want other users to be able to invite other users to join though as I am creating users based on another sites sign ups.

With this fix, you can now create an active user with a single api request and they won’t receive an email confirmation. https://github.com/discourse/discourse/commit/fec68d3d25bfc80d084af52e17882ad886fd5cd0

Once you create the user through the API, you will need to make another api request to this endpoint to approve them: http://localhost:3000/admin/users/ /approve Are you using the discourse_api gem to talk to the API or some other way?

Thank you, I’m using pydiscourse. Didn’t know you could do approvals. I ended up having to tweak their wrapper to have it work. But now it’s working. Thank you

[image] blake: you will need to make another api request to this endpoint to approve them: http://localhost:3000/admin/users/<user_id>/approve Hello @blake, Can you please give an example? I tried using this in vain. curl -X PUT "http://localhost:3000/admin/users/batman/approve?api_key= &api_username=vikas"

try using the of the user instead of the username?

[image] blake: try using the of the user instead of the username? Perfect, worked like a charm. I got confused it with username. Thanks much. Now, the user gets an activation email which I want to avoid, will look around how to avoid that.

[image]Creating Active Users via the API gem Theoretically, you could create an account with a fake email address, deactivate, update the email address to the real email, then activate the account. Unfortunately, this is too much of a workaround for the project we are working on. We have decided to settle with sending our users 2 emails. Not an ideal workflow. ^ I think that might be how you can get around the activate email thing /shrug

Sorry to necro this post but it appears to be the most relevant discussion. I’m currently adding users via the API but they aren’t getting the verification email. Is there something I can add to the response to ensure that this email gets triggered? I’ve seen people setting active to true but that’s what I don’t want since I want them to be pruned if they never verify. Setting it to false doesn’t seem to trigger the activation email though.

Hi, I think I’m having similar trouble using the pydiscourse module. If I create a user with active=true I get the following response: {'success': True, 'active': True, 'message': 'Your account is activated and ready to use.', 'user_id': 212} And all seems well on the dashboard: [19%20PM] However, when I attempt to log in using my newly created account I see this: [image] Weird! OK, let’s resend the activation email (even though none was sent originally). The email comes through and I open the link inside: [image] Only the button doesn’t do anything! I tried adding an HTTP get to /admin/users/ /approve and the API call returns something sensible, but still I get the “You can’t log in yet” message when I attempt to log in. Does anyone have any clues as to where I went wrong? Thank you!

OK I found this post: [image] Creating Active Users via the API gem Development I just spent the better part of today working on this and found a workaround for it. Here’s the process you have to go through to make this work. Create the account and set active=true. Note the user_id that is provided from the API call. In your above example, the user_id=7 so we’ll use that in this example. Make an API call to deactivate the user account. It will be something like this: http://discourseURL/admin/users/7/deactivate.json?api_key=xxxx&api_username=yyyy Make an API call to act… If I do the create/deactivate/activate trick the click here to activate your account button works but I still can’t log in with active=true.

Creating user via API

Development

blake (Blake Erickson) December 23, 2016, 12:10am 7

^ I think that might be how you can get around the activate email thing /shrug

Topic		Replies	Views
Creating Active Users via the API gem Development rest-api	39	11285	August 5, 2020
Disable account confirm emails when creating users via API Development rest-api	26	7218	August 5, 2020
Can't add user via API Development rest-api	6	1537	November 17, 2020
Cant create active user via api, Again Product Support	1	575	April 8, 2021
Approving an already-existing user through API? Development	3	1884	October 13, 2017

Creating user via API

Related topics