Authentication API signup doesn't require client_id actually

Hello, auth0 community.

So yeah, as the title states Authentication API signup doesn’t require client_id actually despite the docs tell the opposite - Authentication API Explorer.

Here’s how i found this out accidentally:

Or probably i’m missing something? Could you plz guide me. Otherwise - fix the docs or add some info when it’s not required.


If you look at the associations, a client application is authorized to use one or more connections, and users are created associated with a connection. So yes, it is possible to create a user without an associated client application. This is actually useful in scenarios where you may want to bulk import users prior to moving applications into Auth0, as they would first need to be created in associated with the connection of the Auth0 datastore, before being assigned to specific client applications that would be created and registered after and given access to these connections containing the users. The benefit of including the clientId in the context of creating a specific user for an application, is that for example in a signup of a new user to your website, by including the clientId you are also ensuring that you have created the user in the correct connection which has the required access to the target client application.

1 Like

Thanks for helping on this one Nissan!

Thanks for reply, Nissan - extremely useful.

Still the docs are misleading as they claim client_id as required, but actually it’s optional.

Will relay that feedback to the docs team!

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.