> 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/monitoring-and-protokolle/api-call-log.md).

# API Call Log

Der **API Call Log** protokolliert die technischen Details jedes API-Aufrufs – ideal, um Fehlerursachen genau zu verstehen.

**Aktivieren**

Das Logging wird über die Konfigurationseinstellung **Enable Developer Log** gesteuert. Bei HTTP-Fehlern wird ein Eintrag auch dann erzwungen, wenn das Logging ausgeschaltet ist.

{% hint style="warning" %}
Aktivieren Sie den Developer Log gezielt zur Fehlersuche. Im Dauerbetrieb erzeugt er viele Einträge.
{% endhint %}

**Inhalt eines Eintrags**

| Feld                          | Bedeutung                            |
| ----------------------------- | ------------------------------------ |
| Zeitpunkt (Request/Response)  | Zeitstempel                          |
| Methode                       | GET, POST, PATCH, PUT, DELETE        |
| Anfrage-URL                   | Vollständige API-URL                 |
| Erfolg / Statuscode           | Ergebnis des Aufrufs                 |
| Anfrage-Daten / Antwort-Daten | JSON-Inhalt von Request und Response |
| Quelle                        | Bezug zum BC-Objekt                  |

**Nutzung**

1. Developer Log aktivieren.
2. Vorgang wiederholen (z. B. Produkt-Upload).
3. Im API Call Log den betreffenden Eintrag öffnen und Request/Response prüfen.

{% hint style="info" %}
Die Karte zeigt Anfrage und Antwort im Klartext – ideal, um dem Support präzise Informationen zu liefern.
{% 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/monitoring-and-protokolle/api-call-log.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.