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

# Usage guidelines

This section provides important guidelines on how to use the **Mews Connector API**. For a deeper understanding of Mews concepts, see [Concepts](/connector-api/concepts.md). For information about individual endpoints or operations, see [API Operations](/connector-api/operations.md).

{% hint style="info" %}

#### Terminology

Some of the terms used in the API, such as *enterprise*, *customer* or *resource* may not be familiar. For example, we use *resource* to describe guest rooms and other types of bookable space. For a full description of all the terms used, see the [Mews Glossary for Open API users](/getting-started/glossary.md).
{% endhint %}

## Contents

* [Authentication](/connector-api/guidelines/authentication.md)\
  Details of how API Operation requests are authenticated.
* [Requests](/connector-api/guidelines/requests.md)\
  Details of how to make API Operation requests.
* [Responses](/connector-api/guidelines/responses.md)\
  Details of API Operation responses, including error messages.
* [Environments](/connector-api/guidelines/environments.md)\
  A description of the different environments available and how to access them, including test credentials, request limits and more.
* [Serialization](/connector-api/guidelines/serialization.md)\
  Various topics related to data formats.
* [Pagination](/connector-api/guidelines/pagination.md)\
  An explanation of the pagination feature and how to use it to fetch data.
* [Best practices](/connector-api/guidelines/best-practices.md)\
  Advice on best practices for using the API.


---

# 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/connector-api/guidelines.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.