---
title: "Get the current shopper"
method: GET
path: "/v1/shoppers/me"
tags: ["Shoppers"]
---

# Get the current shopper

`GET /v1/shoppers/me`

Get the current shopper and shopper data.
You can get shopper information for both anonymous and authenticated shoppers.

## Query parameters

- `token` string
- `ipAddress` string
- `expand` string
- `fields` string

## Response `200`

Successful response.

- union
  - DefaultShopper
    - `shopper` object
      - `uri` string — The Uniform Resource Identifier.
      - `id` integer — The unique identifier for the shopper.
      - `username` string — The shopper's user name.
      - `firstName` string — The shopper's first name.
      - `lastName` string — The shopper's last name.
      - `emailAddress` string — The shopper's email address.
      - `paymentOptions` object — The saved payment options.
        - `uri` string
      - `addresses` object — The saved addresses.
        - `uri` string
      - `orders` object — The shopper's orders.
        - `uri` string
      - `subscriptions` object — The shopper's subscriptions.
        - `uri` string
  - ExpandedShopper
    - `shopper` object
      - `uri` string — The Uniform Resource Identifier.
      - `id` integer — The unique identifier for the shopper.
      - `username` string — The shopper's user name.
      - `externalReferenceId` string — The external reference identifier.
      - `firstName` string — The shopper's first name.
      - `lastName` string — The shopper's last name.
      - `emailAddress` string — The shopper's email address.
      - `locale` string — The shopper's preferred locale.
      - `currency` string — The shopper's preferred currency.
      - `sendMail` boolean — This API has two fields in its request/response body: "sendMail" and "sendEmail". Both fields indicate whether shoppers opt-in to promotional emails using True/False values. - If customers have a single type of promotional email, select either "sendMail" or "sendEmail" to record shopper preferences. - If customers have two distinct types of promotional emails, use both fields to differentiate between them. For example, "sendMail" could indicate interest in product updates, while "sendEmail" could indicate interest in sales and discounts. Please note that Digital River does not send promotional emails. These fields only track shopper preferences and do not affect Digital River’s system notifications.
      - `sendEMail` boolean — Similar to sendMail, this API has two fields in its request/response body: "sendMail" and "sendEmail". Both fields indicate whether shoppers opt-in to promotional emails using True/False values. - If customers have a single type of promotional email, select either "sendMail" or "sendEmail" to record shopper preferences. - If customers have two distinct types of promotional emails, use both fields to differentiate between them. For example, "sendMail" could indicate interest in product updates, while "sendEmail" could indicate interest in sales and discounts. Please note that Digital River does not send promotional emails. These fields only track shopper preferences and do not affect Digital River’s system notifications. Please distinguish this field from the sendEmail field in the v1/shoppers/me/carts API.
      - `ipAddress` string — The shopper's IP address. IPv4 or IPv6.
      - `paymentOptions` object — The saved payment options.
        - `uri` string
      - `addresses` object — The saved addresses.
        - `uri` string
      - `orders` object — The shopper's orders.
        - `uri` string
      - `subscriptions` object — The shopper's subscriptions.
        - `uri` string

## Other responses

- `401` — * Invalid Token
- `409` — * Restricted IP address

---

[API](https://skmtc.net/digitalriver/apis/commerce-api-suite-shopper-apis.md) · [All operations](https://skmtc.net/digitalriver/apis/commerce-api-suite-shopper-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/digitalriver/commerce-api-suite-shopper-apis/revisions/4b69392f93b9/schema)