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

# Mews Connector API

General-purpose API that enables partners of Mews to access data and services in Mews Operations.

Welcome to the **Mews Connector API**! This is a general-purpose API that enables partners of Mews to access data and services in **Mews Operations**.

To make a quick start and get a feel for the API, see [Getting started](/connector-api/getting-started.md). For a full guide on how to connect, what authentication tokens you need, the meaning of error codes and much more, see our [Usage guidelines](/connector-api/guidelines.md). To gain deeper insights into Mews concepts, see [Concepts](/connector-api/concepts.md). For guidance on using the API for specific scenarios, our [Use cases](/connector-api/use-cases.md) section will help you through your implementation. Detailed information on all API operations can be found in [API Operations](/connector-api/operations.md), and information on event mechanisms like Webhooks in [API Events](/connector-api/events.md).

If you have any questions or you encounter issues, please [contact support](/connector-api/contact-support.md).

#### Changes to this API

* For the history of changes to the API, see the [Changelog](/connector-api/changelog.md).
* For important information on deprecations, see [Deprecations](/connector-api/deprecations.md).
* To track changes and updates, you can follow the [GitHub repository](https://github.com/MewsSystems/open-api-docs).

{% hint style="info" %}

#### OpenAPI definition

We maintain an [OpenAPI definition](https://api.mews.com/Swagger/connector/swagger.yaml) (formerly Swagger) for the **Mews Connector API**. You can use this to build out client applications using third party tools.
{% 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 dynamically 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/readme.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 `build a script that syncs our docs to a CMS` 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.