--- metadata: - name: generator content: Diplodoc Platform v5.55.0 alternate: - https://yandex.com/dev/market/partner-api/doc/en/pushapi/concepts/inform-on-errors.md - https://yandex.com/dev/market/partner-api/doc/ru/pushapi/concepts/inform-on-errors.md - https://yandex.com/dev/market/partner-api/doc/zh/pushapi/concepts/inform-on-errors.md - href: en/pushapi/concepts/inform-on-errors.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.com/dev/market/partner-api/doc/en/llms.txt {% note warning "Starting from December 31, push API methods will be unavailable. From October 1, they may be unstable." %}   {% endnote %}   # Error messages The store is expected to respond to the Yandex.Market request `200 OK` (request processed successfully), however, in case of errors, the store can report them. Possible HTTP codes Store responses: - `400 Bad Request` — The request from Yandex. Market violates the API logic. - `403 Forbidden` — The Market sent an incorrect token. - `500 Internal Server Error` — the error is on the store's side. **Type of error**|**Error subtype**|**Error description** ----- | ----- | ----- `CANT_GET_RESPONSE` | `CONNECTION_REFUSED` | The connection to the store's server could not be established. The error may be caused by network problems on the store's side. `CANT_GET_RESPONSE` | `CONNECTION_TIMED_OUT` | The waiting time for connecting to the store's server has expired. `CANT_GET_RESPONSE` | `HTTP` | The response from the store was different from `200 OK`. `CANT_GET_RESPONSE` | `READ_TIMED_OUT` | The waiting time for the store's response to the Yandex.Market request has expired. `CANT_GET_RESPONSE` | `SSL_ERROR` | A secure connection to the store's server cannot be established. The security certificate is not valid. `CANT_GET_RESPONSE` | `UNSUPPORTED_MEDIA_TYPE` | The store's response header states [data format](data-format.md), different from the one specified in the settings. `INVALID_RESPONSE` | `CANT_PARSE_RESPONSE` | The store's response could not be parsed. `INVALID_RESPONSE` | `IGNORED_WRONG_TOKEN` | Incorrect order was sent to the store [authorization token](identification.md) however, the request was not rejected. `INVALID_RESPONSE` | `INVALID_DATA` | The body of the store's response contains incorrect data or insufficient data. For example, there is no delivery information, a negative price is indicated for the product, an incorrect date format is specified, etc. See the error details below. ## Error Details `INVALID_DATA` {#invalid-data} ### In response to the request POST cart {#post-cart-response} **Description**|**Explanation**|**A possible solution** ----- | ----- | ----- **cartResponse contains extra item with feedId=[] and offerId=[]** | The response contains an extra item `item` with the specified `feed-id` and `offer-id`. | Check the correctness of the transmitted data. **cartResponse is null** | The response body is missing. | Send the response body. **delivery id is longer than [] symbols** | Parameter Value `id` delivery options `delivery` exceeds the maximum allowed limit. | Specify a valid value for this parameter. **'delivery options' contains duplicates** | The response duplicates the parameter `delivery-options`. | Check the correctness of the transmitted data. **'delivery options' is empty but 'items' isn't** | An empty parameter was received `delivery-options` However , the parameter `items` contains data. | Check the correctness of the transmitted data. **'delivery options' is null** | The parameter is missing in the response `delivery-options`. | Specify the parameter. **delivery outletId is not positive: []** | A negative parameter value was obtained `outlet-id`. | Check the correctness of the transmitted data. **delivery outletId is null** | The parameter is missing in the response `outlet-id`. | Specify the parameter. **delivery 'outlets' is empty** | An empty parameter was received `outlets` for the delivery option `delivery`. | Specify the data for the parameter. **delivery price is negative: []** | A negative value was obtained `price` for the delivery option `delivery`. | Check the correctness of the transmitted data. **delivery price is null** | The parameter is missing in the response `price` for the delivery option `delivery`. | Specify the parameter. **delivery serviceName is null** | The parameter is missing in the response `service-name` for the delivery option `delivery`. | Specify the parameter. **delivery type is null** | The parameter is missing in the response `type` for the delivery option `delivery`. | Specify the parameter. **delivery type=DELIVERY and 'outlets' is not null** | The type of delivery option has been received `DELIVERY` however, there is a list of points of sale. | Check the correctness of the transmitted data. **delivery type=PICKUP and 'outlets' is null** | The type of delivery option has been received `PICKUP` However, there is no list of points of sale. | Check the correctness of the transmitted data. **delivery 'serviceName' is longer than [] symbols** | Parameter Value `service-name` delivery options `delivery` exceeds the maximum allowed limit. | Specify a valid value for this parameter. **'deliveryDates' is null** | The parameter is missing in the response `dates` delivery options `delivery`. | Specify the parameter. **fromDate in deliveryDates is null** | The parameter is missing in the response `from-date` for the delivery date. | Specify the parameter. **'from-date' should not be after 'to-date'. From-date=[]. To-date=[]** | Delivery date `from-date` (from) cannot be later than the delivery date `to-date` (before). | Check the correctness of the transmitted data. **'from-date' should not be before current day. From-date=[].** | Delivery date `from-date` (from) cannot be earlier than the current date. | Check the correctness of the transmitted data. **item count is negative: []** | A negative parameter value was obtained `count` for the product `item`. | Check the correctness of the transmitted data. **item count is null** | The parameter is missing in the response `count` for the product `item`. | Specify the parameter. **item feedId is not positive: []** | A negative parameter value was obtained `feed-id` for the product `item`. | Check the correctness of the transmitted data. **item feedId is null** | The parameter is missing in the response `feed-id` for the product `item`. | Specify the parameter. **item offerId is empty** | An empty parameter was received `offer-id`. | Specify the data for the parameter. **item offerId is null** | The parameter is missing in the response `offer-id` for the product `item`. | Specify the parameter. **item price is not positive: []** | A negative parameter value was obtained `price` for the product `item`. | Check the correctness of the transmitted data. **item price is null** | The parameter is missing in the response `price` for the product `item`. | Specify the parameter. **'items' is null** | The parameter is missing in the response `items`. | Specify the parameter. **number of items in cartResponse is greater than number of items in cartRequest** | The number of products in the response is higher than in the request. | Check the correctness of the transmitted data. **payment method is null** | In the parameter name `payment-method` contains errors. | Check the correctness of the transmitted data. **'payment methods' is empty but 'items' isn't** | An empty parameter was received `payment-methods` However , the parameter `items` contains data. | Check the correctness of the transmitted data. **'payment methods' is null** | The parameter is missing in the response `payment-methods`. | Specify the parameter. **Value of delivery price has too high scale: []** | The accuracy is set too high for the parameter `price` delivery options. | Set the parameter values with less precision. **Value of item price has too high scale: []** | The accuracy is set too high for the parameter `price`. | Set the parameter values with less precision. ### In response to the request POST order/accept {#post-order-accept-response} **Description**|**Explanation**|**A possible solution** ----- | ----- | ----- **'accepted' is null** | The parameter is missing in the response `accepted`. | Specify the parameter. **'accepted=true' and declineReason is not null: []** | The value received in the response is `true` the parameter `accepted`, however, the reason for rejecting the order is indicated `reason`. | Check the correctness of the transmitted data. **'accepted=false' and declineReason is null** | The value received in the response is `false` the parameter `accepted` However, the reason for rejecting the order is not specified `reason`. | Check the correctness of the transmitted data. **length of orderResponse.id is greater than []** | Parameter Value `id` exceeds the maximum allowed limit. | Specify a valid value for this parameter. **orderResponse is null** | The response body is missing. | Send the response body. **orderResponse.id is null** | The parameter is missing in the response `id`. | Specify the parameter.