> 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/shopware/shopware6_en_us/configuration/test-connection-and-diagnostics.md).

# Test Connection & Diagnostics

Before you synchronize data, the connection to the Shopware Admin API should be working flawlessly. This page shows you how to check the connection and narrow down errors.

### **Testing the Connection**

Two helpful actions are available in the **Shopware Configuration**:

* **Test Connection** – retrieves a fresh token from Shopware. If a success message appears, the URL, path, and credentials are correct.
* **Show Password** – displays the stored credentials so that you can check them.

{% stepper %}
{% step %}
**Check the credentials**

Make sure that the **Website URL** (for example `https://shop.example.com`) and the **API Module Path** (usually `/api`) are correct. A trailing slash is removed automatically.
{% endstep %}

{% step %}
**Run the test**

Click **Test Connection**. The connector requests a token at `…/oauth/token`.
{% endstep %}

{% step %}
**Evaluate the result**

If the test succeeds, a confirmation appears. If it fails, check the causes listed below and enable the **Developer Log** if necessary.
{% endstep %}
{% endstepper %}

### **Common Causes of Connection Errors**

| Symptom                             | Possible cause                          | Solution                                                  |
| ----------------------------------- | --------------------------------------- | --------------------------------------------------------- |
| "UserName or Password is incorrect" | Incorrect credentials / wrong auth mode | Check the credentials and the *Integration Access* toggle |
| No token / empty response           | URL or API path incorrect               | Correct the Website URL and API Module Path               |
| Timeout                             | Shop not reachable / firewall           | Check reachability and the outbound HTTPS connection      |
| Certificate error                   | Invalid TLS certificate                 | Install a valid certificate in the shop                   |

{% hint style="info" %}
For troubleshooting, temporarily enable **Enable Developer Log**. You will then see the exact request URL and the server response in the API Call Log.
{% endhint %}

**Checklist**

<details>

<summary><strong>Connection failing? What to check</strong></summary>

1. Is **Enable** set in the configuration?
2. Are the **Website URL** and **API Module Path** correct?
3. Does the **authentication mode** match your credentials? See [Authentication Methods in Detail](/shopware/shopware6_en_us/configuration/authentication-methods-in-detail.md).
4. Is the Shopware Admin API reachable from outside?
5. Does the **Developer Log** show a specific error message?

</details>


---

# 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.solutioo.de/shopware/shopware6_en_us/configuration/test-connection-and-diagnostics.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.