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

# Authentication

Mews authenticates all requests to your API using bearer token authentication.

### Token scope

A single token covers the entire integration. All requests from Mews to your API use the same token regardless of which property initiates the action. You can distinguish the scope of operation using either `mewsEnterpriseId` or `providerEnterpriseId` properties provided in the request payload.

### Token generation

You are responsible for generating the token and providing it to Mews. Mews stores the token and includes it in all subsequent requests.

### Token lifecycle

Tokens are long-lived, valid for one year under the current agreement. Token rotation is manual: when a token approaches expiration, you generate a new token and provide it to Mews.

During rotation, your API must accept both the current token and the new token simultaneously to avoid service interruptions.

### Example request

```http
POST /members/search HTTP/1.1
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Content-Length: 180

{
  "mewsEnterpriseId": "123e4567-e89b-12d3-a456-426614174000",
  "providerEnterpriseId": "ENT-9876-AZ",
  "memberFilter": {
    "email": "john.doe@example.com",
    "firstName": "John",
    "lastName": "Doe"
  }
}
```

{% hint style="info" %}
Future versions may support automatic token renewal or shorter token lifespans for improved security.
{% 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 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/guidelines/authentication.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.
