I have a script that runs daily to create new users via the API. Up until a few days ago, when the post would complete, the response included the user_id of the newly created user. Now the API no longer does so? But the API docs indicate that it should. Discourse API Docs

Is the user being created? My guess is that for some reason the user isn’t being created and that’s why it’s not returning the user_id.

The users are getting created. I have confirmed. And the API gives back this status but it’s missing the user_id { "success": true, "active": true, "message": "Your account is activated and ready to use." }

Yeah. That seems like a bug, then. I looked for explanations in Commits · discourse/discourse · GitHub but didn’t find one.

To confirm the issue, I created a user through the API on 3.4.0.beta3-dev and it returned user_id in the response. { "success": true, "active": true, "message": "Your account is activated and ready to use.", "user_id": 3 } I did it again after upgrading to 3.4.0.beta4-dev and user_id is then missing: { "success": true, "active": true, "message": "Your account is activated and ready to use." }

So you’ve narrowed down where the errant commit is.

Just a hunch app/controllers/users_controller.rb main # If the user was created as active this will # ensure their email is confirmed and probably related to DEV: Change hide_email_address_taken default to true (#30293) · discourse/discourse@c1c7ea8 · GitHub explained here: [תמונה] Hiding "e-mail taken" on sign-up by default megaphoneAnnouncements Background Under the current default settings, when signing up for an account with an e-mail that has already been registered, the sign-up form will inform of that: [Screenshot 2024-12-16 at 12.32.31 PM] We are changing the default setting to not give away this information. Instead, the sign-up form will look like this, regardless of whether the e-mail is already registered or not: [Screenshot 2024-12-16 at 12.30.04 PM] This also affects password resets in similar ways. With the setting di… [תמונה]Hiding "e-mail taken" on sign-up by default If you want to change back to the old default, you can set the hide_email_address_taken setting back to false. I guess it would be desirable to override this behavior when it’s a request made using an admin API key?

[תמונה]Hiding "e-mail taken" on sign-up by default hide_email_address_taken Thank you! Changing that setting did restore the API result so that I get the user_id in the result after creating a user.

API, יצירת משתמש, כבר לא מחזירה user_id

תמיכה

weber-s (Samuël Weber/GwendalD) 17 באפריל,‏ 2025,‏ 1:22pm 9

Hello,

Same here…

Is it something currently ongoing for the devs? Because it may be tricky to remember that this settings counteract the docs

נושא		תגובות	צפיות
Can't add user via API Development rest-api	6	1544	17 בנובמבר,‏ 2020
Disable account confirm emails when creating users via API Development rest-api	26	7247	5 באוגוסט,‏ 2020
Cant create active user via api, Again Product Support	1	586	8 באפריל,‏ 2021
Creating Active Users via the API gem Development rest-api	39	11309	5 באוגוסט,‏ 2020
Creating user via API Development rest-api	10	7622	5 באוגוסט,‏ 2020

API, יצירת משתמש, כבר לא מחזירה user_id

נושאים קשורים