I understand that you have concerns regarding Auth0 API endpoint rate limits.
First, I would like to clarify that your suggested flow does not need to use the Management API to create a user after the user has been imported into your Auth0 database connection. Doing so may cause a conflict when creating a user in the same database connection because the user with that email address already exists via your import job.
Next, I noticed that your flow involves user creation and user import. Usually, in cases that involve user creation, I recommend that you invite the new user to sign up instead. This would simplify the flow.
However, if your flow involves user import, then I recommend that you do the following instead:
- Bulk import 50-1k users w/o password via Management API’s
/post_users_imports endpoint, which you should be okay with rate-limits on the import side of things.
– Note that there are limits on concurrent import jobs.
- Create a change password ticket
– Using the Authentication API
/dbconnections/change_password endpoint, which may hit Authentication API rate limits, or
– Using the Management API
/Tickets/post-password_change endpoint, which may hit the Management API rate limits.
Keep in mind that rate limits depend on the type of tenant that you have. Therefore, if you must make more requests to the API, you may need to consider a subscription with us.
I hope this answers your questions about rate limits. Please let me know if you have any questions. I would be happy to help.