> 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/monitoring-and-logs/analyze-api-responses.md).

# Analyze API Responses

When a synchronization fails, Shopware usually returns a specific indication in the response. Here is how to interpret the most common cases.

**Typical response patterns**

| Response          | Meaning                                 | Action                                                      |
| ----------------- | --------------------------------------- | ----------------------------------------------------------- |
| 401 / token error | Sign-in failed                          | Check the credentials & authentication mode                 |
| 400 / validation  | Mandatory field missing / invalid value | Check the field contents in BC (for example, tax, category) |
| 404               | Object not found                        | Check the Web-ID/mapping, create it again if necessary      |
| 409 / duplicate   | Record already exists                   | Check the matching/Web-ID                                   |

**Procedure**

{% stepper %}
{% step %}
**Find the entry**

Open the relevant entry in the [API Call Log](https://docs.solutioo.de/shopware/shopware6_en_us/monitoring-and-logs/api-call-log.md).
{% endstep %}

{% step %}
**Read the response**

Look for `errors` or `detail` in the response – this is where the specific cause is stated.
{% endstep %}

{% step %}
**Fix the cause**

Correct the value in BC (for example, a missing tax mapping) and repeat the process.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
When you submit a support request, attach the relevant API Call Log entry – this speeds up processing considerably.
{% endhint %}


---

# 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/shopware/shopware6_en_us/monitoring-and-logs/analyze-api-responses.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.
