Fwith the return code you tell zitadel to not send any emails, but rather return the verification code in the response, this allows you to send your own emails to your users and verify it with the code afterwards
Fif you choose send code, ZITADEL will send the emails, if you send no urlTemplate, ZITADEL will take the default url, which points to our hosed login where the user will be able to verify, the urltemplate also gives you the possiblity to specify your own url where the user should be sent with the email link, this allows you to implement your own ui
Fcan you send the curl you are doing?
FNow I see, it looks like you have mixed up two different requests, the url you are pointing to is the following from our v1 api, where we always send the email, there is no possiblity to set returnCode: https://zitadel.com/docs/apis/resources/mgmt/management-service-add-human-user
Create a new user with the type human. The newly created user will get an initialization email if either the email address is not marked as verified or no password is set. If a password is set the user will not be requested to set a new one on the first login.
Fwith the request from the version 2, you are able to tell zitadel to return the code: https://zitadel.com/docs/apis/resources/user_service_v2/user-service-add-human-user
Create/import a new user with the type human. The newly created user will get a verification email if either the email address is not marked as verified and you did not request the verification to be returned.
Fthis doesn't have to do with self hosting or cloud, the apis are available to all environments
Fon which version do you run?
Fthe v2 api is available from version v2.58.0
Fhm. with that version it should actually work. do you get an error message, or an error code?
Fcan you send again the code you are running now?