> 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](/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.
Screenshot of a Mews customer profile with a Refresh button to manually sync membership data from the partner system.

Manual membership sync in Mews: front desk staff use the Refresh button on the customer profile to update membership details from the partner system.

## 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mews.com/loyalty-partner/workflows/list-memberships.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.