---
metadata:
  - name: generator
    content: Diplodoc Platform v5.52.0
alternate:
  - https://yandex.ru/dev/market/partner-api/doc/en/concepts/debug.md
  - https://yandex.ru/dev/market/partner-api/doc/ru/concepts/debug.md
  - https://yandex.ru/dev/market/partner-api/doc/zh/concepts/debug.md
  - href: en/concepts/debug.md
    type: text/markdown
    title: Markdown version
  - href: ../llms.txt
    type: text/markdown
    title: llms.txt
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/dev/market/partner-api/doc/en/llms.txt

# Request logs



On the pages with logs, you can view requests to Yandex Market API or the store's API, as well as find out information about the response. To do this, click on the icon of your account → in the seller's account on the Market. **Settings** and in the menu on the left, select **APIs and modules** → tab **Query log** or **Notification Log**.

![Screenshot of the widget](../_images/concepts/widget.png)


{% note warning %}


If the API is unavailable, API requests are not executed and are not recorded in logs. [Learn more about API access control](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-access.md)


{% endnote %}




On these pages   for each integration   there are widgets with information:

   * calls to which resources are terminated with errors (tab **Query log**);

   

   * the response to which type of notification is received with an error (tab **Notification Log**);
   

   * the percentage and number of errors in requests.



For the integration to work correctly, fix the errors. To view the details, click on the row with the problematic request or notification type, and the log table will be updated.

  ![Screenshot of the log table](../_images/concepts/logs.png)



## How to work with logs {#how-to}

On the logs page, you can:

 * Search by the body of the request and response, as well as by the request parameters. To do this, in the field **Search** enter the information you want to find.

 * Search by filters. For example, using the **Resource** filter, you can find queries using certain methods.  , and by filter **Integration** — queries related to the selected integration  .



 * View detailed information on request — click on the line with it to see the request itself and the response received. Learn more about errors and how to solve them:

   * [Query errors to Yandex Market API](https://yandex.ru/dev/market/partner-api/doc/en/concepts/error-codes.md)
   * [Errors when connecting or working with API notifications](https://yandex.ru/dev/market/partner-api/doc/en/push-notifications/concepts/error-codes.md)

 * Check which integration requests and responses relate to, — in the block **Type of integrations** the name that you provided in the request or response is specified, or the type **Documentation Console** if you have used it. [Learn more about how to sign integrations](https://yandex.ru/dev/market/partner-api/doc/en/concepts/integration-signing.md)



## Unique request ID {#traceparent}



The market transmits a unique request identifier in the header [traceparent](*traceparent):

* the response, if it is a request from the store to the Market.
* the request itself in the case of API notifications, when the Market sends a request to the store. [How to work with notifications](https://yandex.ru/dev/market/partner-api/doc/en/push-notifications/index.md)

Example of a request or response header:



```no-highlight translate=no
Content-Type: application/json
traceparent: 00-8b05ba11f1d37f7cfce0eac1a5230600-8b23fad39202f968-01
```

With the request ID, you can find its logs faster, and it can also be useful when contacting support.

To find information about a completed query:

1. Insert the unique identifier in the field **Search**.

2. Click on the request to see detailed information, including its ID in the field. **Tracing**.

[*traceparent]:
It is included in the open standard [OpenTelemetry](https://opentelemetry.io/docs/).