> 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-occupancy availability blocks](/connector-api/concepts/multi-occupancy-availability-blocks.md)\
  An explanation of how availability blocks split their allocated units by guest count.
* [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 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/concepts.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.