> 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/contact-support.md). # Contact support Partner Success team is ready to help you with any questions about API behavior, clarification of documentation, technical troubleshooting, and general guidance on integrations. ## Technical issues If you are experiencing a problem with the API, we recommend first reviewing the following resources, as many common issues can be resolved there: * [Best practices](/connector-api/guidelines/best-practices.md) * [Response troubleshooting](/connector-api/guidelines/responses.md) To help us investigate and respond as quickly as possible, please include the following details when reporting an issue: * Full API response body including the `RequestId` property in the [Error response details](/connector-api/guidelines/responses.md#error-response-details). * The request body you are sending and the response you are receiving, provided in JSON format, with `ClientToken` and `AccessToken` values redacted (e.g. replaced with empty string or leaving just a few characters). Avoid sending screenshots or document files (for example Word or PDF files). * Do not send full `ClientToken`, `AccessToken`, or any other sensitive information (e.g. guests' personal data in request payload). Partner success will never ask for this information. ## Contact Contact the Partner Success team at . --- # 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/contact-support.md?ask=&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.