(ctx: RequestContext, options: ListQueryOptions<Customer> | undefined, relations: RelationPaths<Customer> = []) => Promise<PaginatedList<Customer>>(ctx: RequestContext, id: ID, relations: RelationPaths<Customer> = []) => Promise<Customer | undefined>(ctx: RequestContext, userId: ID, filterOnChannel: = true) => Promise<Customer | undefined>Returns the Customer entity associated with the given userId, if one exists.
Setting filterOnChannel to true will limit the results to Customers which are assigned
to the current active Channel only.
(ctx: RequestContext, customerId: ID) => Promise<Address[]>Returns all Address entities associated with the specified Customer.
(ctx: RequestContext, customerId: ID) => Promise<CustomerGroup[]>Returns a list of all CustomerGroup entities.
(ctx: RequestContext, input: CreateCustomerInput, password?: string) => Promise<ErrorResultUnion<CreateCustomerResult, Customer>>Creates a new Customer, including creation of a new User with the special customer Role.
If the password argument is specified, the Customer will be immediately verified. If not,
then an AccountRegistrationEvent is published, so that the customer can have their
email address verified and set their password in a later step using the verifyCustomerEmailAddress()
method.
This method is intended to be used in admin-created Customer flows.
(ctx: RequestContext, input: UpdateCustomerShopInput & { id: ID }) => Promise<Customer>(ctx: RequestContext, input: UpdateCustomerInput) => Promise<ErrorResultUnion<UpdateCustomerResult, Customer>>(ctx: RequestContext, input: UpdateCustomerInput | (UpdateCustomerShopInput & { id: ID })) => Promise<ErrorResultUnion<UpdateCustomerResult, Customer>>(ctx: RequestContext, input: RegisterCustomerInput) => Promise<RegisterCustomerAccountResult | EmailAddressConflictError | PasswordValidationError>Registers a new Customer account with the NativeAuthenticationStrategy and starts
the email verification flow (unless AuthOptions requireVerification is set to false)
by publishing an AccountRegistrationEvent.
If an account with the given email address already exists via another authentication method
(for example an external/SSO strategy) and has no native credential yet, a native credential is
added in an unactivated state (no password) and an AccountRegistrationEvent is always
published, even when requireVerification is false. The password can then only be set by
whoever controls the email address, by completing the verification flow. This prevents an
unauthenticated caller from taking over such an account by registering a password against it.
This method is intended to be used in storefront Customer-creation flows.
(ctx: RequestContext, emailAddress: string) => Promise<void>Refreshes a stale email address verification token by generating a new one and publishing a AccountRegistrationEvent.
(ctx: RequestContext, verificationToken: string, password?: string) => Promise<ErrorResultUnion<VerifyCustomerAccountShopResult, Customer>>Given a valid verification token which has been published in an AccountRegistrationEvent, this
method is used to set the Customer as verified as part of the account registration flow.
(ctx: RequestContext, customerId: ID, password?: string) => Promise<ErrorResultUnion<VerifyCustomerAccountAdminResult, Customer>>v3.8.0Manually marks a Customer's email address as verified, for use by an administrator when the
customer has not received or cannot complete the verification email. See
UserService.verifyUserWithoutToken for the rules the password argument follows.
A Customer with no User (a guest checkout) has no account to verify, and is rejected.
(ctx: RequestContext, emailAddress: string) => Promise<void>Publishes a new PasswordResetEvent for the given email address. This event creates
a token which can be used in the resetPassword() method.
(ctx: RequestContext, passwordResetToken: string, password: string) => Promise< User | PasswordResetTokenExpiredError | PasswordResetTokenInvalidError | PasswordValidationError >Given a valid password reset token created by a call to the requestPasswordReset() method,
this method will change the Customer's password to that given as the password argument.
(ctx: RequestContext, userId: ID, newEmailAddress: string) => Promise<boolean | EmailAddressConflictError>Publishes a IdentifierChangeRequestEvent for the given User. This event contains a token
which is then used in the updateEmailAddress() method to change the email address of the User &
Customer.
(ctx: RequestContext, token: string) => Promise<boolean | IdentifierChangeTokenInvalidError | IdentifierChangeTokenExpiredError>Given a valid email update token published in a IdentifierChangeRequestEvent, this method will update the Customer & User email address.
(ctx: RequestContext, input: Partial<CreateCustomerInput> & { emailAddress: string }, errorOnExistingUser: boolean = false) => Promise<Customer | EmailAddressConflictError>For guest checkouts, we assume that a matching email address is the same customer.
(ctx: RequestContext, customerId: ID, input: CreateAddressInput) => Promise<Address>Creates a new Address for the given Customer.
(ctx: RequestContext, input: UpdateAddressInput) => Promise<Address>(ctx: RequestContext, id: ID) => Promise<boolean>(ctx: RequestContext, customerId: ID) => Promise<DeletionResponse>(ctx: RequestContext, order: Order) => If the Customer associated with the given Order does not yet have any Addresses, this method will create new Address(es) based on the Order's shipping & billing addresses.
(ctx: RequestContext, input: AddNoteToCustomerInput) => Promise<Customer>(ctx: RequestContext, input: UpdateCustomerNoteInput) => Promise<HistoryEntry>(ctx: RequestContext, id: ID) => Promise<DeletionResponse>Architecture reviews, custom plugin work, migrations, ongoing support. Get a hand from the team that builds Vendure.
Talk to the team