> For the complete documentation index, see [llms.txt](https://docs.mews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mews.com/loyalty-partner/workflows/list-memberships.md).

# List memberships

**Mews Operations** uses the [List memberships operation](https://docs.mews.com/loyalty-partner/api-operations/memberships.md#post-memberships-list) to retrieve current membership data for one or more customers using their `providerMembershipId` values. This operation is used in both manual and automated workflows to keep loyalty data up to date in Mews.

## Manual membership sync

Front desk staff click **Refresh** on a customer profile that is already linked to a membership in the partner system. Mews fetches the latest membership data from the partner system.

<figure><img src="https://3946584615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXX5WlJYsdpRtizxNDPz%2Fuploads%2Fgit-blob-36622b93a69b8a864d3f26c18cd42ca0be964789%2Fmanual-membership-sync.png?alt=media" alt="Screenshot of a Mews customer profile with a Refresh button to manually sync membership data from the partner system." width="563"><figcaption><p>Manual membership sync in Mews: front desk staff use the Refresh button on the customer profile to update membership details from the partner system.</p></figcaption></figure>

## Automatic membership sync

Once a day, an automated job identifies customers arriving the next day and fetches the latest membership data for each of them from the partner system.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mews.com/loyalty-partner/workflows/list-memberships.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
