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

# API Call Log

The **API Call Log** records the technical details of every API call – ideal for understanding the exact cause of an error.

**Enabling**

Logging is controlled by the configuration setting **Enable Developer Log**. In the event of HTTP errors, an entry is created even if logging is switched off.

{% hint style="warning" %}
Enable the Developer Log specifically for troubleshooting. In continuous operation it generates a large number of entries.
{% endhint %}

**Contents of an entry**

| Field                        | Meaning                                  |
| ---------------------------- | ---------------------------------------- |
| Timestamp (request/response) | Time stamp                               |
| Method                       | GET, POST, PATCH, PUT, DELETE            |
| Request URL                  | Complete API URL                         |
| Success / status code        | Result of the call                       |
| Request data / response data | JSON content of the request and response |
| Source                       | Reference to the BC object               |

**Usage**

1. Enable the Developer Log.
2. Repeat the process (for example, a product upload).
3. Open the relevant entry in the API Call Log and check the request/response.

{% hint style="info" %}
The page shows the request and the response in plain text – ideal for providing support with precise information.
{% 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 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/monitoring-and-logs/api-call-log.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.