> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/magento-2-api-connector/magento2_en_us/getting-started/prerequisites.md).

# Prerequisites

Verify technical and business prerequisites before installation.

### Business Central

* Compatible BC version, documented 27.0.0.0
* App version 27.10.0.16
* Permission set **SouPermissionSet**
* Number series for sales documents
* Customer and Item templates
* Locations for MSI sources
* Verified tax Posting Groups and posting matrix
* G/L account for shipping charges

### Magento 2

* Reachable HTTPS REST API
* API path, usually `/rest/all/V1`
* Technical user with required read/write permissions
* Websites, Store Views, and Attribute Sets
* Payment, shipping, and tax configuration
* For inventory: MSI sources

{% hint style="danger" %}
Use a dedicated technical account with minimum required permissions.
{% endhint %}

### Network and Security

* Valid TLS certificate
* Outbound connectivity
* No blocking by firewall/WAF
* Credentials only in masked fields

### Business Preparation

Define data ownership, shops/languages, customer handling, mappings, tax/credit memo processes, and acceptance tests.


---

# 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.solutioo.de/magento-2-api-connector/magento2_en_us/getting-started/prerequisites.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 `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.
