---
title: "List Member Activity"
method: GET
path: "/v1/loyalties/members/{memberId}/activity"
tags: ["Loyalties"]
---

# List Member Activity

`GET /v1/loyalties/members/{memberId}/activity`

> 📘 Alternative endpoint
> This endpoint is an alternative to this [endpoint](/api-reference/loyalties/list-member-activity-with-campaign-id). The URL was re-designed to allow you to get member activities without having to provide the `campaignId` as a path parameter.

Retrieves the list of activities for the given member ID related to a voucher and customer who is the holder of the voucher.

## Query parameters

- `limit` integer
- `order` 'created_at' | '-created_at'
- `starting_after_id` string

## Response `200`

Returns a list of event objects related to the loyalty card.

- LoyaltiesMemberActivityListResponseBody — Response body schema for retrieving member activity.
  - `object` 'list', required — The type of the object represented by JSON. This object stores information about member activities in a dictionary.
  - `data_ref` string, required — Identifies the name of the attribute that contains the array of member activity objects.
  - `data` MemberActivity[], required — Array of member activity objects.
    - `id` string, required — Unique activity ID.
    - `member_id` string, required — ID of the member the activity relates to.
    - `type` 'vl.member.created' | 'vl.member.deleted' | 'vl.member.activated' | 'vl.member.deactivated' | 'vl.member.card.assigned' | 'vl.member.card.unassigned', required — Activity type.
    - `data` object, required — Activity payload - snapshots of the objects involved at the time of the activity (e.g. `member` and `program` objects for member lifecycle activities).
    - `created_at` string, date-time, required — Timestamp when the activity was recorded (ISO 8601).
    - `group_id` string — ID grouping activities recorded within the same request.
    - `source` MemberActivitySource — Origin of an activity.
      - `channel` 'USER_PORTAL' | 'API' | 'CLIENT_API' | 'INTERNAL' — Channel through which the activity was triggered.
      - `user` object — The dashboard user who triggered the activity. Omitted when not applicable.
        - `id` string — User ID.
      - `api_key` object — The API key used to trigger the activity. Omitted when not applicable.
        - `name` string — API key name.
        - `app_id` string — Application ID of the API key.
        - `client_app_id` string — Client application ID of the API key.
  - `has_more` boolean, required — As query results are always limited (by the limit parameter), the `has_more` flag indicates if there are more records for given filter parameters. This lets you know if you can run another request with a `starting_after_id` query or a different limit to get more records returned in the results.
  - `more_starting_after` string — Returns an ID that can be used to return another page of results. Use the event ID in the `starting_after_id` query parameter to display another page of the results starting after the event with that ID.

## Other responses

- `404` — Returns an error if the member ID could not be found.

---

[API](https://skmtc.net/voucherifyio/apis/voucherify-api-async-actions.md) · [All operations](https://skmtc.net/voucherifyio/apis/voucherify-api-async-actions/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/voucherifyio/voucherify-api-async-actions/versions/4982266e0494/schema)