Get details of the user including the wallet balance, tier, membership and referral code. Look up by lead id in the path. To look up by customer_id, referral_code, email or mobile instead, pass any placeholder uuidv4 in the path (the path id is always required to keep the API strict) and pass the lookup key in the query, the query value takes precedence. email and mobile are masked in the response. When looked up by email, mobile or referral_code with a read only api key, the response omits id, customer_id, wallet_id and creditwallet_id so that a visitor cannot discover another customer's ids, use customer_id or the path id (or a write api key) to get them. When called with a storefront read only api key and x-leaddigest, the response also carries lead_token, a 1 hour token identifying this customer, which every customer scoped API accepts in the x-leadtoken header so the customer id never has to be trusted from the browser. Refer to this article for the authentication flow when calling this API from a storefront or client side environment.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
