> 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/readme.md).

# Loyalty Partner API

The **Mews Loyalty Partner API** enables loyalty program providers to integrate their membership systems with Mews. Once connected, **Mews Operations** users (like front desk staff) can view and manage customer loyalty memberships directly within the Mews guest profile.

<figure><img src="/files/rKAmzeboR1j8m23aC4RS" alt="Screenshot of Mews Operations UI showing a guest profile with Loyalty section showing membership in Choice Privileges with membership number, points, tier, and expiration date." width="563"><figcaption><p>Guest profile in Mews Operations with loyalty membership connected</p></figcaption></figure>

### Reverse API model

This integration uses a reverse API pattern: Mews calls your system, not the other way around. You implement a set of operations defined by a Mews-provided OpenAPI specification. Once deployed, Mews calls your API when **Mews Operations** users perform loyalty-related actions.

The integration works as follows:

1. Mews provides an OpenAPI specification describing the operations you must implement.
2. You implement those operations on your system.
3. Mews calls your API when a **Mews Operations** user performs a loyalty action, for example enrolling a customer.

### Changes to this API

See the [Changelog](/loyalty-partner/changelog.md) for notable updates, deprecations, and breaking changes.

{% hint style="warning" %}
The OpenAPI specification is the authoritative source for implementation details. This documentation provides context and examples, but the spec takes precedence.
{% endhint %}


---

# 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/readme.md?ask=<question>&goal=<endgoal>
```

`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.
