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

# Usage guidelines

This section provides important guidelines on how to use the **Mews Channel Manager API**. Unless specified otherwise, the guidelines apply to both the Mews side of the API and the Channel Manager side of the API. For information on the partner journey and on the certification process, see [Your integration journey](/channel-manager-api/your-journey.md). For information about individual endpoints or operations, see [API Operations (Mews)](/channel-manager-api/mews-operations.md) and [API Operations (CHM)](/channel-manager-api/channel-manager-operations.md).

> #### Terminology
>
> We use the term *Property* to describe the hotel, hostel or other enterprise; we use the term *Space* to refer to a hotel room, dormitory bed or other type of bookable space, and *Space Type* to refer to the category of *Space* offered by the *Property*. Although typically a room in a hotel, this could be for example a squash court in a sports facility. For a full description of all the terms used in the API, see the [Mews Glossary for Open API users](/getting-started/glossary.md).

## Contents

* [Authentication](/channel-manager-api/guidelines/authentication.md)\
  Details of how API Operation requests are authenticated.
* [Requests](/channel-manager-api/guidelines/requests.md)\
  Details of how to make API Operation requests.
* [Responses](/channel-manager-api/guidelines/responses.md)\
  Details of API Operation responses, including error messages.
* [Environments](/channel-manager-api/guidelines/environments.md)\
  A description of the different environments available and how to access them.
* [Compliance](/channel-manager-api/guidelines/compliance.md)\
  Information about PCI compliance.


---

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