create customer api route

[didinadir1]

What Medusa version and documentation are you using?

v2

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/medusajs/medusa/issues

Issue Summary

in the documentation that treats the registration of customers the create api route is often referenced. but it seems that it no longer exists and when clicking on the link for the related documentation it redirects to the register api route.
it seems that this api route is essential to the process of creating a customer when the same email is already used for another identity and the register route can't be used for this purpose , i quote :

However, a customer may enter an email that's already used either by an admin user, another customer, or a custom actor type. To handle this scenario:

Try to obtain a login token by sending a POST request to the /auth/customer/emailpass Authenticate Customer API route. The customer is only allowed to register if their email and password match the existing identity. This allows admin users to log in or register as customers.
If you obtained the login token successfully, create the customer using the login JWT token instead of the registration token. This will not remove the existing identity. So, for example, an admin user can also become a customer.

and :

... Send a request to the Create Customer API route to create the customer in Medusa.

does this api route still exits ? is there a way to achieve the creation of a customer despite the email being used for another identity ?
tnx

[shahednasser]

Hi @didinadir1 , thank you for reporting this issue. There seems to be a misunderstanding here. The document refers to the API route as "Create Customer API route", but it's essentially the register API route. I think we need to align the terms to avoid a similar confusion.

is there a way to achieve the creation of a customer despite the email being used for another identity ?

Can you clarify what you mean exactly here? What use case are you trying to implement?

[didinadir1]

Hello @shahednasser, tnx for your reply !

What use case are you trying to implement?

Let's say i want a customer to be a seller (custom actor type) at the same time. So i want him to be able to use the same email for login.

What to you think ? is it possible right now ? how would you implement it ?

[shahednasser]

As mentioned in the guide, when the registration fails because the customer already exists as another identity (such as an admin user, or a seller), you can simply log them in instead of creating the customer. Refer to this part in the guide:

Try to obtain a login token by sending a POST request to the /auth/customer/emailpass Authenticate Customer API route. The customer is only allowed to register if their email and password match the existing identity. This allows admin users to log in or register as customers.

Does this answer your question?

[didinadir1]

So if i understand correctly, what you're saying is that if a seller already exists as another identity (let's say customer). i don't need to create a new seller ? I just have to log them to access the seller endpoints ? what about the actor_id being cus_**** intead of sel_**** and the seller_id not defined in the token ? (example of decoded token in the image below)

[shahednasser]

The identity will be associated with both. So, app_metadata will have seller_id and customer_id, for example.