Customers must contain an email address and, optionally, a password. Registered customers can get an access token through the Password Flow to manage their data. Customer status can be one of "prospect," (with no orders) "acquired," (with one order), or "repeat" (with two or more orders). Customers can be associated with groups to get access to the related private markets (learn more).
A customer object is returned as part of the response body of each successful create, list, retrieve, or update API call.
The customer unique identifier
The customer endpoint URL
The customer's email address
The customer's password. Initiate a customer password reset flow if you need to change it.
The customer's status, one of 'prospect', 'acquired', or 'repeat'.
Indicates if the customer has a password.
Time at which the resource was created.
Time at which the resource was last updated.
A string that you can use to add any external identifier to the resource. This can be useful for integrating the resource to an external system, like an ERP, a marketing tool, a CRM, or whatever.
Any identifier of the third party system that defines the reference code
Set of key-value pairs that you can attach to the resource. This can be useful for storing additional information about the resource in a structured format.
The group to which this customer belongs (optional).
The customer's saved addresses, i.e. their address book.
The customer's saved creadit cards, i.e. their wallet.
The customer's subscriptions.
The customer's orders, either pending or placed.
The customer's returns, either pending or shipped.
The resource environment (can be one of