> For the complete documentation index, see [llms.txt](https://developers.shopbase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.shopbase.com/build-an-app/getting-your-app-approved/submitting-your-app.md).

# Submitting your app

After you’ve tested your app and ensured that it's production-ready, you can submit it for approval.

{% hint style="warning" %}
Make sure you thoroughly [test your app](/build-an-app/getting-your-app-approved/testing-your-app.md) before submitting it. If we discover a bug that prevents us from being able to review the functionality of your app, then it will be rejected.
{% endhint %}

Before you submit your app, check the following things:

* Make sure that the app meets our [requirements](/build-an-app/getting-your-app-approved/app-requirements.md). This helps to speed up your app’s review.
* Make sure that your app is appropriately documented, keeping in mind that many of your users might not be digitally literate. Try to create a guide that caters to all levels of experience. If your app requires the setup of an external service to function, then include this within your documentation.


---

# 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://developers.shopbase.com/build-an-app/getting-your-app-approved/submitting-your-app.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.