> 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/your-journey/private-integration.md).
# Private integration journey
Please follow the below steps if you are a property building your own integration or a company working on behalf of a customer to build a connection with **Mews Connector API**. A private integration means your integration will not be listed in the Mews Marketplace.
## Certification instructions
1. Review the guidelines, demo credentials, best practices, use cases, and endpoints found in [Connector API](/connector-api/readme.md) documentation.
2. Fill in the [Become a Mews Partner Form](https://www.mews.com/en/partners/new-partnerships) and get your Partner Id if you have not done so already.
3. Complete our [Private Integrations Certification Form](https://mews.typeform.com/to/xKbTQfDC?typeform-source=mews.atlassian.net).
4. Test all the endpoints you are listing on the form in demo. [Request a dedicated Demo Property](/connector-api/guidelines/environments.md#mews-operations-credentials) to get access.
5. Make sure you are specifying the `Client` parameter in your [API request body](/connector-api/guidelines/requests.md#body). Note that if you do not specify a **unique** Client name in your demo API calls, we cannot review the API activity and therefore approve the certification.
6. Once you've generated the API activity, [book a review with us](https://outlook.office.com/book/MewsMarketplace1@mewssystems.com/s/7N13ca0m6U26AMjM1h8p6w2?ismsaljsauthenabled) in our calendar. *Please note this is not a meeting but rather a placeholder for us to review your solution*.
## Receiving tokens
Once the integration profile is created in the production environment, you will receive an email with your `ClientToken` and `AccessToken`.
## Questions
[Contact support](/connector-api/contact-support.md) if you have any questions or would like to schedule a meeting with one of our private integrations team members. Please include a quick summary about the integration you are building and the property(ies) it is for.
## FAQs
We need access to more endpoints than we originally thought, how do we go about getting access to additional permissions post certification?
Please make the necessary tests in demo and then [contact support](/connector-api/contact-support.md) letting us know which you need enabled.
Our integration is currently private but we would now like to be listed in the Mews Marketplace. Can we modify this and if so how?
[Contact support](/connector-api/contact-support.md) letting us know you would like to go public and let us know of any changes to your integration profile (description, images…).
I am confused by the wording in Mews, is there a cheat sheet for what certain words mean in the system?
Yes, please see [Mews Glossary for Open API users](/getting-started/glossary.md).
What is required by a property to have a private integration?
A property must have the Connectivty Add-on as part of their subscription or be on the Enterprise package. They can verify their current subscription by contacting their Client Success Manager.
Can a partner configure multiple webhook endpoints per integration?
No — there can only be one Webhook URL per integration client; partners should route by Enterprise ID inside their handler.
How long do integrations take to go live?
This is entirely up to you! Once all endpoints are tested and a certification time is booked, the team can have you live within 24 hours of that certification if there are no issues.
---
# 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/your-journey/private-integration.md?ask=&goal=
```
`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.