# Request app review

Once you make sure that your app meets Make's [requirements](/custom-apps-documentation/app-review/prerequisites.md) and follows Make's [best practices](https://github.com/integromat/make-apps-sdk-docs/blob/master/app-review/broken-reference/README.md), you can request an app review:

## Request a review

To request an app review:

{% stepper %}
{% step %}
Remove the test modules or test connections before you publish an app. When your app is public, you can't delete its modules, connections, or other components.
{% endstep %}

{% step %}
Navigate to your custom app's code and click the **Publish** button.

<div align="left"><figure><img src="/files/vaX8F2939owbG4m3HF3Q" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
Once you publish your app, you can't unpublish it. See the [app visibility section](/custom-apps-documentation/create-your-first-app/app-visibility.md) for more details.
{% endhint %}
{% endstep %}

{% step %}
In the **Modules** tab, click the switch to set the visible status of each module in the app that you want to publish.

<div align="left"><figure><img src="/files/o6rWpY6U7kKVGEk5wVuY" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
You will see a new **Review** tab in the top panel.

<div align="left"><figure><img src="/files/XZwhfDfhpktpVvNSQMe2" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Complete the form on the **Review** page.

* Add a link to the API documentation of the service for which you are creating a custom app.
* Add a link to scenarios with the custom app modules. Check the testing scenarios section in the [App review prerequisites](/custom-apps-documentation/app-review/prerequisites.md).
  {% endstep %}

{% step %}
Click the **Request review** button at the bottom of the page.
{% endstep %}
{% endstepper %}

The data you submit is sent to Make QA developers for review. At the top of the page, the **Request review** button changes to **Review process started** and becomes inactive. Also, the app status changes to **pending approval**.

<figure><img src="/files/ehNRlLI4Mwyk2LB2baAh" alt="" width="563"><figcaption></figcaption></figure>

Once you request the app review, Make sends you an email with the subject: "*App review: YourApp'sName*". If you have any questions or additional information to share, reply to the email.

Each time you update your app based on reviewer feedback, run your scenarios to generate new logs.

If you need to edit your links, you can update your form and submit the changes by clicking the **Update review** button

## Review process

The review process contains three phases: form submission, automatic review, and manual review.

### Form submission

Once you hit the **Request Review** button, you will receive an e-mail containing a link to our form where you will be prompted to share the following information about you and your app:&#x20;

* **Developer information** - What is your relationship with the vendor of the API service?
* **Partnership contact** - Applicable for ISV. The details of a contact person or team on your end responsible for partnership-related discussions.
* **Support contact** - Details of the contact person or team that should be contacted in case of any app issues reported by users.
* **Categories and subcategories of your app** - The categories and subcategories in which you wish to have the app listed on the [make.com integrations page](https://make.com/en/integrations).
* **Logo of your company** - Applicable for ISV. The logo should appear on the app's landing page on make.com.
* **URL to the service** - The URL leading to your website that should appear on the app's landing page on make.com.
* **Trademark compliance** - Confirm that you have obtained all necessary written licenses for any trademarks, service marks, or brand names used in your app and that you understand that unauthorized use of third-party intellectual property is grounds for immediate rejection or removal without prior notice.
* **External Service T\&C compliance** - Confirm that the app and its data-handling practices comply with any applicable terms and conditions and API policies of all integrated third-party components of the app. Also, confirm that you agree to indemnify and hold Make harmless for any claims, damages, or legal fees arising from your breach of this form or any third-party terms applicable to the app. Make reserves the right to audit or disable any app reported for violation of any terms and conditions applicable to it.

Upon completing the form, you will receive feedback from the automatic review.

### Automatic review (beta)

Your app is first reviewed by our application. The automatic review checks for common issues and generates a PDF file with the issues found.

The PDF file with feedback from the automatic review is sent to the existing app review email thread.

{% hint style="info" %}
The automatic review is in beta and is still in the process of improvement. Therefore, there might be inconsistencies.
{% endhint %}

### Manual review

Once your app passes the automatic review, it is reviewed by our QA engineer who makes sure that your app follows our best practices and is user-friendly.

The QA engineer shares the feedback in the existing app review email thread.

Once your app successfully passes the manual review, your app is listed in our planned release. You will be informed about the app approval as well as the app release.


---

# Agent Instructions: 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:

```
GET https://developers.make.com/custom-apps-documentation/app-review/request-app-review.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
