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

# Concepts

This section delves into domain-specific topics related to the Mews system. An understanding of these will help you to make the most effective use of the API.

{% 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

* [Multi-property](/connector-api/concepts/multi-property.md)\
  An explanation of multi-property operation with Portfolio Access Tokens.
* [Restrictions](/connector-api/concepts/restrictions.md)\
  An explanation of the algorithms used to support setting and clearing restrictions.
* [Taxation](/connector-api/concepts/taxation.md)\
  An explanation of the different tax environments and how they impact your integration.
* [Time units](/connector-api/concepts/time-units.md)\
  A detailed explanation of the time units used to describe service reservations.


---

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