--- metadata: - name: generator content: Diplodoc Platform v5.52.0 alternate: - https://yandex.ru/dev/market/partner-api/doc/en/concepts/error-codes.md - https://yandex.ru/dev/market/partner-api/doc/ru/concepts/error-codes.md - https://yandex.ru/dev/market/partner-api/doc/zh/concepts/error-codes.md - href: en/concepts/error-codes.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 # Types of errors and what to do about them If the request could not be completed, Yandex. Market returns a parameter in response `errors`. It contains error codes (parameter `code`) and their brief descriptions (parameter `message`). If there are too many errors with a certain code, you will receive a notification about this in the seller's account on the Market. ## What do the error codes mean? {#codes} #| ||**Code**|**Title**|**What happened and what to do**|| ||[400](#400)| `Bad Request` | Something is wrong with the request content. For example, there is an error in the JSON data format or you are trying to change the status of a cancelled or delivered order. Focus on the error description to understand what exactly is wrong.|| ||[401](#401)| `Unauthorized` | The authorization token is not specified in the request (or is specified, but not there).|| ||[403](#403)| `Forbidden` | * The authorization token did not work. **For the OAuth token:** most likely, it has expired or you have removed the person for whom the token was issued from the staff. * Another access error. || ||[404](#404)| `Not Found` | * The requested method or resource was not found. Check the request addresses that the system uses. * The specified parameter was not found. For example, a campaign. Check the correctness of the transmitted data. * The method version was not found. Check that the version you are using is correct. || ||[405](#405)| `Method Not Allowed` | There is no such method on the specified resource. Check the request addresses that the system uses.|| ||[415](#415)| `Unsupported Media Type` | The requested content type is not supported by the method. Check the correctness of the request.|| ||[420](#420)| `Enhance Your Calm` | The request limit has been exceeded. Make sure that your system does not send anything superfluous.|| ||[423](#423)| `Locked` | The method cannot be used for this store. Focus on the error description to understand what exactly is wrong.|| ||[499](#499)| `Client Closed Request` | The client closed the connection before the request was processed on the side. Yandex.Market . Check the timeouts on the client side and repeat the request.|| ||[500](#500)| `Internal Server Error` | Internal error Yandex.Market .|| ||[503](#503)| `Service Unavailable` | The server Yandex.Market overloaded.|| |# ## Errors in the query content (400) {#400} ### Errors found in all methods {#common} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**'field' elements must be not null (rejected value: 'value')** | Collection items should not be `null`. | Delete or replace the elements with the value `null`.| It is found in all methods. || ||**'field' must be greater than 'value' (rejected value: 'value')** | The value must be strictly greater than the threshold. | Specify a value from the acceptable range.| It is found in all methods. || ||**'field' must be greater than or equal to 'value' (rejected value: 'value')** | The value must be greater than or equal to the threshold. | Specify a value from the acceptable range.| It is found in all methods. || ||**'field' must be less than or equal to 'value' (rejected value: 'value')** | The value must be less than or equal to the threshold. | Specify a value from the acceptable range.| It is found in all methods. || ||**'field' must match 'regexp' (rejected value: 'value')** | The value does not match the required template. | Pass the value corresponding to the regular expression.| It is found in all methods. || ||**'field' must not be empty (rejected value: 'value')** | The field must not be empty. | Pass a non-empty field value.| It is found in all methods. || ||**'field' must not be null (rejected value: null)** | The required field is not passed. | Specify the field value.| It is found in all methods. || ||**'field' size must be between 'min' and 'max' (rejected size: 'size')** | Invalid collection size: must be from 'min' to 'max'. | Change the number of elements to acceptable.| It is found in all methods. || ||**'field' size must be between 'min' and 'max' (rejected value: 'value')** | Invalid value length: must be from 'min' to 'max'. | Pass the value of the allowed length.| It is found in all methods. || ||**Campaign type is not allowed. Allowed campaign types: 'campaignTypes'** | This method does not support your store's operating model. | Make sure that you use a method that supports your store's operating model.| It is found in all methods. || ||**Content type 'contentType' not supported** | The requested content type is not supported. | Pass one of the supported content types in the header `Content-Type`. [Learn more about the input data format](https://yandex.ru/dev/market/partner-api/doc/en/concepts/input-format.md) | It is found in all methods. || ||**Illegal input at 'path'** | Invalid value for the specified path. | Check the structure and types in the request body using the specified path; correct the field names and value formats to match the expected JSON schema. If the content type is not JSON, specify the correct one. `Content-Type`. | It is found in all methods. || ||**JSON: {message}** | The JSON data format contains an error. | Check the correctness of the JSON. | It is found in all methods. || ||**Required request body is missing** | The request body is required, but it has not been transmitted. | Make sure that you have passed the request body for the method where it is required. | It is found in all methods. || ||**Required request parameter 'param' is not present** | The required parameter was not passed. | Make sure that you have passed all the required input parameters for the method used. | It is found in all methods. || ||**The request is too big: Maximum allowed request size must be less than 'maxSize' KB, but passed 'size' MB** | The request is too large: the size of the transmitted request is greater than the maximum allowed. | Reduce the request body; if there is a large volume, split the data into several smaller requests so that each one does not exceed the limit. | It is found in all methods. || ||**The request is too big: {message}** | The HTTP request size limit has been exceeded. | The content size cannot exceed 512 KB. Split the request into several.| It is found in all methods. || ||**Type mismatch: 'value'** | The input value type does not match the expected parameter type. | Pass the values in the correct format and type, which can be viewed on the corresponding methods page. | It is found in all methods. || ||**Unexpected end of content** | The request body ends unexpectedly. | Check the correctness of the format of the data transmitted in the request body.| It is found in all methods. || ||**Incorrect X-Business-Id header value: 'value'** | Incorrect header value `X-Business-Id`. | Enter the correct positive numeric value of the cabinet ID in the header. `X-Business-Id`. | It is found in all methods. || ||**URL businessId ('urlBusinessId') does not match businessId in X-Business-Id header ('headerBusinessId')** | Account ID in URL does not match the identifier in the header `X-Business-Id`. | Make sure that `businessId` in URL matches the value in the header `X-Business-Id`. | It is found in all methods in which `businessId` transmitted to URL. || |# ### Pagination errors {#pagination} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Bad page token**| Invalid pagination token.| Check the correctness of the transmitted pagination token. [Learn more about pagination in queries](https://yandex.ru/dev/market/partner-api/doc/en/concepts/pagination.md). | It is found in all methods where pagination is used. || ||**Parameter limit must be less than or equal to 'max-limit' (rejected value: 'limit')**| The limit on the number of values per page has been exceeded — parameter `limit`.| Reduce the number of values. | It is found in all methods where pagination is used. || |# ### Errors when working with orders {#orders} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Action is not allowed for order 'orderId' with status 'status' and substatus 'substatus'** | The action is not available for the order in the current status and sub-status. | Detailed instructions on how to handle orders for your type of placement can be found in the section [Step-by-step instructions](https://yandex.ru/dev/market/partner-api/doc/en/step-by-step/index.md). | [POST v2/campaigns/{campaignId}/orders/{orderId}/delivery/track](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/setOrderDeliveryTrackCode.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/delivery/date](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/setOrderDeliveryDate.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/identifiers](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/provideOrderItemIdentifiers.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/boxes](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/setOrderBoxLayout.md) || ||**Attempt to change order items or instances after READY_TO_SHIP** | An attempt to change order items or labeling codes after switching to the status `READY_TO_SHIP`. | Do not try to change the order composition or labeling codes after switching to the status `READY_TO_SHIP`. Detailed instructions on how to handle orders for your type of placement can be found in the section [Step-by-step instructions](https://yandex.ru/dev/market/partner-api/doc/en/step-by-step/index.md). | [PUT v2/campaigns/{campaignId}/orders/{orderId}/boxes](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/setOrderBoxLayout.md) || ||**Can't create return for order with status: 'status'**|You cannot create a refund for an order in its current status.|Create a refund only for an order with the status `DELIVERED`.|[POST v1/campaigns/{campaignId}/returns/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/returns/createReturn.md) || ||**Can't resolve geo for address 'address'**|An incorrect delivery address was transmitted.|Check the correctness of the delivery address: specify the full address, including the region and locality.|[POST v1/campaigns/{campaignId}/orders/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/createOrder.md) || ||**Cancellation request substatus 'subbstatus' is not available for status 'status' and role 'role' for order 'orderId'** | The sub-status of the cancellation request is not available for the specified combination of status and role. | Use the correct sub-status based on the order status and your role. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) || ||**Cannot do operation for order with status 'status', and substatus 'substatus' (partnerId = 'partnerId', orderId = 'orderId')** | It is not possible to perform an operation for an order with the current status and sub-status. | Do not send an external ID after the order status changes `PROCESSING` with a sub-status `READY_TO_SHIP`. | [POST v2/campaigns/{campaignId}/orders/{orderId}/external-id](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateExternalOrderId.md) || ||**Cannot do operation, external ID already set for order (partnerId = 'partnerId', orderId = 'orderId', externalId = 'externalId')** | The operation cannot be performed: the external ID has already been sent for the order. | Do not attempt to transmit the external order ID more than once. | [POST v2/campaigns/{campaignId}/orders/{orderId}/external-id](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateExternalOrderId.md) || ||**Delivery date can't be in the future** | The delivery date cannot be in the future. | Set the delivery date no later than the current moment. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) || ||**Delivery dates can't be updated for 'deliveryType' order with id 'orderId'**|You cannot change the delivery dates for the specified delivery type.|Check the delivery type of the order and change the date only for courier delivery.|[POST v1/campaigns/{campaignId}/orders/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrder.md) || ||**Exceeded the number of days to edit delivery dates! limit is: 'days' days** | The allowed period for editing delivery dates has been exceeded. | Postpone the date no further than the specified limit of days. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/delivery/date](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/setOrderDeliveryDate.md) || ||**Exceeded the number of edits of delivery dates! limit is: 'limit'** | The number of delivery date changes has been exceeded. | — | [PUT v2/campaigns/{campaignId}/orders/{orderId}/delivery/date](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/setOrderDeliveryDate.md) || ||**Failed to upload photos**|The links to the photos could not be processed.|Make sure that the links to the photo are valid and available, or use another hosting service.|[POST v1/campaigns/{campaignId}/returns/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/returns/createReturn.md) || ||**Invalid filters: interval between 'dateFrom' and 'dateTo' is more than 'range' days.** | Incorrect filters: the interval between the start and end dates exceeds the allowed value. | Reduce the period to the acceptable limit or divide the request into several smaller intervals. | [POST v1/businesses/{businessId}/orders](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/getBusinessOrders.md) || ||**Invalid incoming cis for item with id = %d for reason: {reason}** | An incorrect labeling code was transmitted for the product in the order. | Check that the transmitted marking code (`cis`) is non-empty and has a valid format. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/identifiers](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/provideOrderItemIdentifiers.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/boxes](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/setOrderBoxLayout.md) || ||**Invalid order boxes layout request. Violations: {violations}** | Incorrect box layout request. | Correct the layout according to the list of violations and repeat the request. Make sure that you do not specify the same product as different objects in the same box; one box does not contain both the entire product and parts of the goods. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/boxes](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/setOrderBoxLayout.md) || ||**Invalid status for order 'orderId': 'status', PROCESSING expected** | Invalid order status, pending status `PROCESSING`. | Use the method only for digital orders with the status `PROCESSING`. You can read more about working with digital orders in [step-by-step instructions](https://yandex.ru/dev/market/partner-api/doc/en/step-by-step/digital.md). | [POST v2/campaigns/{campaignId}/orders/{orderId}/deliverDigitalGoods](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/provideOrderDigitalCodes.md) || ||**Merchant return with id: 'returnId' already exists**|A refund with this external ID already exists.|Send a unique one `externalReturnId` for a new refund.|[POST v1/campaigns/{campaignId}/returns/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/returns/createReturn.md) || ||**New delivery dates are the same as the current!** | The new delivery date is the same as the current one. | Send the changed delivery date. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/delivery/date](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/setOrderDeliveryDate.md) || ||**No permission to set status 'newStatus' for order 'orderId' with status 'currentStatus'** | It is not allowed to set the transmitted status for an order with the current status. | Make sure that you are trying to transfer the order to the correct status. Detailed instructions on how to handle orders for your type of placement can be found in the section [Step-by-step instructions](https://yandex.ru/dev/market/partner-api/doc/en/step-by-step/index.md). | [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) || ||**No transition found: 'fromStatus' -> 'toStatus'** | The transition between statuses was not found. | Send the correct status for changing the order status. Detailed instructions on how to handle orders for your type of placement can be found in the section [Step-by-step instructions](https://yandex.ru/dev/market/partner-api/doc/en/step-by-step/index.md). | [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) || ||**Not a business buyer.** | Buyer — not a legal entity. | Use the method of obtaining information about the buyer — an individual [GET v2/campaigns/{campaignId}/orders/{orderId}/buyer](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/getOrderBuyerInfo.md). | [POST v2/campaigns/{campaignId}/orders/{orderId}/business-buyer](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-business-information/getOrderBusinessBuyerInfo.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/documents](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-business-information/getOrderBusinessDocumentsInfo.md) || ||**Not enough stock for items: 'offerIds'**|The product is not available enough.|Transfer only the items with the required amount of balance.|[POST v1/campaigns/{campaignId}/orders/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/createOrder.md) || ||**Offers not found for SKUs: 'offerIds'**|Non-existent product IDs were transmitted.|Check the correctness `offerIds`.|[POST v1/campaigns/{campaignId}/orders/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/createOrder.md) [POST v1/campaigns/{campaignId}/returns/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/returns/createReturn.md) [POST v1/campaigns/{campaignId}/delivery-options](https://yandex.ru/dev/market/partner-api/doc/en/reference/delivery-options/getDeliveryOptions.md) [POST v1/campaigns/{campaignId}/return-delivery-options](https://yandex.ru/dev/market/partner-api/doc/en/reference/delivery-options/getReturnDeliveryOptions.md) || ||**Order 'orderId' is in cancellation state**|The order is in the process of cancellation.|Do not modify the cancelled order.|[POST v1/campaigns/{campaignId}/orders/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrder.md) || ||**Order 'orderId' is in terminal state**|You cannot change the order in the final status.|Do not change the order in the statuses `DELIVERED` or `CANCELLED`.|[POST v1/campaigns/{campaignId}/orders/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrder.md) || ||**Order already exists with external id 'externalOrderId'**|An order with this external ID already exists.|Send a unique one `externalOrderId` for a new order.|[POST v1/campaigns/{campaignId}/orders/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/createOrder.md) || ||**Order creation start date is required to be less than end date** | The start date for filtering orders by checkout date must be less than the end date. | Set the beginning of the period strictly before the end; if necessary, swap the dates or adjust one of them. | [POST v1/businesses/{businessId}/orders](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/getBusinessOrders.md) || ||**Order is in the wrong status, it’s only possible starting from the status PROCESSING.** | The order is in an unsuitable status; the operation is only possible with the PROCESSING status. | Make sure that the transferred order is in the status `PROCESSING`, `DELIVERY`, `PICKUP` or `DELIVERED`. | [POST v2/campaigns/{campaignId}/orders/{orderId}/business-buyer](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-business-information/getOrderBusinessBuyerInfo.md) || ||**Order is not in shop-processing status (actual: 'status').** | The order is not in the status of processing by the store. | You can receive the data only if the order is in the status `PROCESSING`, `DELIVERY` or `PICKUP`. | [GET v2/campaigns/{campaignId}/orders/{orderId}/buyer](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/getOrderBuyerInfo.md) || ||**Order shipment start date is required to be less than end date** | The start date for filtering orders by shipping date to the delivery service must be less than the end date. | Set the beginning of the period strictly before the end; if necessary, swap the dates or adjust one of them. | [POST v1/businesses/{businessId}/orders](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/getBusinessOrders.md) || ||**Order update start is required to be less than end date** | The start date for filtering orders by date and time of the update must be less than the end date. | Set the beginning of the period strictly before the end; if necessary, swap the dates or adjust one of them. | [POST v1/businesses/{businessId}/orders](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/getBusinessOrders.md) || ||**Order.id='orderId' is not digital.** | The transmitted order is not digital. | Make sure that the transmitted order is digital. This method is only available for working with digital orders. | [POST v2/campaigns/{campaignId}/orders/{orderId}/deliverDigitalGoods](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/provideOrderDigitalCodes.md) || ||**Real delivery date should be from order creation date to current date inclusively** | The actual delivery date must be from the date the order was created up to and including the current date. | Specify the actual delivery date in the range from the order creation date to the current date inclusive. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) || ||**Status change was forbidden for client role = 'role'** | Changing the order status is prohibited for the customer role. | — | [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) || ||**Status not allowed: 'status'** | The transfer of the order to the transferred status is not allowed. | Check the correctness of the transmitted order status. It is allowed to transfer the order to the following statuses `PROCESSING`, `CANCELLED`, `DELIVERY`, `PICKUP`, `DELIVERED`.| [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) || ||**String (value) is not a valid country code according to ISO 3166-1 alpha-2** | Invalid country code. | Specify the country code in the ISO 3166-1 alpha-2 format. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/identifiers](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/provideOrderItemIdentifiers.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/boxes](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/setOrderBoxLayout.md) || ||**The requested delivery interval is not valid for order 'orderId'**|An incorrect delivery date interval was transmitted.|Check the available delivery intervals and send the current interval.|[POST v1/campaigns/{campaignId}/orders/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/createOrder.md) [POST v1/campaigns/{campaignId}/orders/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrder.md) || ||**Transition 'fromStatus' -> 'toStatus' is not allowed. Reason: {reason}** | Changing the order status from the current to the target is not available. | Make sure that you are trying to transfer the order to the correct status. Detailed instructions on how to handle orders for your type of placement can be found in the section [Step-by-step instructions](https://yandex.ru/dev/market/partner-api/doc/en/step-by-step/index.md).| [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) || ||**Wrong count for shop skus: 'offerIds'**|The incorrect number of items in the refund was sent.|Make sure that the number of items in the refund does not exceed the number of items in the order.|[POST v1/campaigns/{campaignId}/returns/create](https://yandex.ru/dev/market/partner-api/doc/en/reference/returns/createReturn.md) || |# ### Errors when working with shipments (FBS) {#shipments} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Closest shipment for reception transfer act generation not found.** | Shipments with the status **Can be processed** not found. | Create a purchase order or wait for the existing order to be upgraded to the desired status. | [GET v2/campaigns/{campaignId}/shipments/reception-transfer-act](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentReceptionTransferAct.md) || ||**Cutoff time for shipments has not been reached yet** | The time to confirm the shipment has not yet arrived. | Wait for the start of the shipping confirmation time according to the warehouse schedule and try again. You can check the shipment confirmation using the method [GET v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/getShipment.md): among the available actions `availableActions` There must be an action `CONFIRM`. | [POST v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/confirm](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/confirmShipment.md) || ||**No orders for closest shipment have been processed yet (shipmentId: 'shipmentId').** | There are no orders in the next shipment. | Check that the orders have the parameter `status` it matters `PROCESSING`, and the parameter `substatus` — `READY_TO_SHIP`. You can get the statuses and shipping dates of orders using the method [POST v1/businesses/{businessId}/orders](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/getBusinessOrders.md), change order statuses — using methods [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) and [POST v2/campaigns/{campaignId}/orders/status-update](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatuses.md). | [GET v2/campaigns/{campaignId}/shipments/reception-transfer-act](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentReceptionTransferAct.md) || ||**Outbound with id = 'shipmentId' is not confirmed and hasn't draft transfer** | Shipment has not been confirmed. | Before receiving the acceptance certificate, it is necessary to confirm the shipment. To do this, use the method [POST v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/confirm](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/confirmShipment.md). | [GET v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/act](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentAct.md) || ||**Shipment with ID 'shipmentId' contains invalid orders. Reasons: orders are in wrong status ('orderIds')** | The shipment contains orders with incorrect statuses. | For confirmation, the shipment must contain only orders in acceptable statuses.: `PROCESSING` with a sub-status `READY_TO_SHIP` or `SHIPPED`, or `DELIVERY`, `DELIVERED`, `PICKUP`. Transfer incorrect orders to the allowed statuses or transfer them to the next shipment using the method [POST v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/orders/transfer](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/transferOrdersFromShipment.md) and repeat the confirmation. | [POST v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/confirm](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/confirmShipment.md) || ||**Shipment with ID 'shipmentId' does not contain any orders** | There is not a single order in the shipment. | Add orders to the shipment: set them to acceptable statuses. Then repeat the confirmation. | [POST v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/confirm](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/confirmShipment.md) || ||**Shipment with ID 'shipmentId' has been confirmed already** | The shipment has already been confirmed. | Do not repeat the shipment confirmation. To receive the acceptance certificate for a confirmed shipment, use the method [GET v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/act](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentAct.md). | [GET v2/campaigns/{campaignId}/shipments/reception-transfer-act](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentReceptionTransferAct.md) [POST v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/confirm](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/confirmShipment.md) || ||**Some orders are in the process of being excluded from shipment (shipmentId: 'shipmentId', orderIds: 'orderIds'). Please wait up to 30 minutes and try again.** | IDs of orders in the nearest shipment that are in the process of being deleted from it. | Transferring orders can take up to 30 minutes. Wait for the transfer to finish and try again. | [GET v2/campaigns/{campaignId}/shipments/reception-transfer-act](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentReceptionTransferAct.md) || ||**Some orders have not been processed yet. Please change the status of orders to READY_TO_SHIP and try again. (shipmentId: 'shipmentId', orderIds: 'orderIds').** | IDs of orders in the nearest shipment that have not yet been processed. | Send it for orders with the specified IDs `status: PROCESSING` and `substatus: READY_TO_SHIP` and try again. You can change the order statuses using queries. [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) and [POST v2/campaigns/{campaignId}/orders/status-update](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatuses.md). | [GET v2/campaigns/{campaignId}/shipments/reception-transfer-act](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentReceptionTransferAct.md) || |# ### Errors when working with prices {#prices} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**discountBase is less than value: offerId = 'offerId'** | The crossed-out price is less than the current price of the product. | Set the crossed-out price not lower than the current one. If there is no discount — do not indicate the crossed-out price. | [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) || ||**Duplicate offer in request: offerId = 'offerId'** | Duplicate product in the request. | Check the uniqueness of the transferred items. | [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) || ||**Missing offerId** | The product ID is missing. | Pass a non-empty `offerId`. | [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) || ||**Missing price value: offerId = 'offerId'** | The product price value is missing. | Transmit the value of the product price. | [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) || ||**Offer at index 'index' should have valid discount value. Discount percentage must be between 'min' and 'max', actual 'val'** | The product has an invalid discount value: the discount percentage must be from 'min' to 'max'. | Specify the discount percentage in the acceptable range.| [POST v2/businesses/{businessId}/offer-mappings/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/updateOfferMappings.md) [POST v2/businesses/{businessId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updateBusinessPrices.md)|| ||**Offer at index 'index' should not have 'fieldName' with 'currency' currency** | Incorrect currency is specified for the price. | Send the price in the cabinet currency. You can view the currency in the cabinet using the method [GET v2/campaigns/{campaignId}/settings](https://yandex.ru/dev/market/partner-api/doc/en/reference/campaigns/getCampaignSettings.md). | [POST v2/businesses/{businessId}/offer-mappings/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/updateOfferMappings.md) [POST v2/businesses/{businessId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updateBusinessPrices.md) || ||**Offer at index 'index' should not have 'fieldName' with too many digits** | There are too many decimal places passed for the field. | Pass a value with no more than 7 decimal places. | [POST v2/businesses/{businessId}/offer-mappings/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/updateOfferMappings.md) [POST v2/businesses/{businessId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updateBusinessPrices.md) || ||**offerId = 'offerId' should have valid discount value. Discount percentage must be between min' and 'max', actual 'val'** | The product has an invalid discount value: the discount percentage must be from 'min' to 'max'. | Specify the discount percentage in the acceptable range.| [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) || ||**Unrecognized vat: 'value': offerId = 'offerId'** | The unrecognized VAT rate. | Send the correct VAT rate for the product. You can view the acceptable VAT IDs on the method page. [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md). | [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) || ||**Vat setting of 'vatName' ('vatId') not supported for current 'taxSystemName' ('taxSystemId') taxSystem: 'offerId'** | The VAT rate is not supported for the current taxation system. | Use the supported VAT rate for your tax system/country. | [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) [POST v2/campaigns/{campaignId}/offers/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/offers/updateCampaignOffers.md) || ||**Vat setting of 'vatName' ('vatId') not supported since year 2019: 'offerId'** | The VAT rate has not been supported since 2019. | Do not use the unsupported 18% rate. Specify the current supported rate for your tax system/country. | [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) [POST v2/campaigns/{campaignId}/offers/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/offers/updateCampaignOffers.md) || |# ### Errors when working with products {#offers} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Duplicate offerId='offerId' at positions 'positions'** | Duplicate items were transferred. | Ensure that the items in the transmitted list are unique. | [POST v2/campaigns/{campaignId}/hidden-offers](https://yandex.ru/dev/market/partner-api/doc/en/reference/hidden-offers/addHiddenOffers.md) || ||**Offer at index 'index' cannot have parameter 'fieldName' deleted and set at the same time** | You can either pass the parameter value to `deleteParameters`, or the corresponding parameter in `UpdateOfferDTO`. | To delete a previously passed parameter, specify its value in `deleteParameters` and don't send it to `UpdateOfferDTO`.

If you want to set a new parameter value, pass it to `UpdateOfferDTO` and do not specify in `deleteParameters`. | [POST v2/businesses/{businessId}/offer-mappings/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/updateOfferMappings.md) || ||**Offer at index 'index' should not have empty values in list of 'fieldName'** | The product must not contain empty values in the list. | Remove empty items from the 'fieldName' list or replace them with valid values. | [POST v2/businesses/{businessId}/offer-mappings/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/updateOfferMappings.md) || ||**Offer at index 'index' should have weightDimensions. greater than 0** | The dimensions of the package and the weight of the product must be positive. | Send positive values for the package dimensions and the weight of the product. | [POST v2/businesses/{businessId}/offer-mappings/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/updateOfferMappings.md) || ||**Offers should have different ids. Following offers ids are repeating: 'offerIds'.** | The transferred items must be unique. | Check the uniqueness of the transmitted product IDs. | [POST v2/businesses/{businessId}/offer-mappings/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/updateOfferMappings.md) || |# ### Errors when working with leftovers {#stocks} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Duplicate shop-sku 'sku' for warehouse 'count'** | Duplicate shop-sku for the warehouse. | Check the uniqueness of the transmitted values `sku`.| [PUT v2/campaigns/{campaignId}/offers/stocks](https://yandex.ru/dev/market/partner-api/doc/en/reference/stocks/updateStocks.md) [POST v3/businesses/{businessId}/offers/stocks/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/stocks/updateStocksOnPartnerWarehouses.md) || ||**Stock for 'sku' should not be in the future** | Data on the remaining items should not be available in the future. | Install `updatedAt` no later than the current moment. | [PUT v2/campaigns/{campaignId}/offers/stocks](https://yandex.ru/dev/market/partner-api/doc/en/reference/stocks/updateStocks.md) [POST v3/businesses/{businessId}/offers/stocks/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/stocks/updateStocksOnPartnerWarehouses.md) || ||**Stock for 'sku' should not be older than a day** | The remaining data for the product must not be more than a day old. | Enter the current date and time of the update (no more than 24 hours) in the field `updatedAt`. | [PUT v2/campaigns/{campaignId}/offers/stocks](https://yandex.ru/dev/market/partner-api/doc/en/reference/stocks/updateStocks.md) [POST v3/businesses/{businessId}/offers/stocks/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/stocks/updateStocksOnPartnerWarehouses.md) || |# ### Errors when working with points of sale {#outlets} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**datediff-is-to-big-local** | For delivery in your region, the difference between the maximum and minimum delivery time should not exceed two days. | Make sure that the difference between `maxDeliveryDays` and `minDeliveryDays` not more than two days. | [POST v2/campaigns/{campaignId}/outlets](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/createOutlet.md) [PUT v2/campaigns/{campaignId}/outlets/{outletId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/updateOutlet.md) || ||**datediff-is-to-big-long-period** | When delivering to other regions where the minimum delivery time is more than 18 days, the difference between the maximum and minimum delivery time should not exceed the minimum time. | Make sure that the difference between `maxDeliveryDays` and `minDeliveryDays` does not exceed `minDeliveryDays`. | [POST v2/campaigns/{campaignId}/outlets](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/createOutlet.md) [PUT v2/campaigns/{campaignId}/outlets/{outletId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/updateOutlet.md) || ||**datediff-is-to-big-remote** | For delivery to other regions, the difference between the maximum and minimum delivery time should not exceed four days. | Make sure that the difference between `maxDeliveryDays` and `minDeliveryDays` not more than four days. | [POST v2/campaigns/{campaignId}/outlets](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/createOutlet.md) [PUT v2/campaigns/{campaignId}/outlets/{outletId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/updateOutlet.md) || ||**Not valid outlet info: 'errors'** | Invalid point of sale data. | Correct the data of the point of sale according to the error text (address, region, opening hours, required fields, value format, etc.) and repeat the request. The full requirements for the fields can be found in the descriptions of the corresponding methods. | [POST v2/campaigns/{campaignId}/outlets](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/createOutlet.md) [PUT v2/campaigns/{campaignId}/outlets/{outletId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/updateOutlet.md) || ||**Outlet with code 'shopOutletCode' already exists for campaign 'campaignId'** | The point of sale with the transmitted ID `shopOutletCode` it already exists. | The value of the identifier `shopOutletCode` it must be unique within the same campaign. | [POST v2/campaigns/{campaignId}/outlets](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/createOutlet.md) || ||**Region 'regionName' cannot be used as outlet region** | The region cannot be used as a point of sale address. | Specify only the following types of regions `TOWN` (city), `CITY` (large city) and `REPUBLIC_AREA` (district of the federal subject). The region type is specified in the output parameter `type` requests [GET v2/regions](https://yandex.ru/dev/market/partner-api/doc/en/reference/regions/searchRegionsByName.md) and [GET v2/regions/{regionId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/regions/searchRegionsById.md). | [POST v2/campaigns/{campaignId}/outlets](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/createOutlet.md) [PUT v2/campaigns/{campaignId}/outlets/{outletId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/updateOutlet.md) || ||**Wrong outlet gps coordinates** | Incorrect GPS coordinates of the point of sale. | Specify the coordinates in the format: longitude, latitude. Delimiters: comma and/or space. For example, `20.4522144, 54.7104264`. | [POST v2/campaigns/{campaignId}/outlets](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/createOutlet.md) [PUT v2/campaigns/{campaignId}/outlets/{outletId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/updateOutlet.md) || |# ### Errors when working with categories {#categories} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Category is not a leaf.** | The category is not a leaf one. | Use the ID of the leaf category (a category that has no children). To get a category tree on the Market, use the method [POST v2/categories/tree](https://yandex.ru/dev/market/partner-api/doc/en/reference/categories/getCategoriesTree.md). | [POST v2/category/{categoryId}/parameters](https://yandex.ru/dev/market/partner-api/doc/en/reference/content/getCategoryContentParameters.md) || ||**Following categories are not leaf categories: 'categories'** | The transmitted categories are not leaf categories. | Use the IDs of the leaf categories (categories that have no children). To get a category tree on the Market, use the method [POST v2/categories/tree](https://yandex.ru/dev/market/partner-api/doc/en/reference/categories/getCategoriesTree.md). | [POST v2/tariffs/calculate](https://yandex.ru/dev/market/partner-api/doc/en/reference/tariffs/calculateTariffs.md) || ||**Unknown categories: 'categories'** | Unknown categories have been transmitted. | Check that the transmitted category IDs are correct. To find out the ID of the category to which the product you are interested in belongs, use the request [POST v2/categories/tree](https://yandex.ru/dev/market/partner-api/doc/en/reference/categories/getCategoriesTree.md). | [POST v2/tariffs/calculate](https://yandex.ru/dev/market/partner-api/doc/en/reference/tariffs/calculateTariffs.md) || ||**Requested businessId ('requestedBusinessId') does not match businessId in X-Business-Id header ('headerBusinessId')** | The cabinet ID in the query parameter does not match the ID in the header. `X-Business-Id`. | Make sure that `businessId` The query parameter matches the value in the header. `X-Business-Id`. | [POST v2/category/{categoryId}/parameters](https://yandex.ru/dev/market/partner-api/doc/en/reference/content/getCategoryContentParameters.md) || |# ### Errors when working with pricing plans {#tariffs} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Invalid parameter: payout frequency 'frequency' and delay weeks 'paymentDelayWeeks' are not supported** | An unsupported combination of frequency and deferred payments has been transmitted. | For an account in the Russian Federation, the following frequencies are supported: `DAILY`; or frequency `WEEKLY` deferred payments of 1, 2 or 4 weeks (`paymentDelayWeeks`). | [POST v2/tariffs/calculate](https://yandex.ru/dev/market/partner-api/doc/en/reference/tariffs/calculateTariffs.md) || ||**Currency 'currency' is not supported for tariff calculation** | The currency that is unsupported for calculating tariffs has been transferred. | Specify the currency that is supported for calculating tariffs. | [POST v2/tariffs/calculate](https://yandex.ru/dev/market/partner-api/doc/en/reference/tariffs/calculateTariffs.md) || |# ### Mistakes when working with stocks {#promos} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Not enough parameters in request: offerIds or deleteAllOffers should be specified** | The parameter for removing products from the promotion was not passed. | To remove all products, pass the value `true` in the parameter `deleteAllOffers`. To delete only some items, transfer them SKU in the parameter `offerIds`. | [POST v2/businesses/{businessId}/promos/offers/delete](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/deletePromoOffers.md) || ||**Promo has ended** | The promotion is over. | Check the correctness of the transmitted stock ID. To find out which promotions you can participate in, use the method [POST v2/businesses/{businessId}/promos](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/getPromos.md). | [POST v2/businesses/{businessId}/promos/offers](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/getPromoOffers.md) [POST v2/businesses/{businessId}/promos/offers/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/updatePromoOffers.md) [POST v2/businesses/{businessId}/promos/offers/delete](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/deletePromoOffers.md) || ||**The limit for promo update requests with a single offerId has been exceeded. Please wait or use batch requests with multiple offerIds for the same promoId.** | The limit of requests to update the promotion for one product per request has been exceeded. | Wait and try again later, or use queries with multiple items in the list. `offers` for the same promotion. | [POST v2/businesses/{businessId}/promos/offers/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/updatePromoOffers.md) [POST v2/businesses/{businessId}/promos/offers/delete](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/deletePromoOffers.md) || ||**Too many parameters in request: only one of parameters offerIds or deleteAllOffers should be specified** | You can either pass the value `true` in the parameter `deleteAllOffers`, or SKU products in the parameter `offerIds`. | Give me one thing. — or the value `true` in the parameter `deleteAllOffers`, or SKU products in the parameter `offerIds`. | [POST v2/businesses/{businessId}/promos/offers/delete](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/deletePromoOffers.md) || |# ### Errors in reports and documents {#reports} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Contract with type MARKETING was signed with the agency** | The marketing contract has been signed with the agency. | For information on the closing documents, please contact your agency. | [POST v2/reports/closure-documents/detalization/generate](https://yandex.ru/dev/market/partner-api/doc/en/reference/reports/generateClosureDocumentsDetalizationReport.md)|| ||**Date field 'dateFieldTo' must be greater or equal to 'dateFieldFrom'!** | The end date of the interval must be at least the start date. | Set the end of the period no earlier than the beginning; adjust the dates or swap them if necessary. | [POST v2/campaigns/{campaignId}/stats/orders](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders-stats/getOrdersStats.md) || ||**Only default prices are used for this business. Generate the report at the business level (not campaign) to see actual prices.** | Only the uniform cabinet prices are used for this cabinet. | Create a business-level report (not a campaign). To check whether store prices are enabled, use the parameter `onlyDefaultPrice` in the method [POST v2/businesses/{businessId}/settings](https://yandex.ru/dev/market/partner-api/doc/en/reference/businesses/getBusinessSettings.md). | [POST v2/reports/goods-prices/generate](https://yandex.ru/dev/market/partner-api/doc/en/reference/reports/generateGoodsPricesReport.md) || ||**Periods "orderDate" and "orderUpdate" can't be specified simultaneously!** | You cannot specify the periods by the date of the order formation and by the date of the change at the same time. | Specify only one period: either by the date of formation or by the date of modification. | [POST v2/campaigns/{campaignId}/stats/orders](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders-stats/getOrdersStats.md) || ||**Without subscription, you cannot request data older than 90 days. The dateFrom ('dateFrom') is too far in the past.** | You cannot request data older than 90 days without a subscription. | Subscribe to access the data for a longer period, or specify `dateFrom` not earlier than 90 days from the current date. Read more about the subscription for sellers [in the Help of the Market for sellers](https://yandex.ru/support/marketplace/ru/marketing/subscription). | It is found in report generation methods. || ||**You cannot request data older than 400 days. The dateFrom ('dateFrom') is too far in the past.** | You cannot request data older than 400 days. | Specify `dateFrom` not earlier than 400 days from the current date. | It is found in report generation methods. || |# ### Errors when working with product reviews {#feedback} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Duplicate comment.** | There is already a comment with this text. | Do not send a comment that matches an existing one. | [POST v2/businesses/{businessId}/goods-feedback/comments/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-feedback/updateGoodsFeedbackComment.md) || ||**Illegal url in comment text.** | Links to third-party resources were found in the comment text. | Delete the links and, if necessary, add those that lead to the Market. | [POST v2/businesses/{businessId}/goods-feedback/comments/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-feedback/updateGoodsFeedbackComment.md) || |# ### Errors when dealing with product questions {#questions} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs** || ||**parentEntityId required for CREATE operation** | To create it, you need the ID of the question or answer as the parent entity. | Specify in the request `parentEntityId`. | [POST v1/businesses/{businessId}/goods-questions/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-questions/updateGoodsQuestionTextEntity.md) || ||**entityId required for UPDATE and DELETE operation** | To update and delete, you need the ID of the updated response or comment. | Specify in the request `entityId`. | [POST v1/businesses/{businessId}/goods-questions/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-questions/updateGoodsQuestionTextEntity.md) || ||**QUESTION entity type cannot be updated** | The question cannot be changed after creation.|Change the type of the entity to a reply or comment. | [POST v1/businesses/{businessId}/goods-questions/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-questions/updateGoodsQuestionTextEntity.md) || ||**Cannot create a comment on another comment.** | You can't create a comment on a comment.|Change the type of parent entity for the response. | [POST v1/businesses/{businessId}/goods-questions/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-questions/updateGoodsQuestionTextEntity.md) || |# ## 401 Unauthorized Errors {#401} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Api-Key token is invalid** | Api-Key-the token is invalid. | Check the spelling Api-Key- a token. If the error persists, get a new token. [How to do it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md) | It is found in all methods. || ||**Api-Key token is not specified** | The request does not specify Api-Key- a token. | Pass it on Api-Key-the token in the header `Api-Key` by [Instructions](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md#use). | It is found in all methods. || ||**Api-Key token length invalid** | Incorrect length Api-Key- a token. | Check the spelling Api-Key- a token. If the error persists, get a new token. [How to do it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md) | It is found in all methods. || ||**Api-Key token prefix invalid** | Incorrect prefix Api-Key- a token. | Make sure that you do not use a prefix in the header. `Bearer`. [How to transmit Api-Key-token](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md#use) If there is no prefix, check the spelling. Api-Key- a token. If the error persists, get a new token. [How to do it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md) | It is found in all methods. || ||**Api-Key token format invalid** | Incorrect format Api-Key- a token. | Check the spelling Api-Key- a token. If the error persists, get a new token. [How to do it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md) | It is found in all methods. || ||**Api-Key token is revoked** | Api-Key-the token has been deleted. | Get a new token. [How to do it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md) | It is found in all methods. || ||**Authorization header has invalid syntax** | HTTP header format `Authorization` incorrect. | Make a headline by [Instructions](https://yandex.ru/dev/market/partner-api/doc/en/concepts/oauth-2.0.md#use). | It is found in all methods. || ||**Credentials are not specified** | The authorization data is not specified in the request. | Make a heading according to the instructions: * [Api-Key-token](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md#use) * [The OAuth token](https://yandex.ru/dev/market/partner-api/doc/en/concepts/oauth-2.0.md#use) | It is found in all methods. || ||**OAuth client id is not specified** | The request did not specify the OAuth client ID (`client_id`). | Specify `client_id` your application in the header `oauth_client_id`. | It is found in all methods. || ||**OAuth credentials are not specified** | The authorization data is not specified in the request. | Make a headline `Authorization` by [Instructions](https://yandex.ru/dev/market/partner-api/doc/en/concepts/oauth-2.0.md#use). | It is found in all methods. || ||**OAuth token is not specified** | The request does not specify an OAuth authorization token. | Make a headline `Authorization` by [Instructions](https://yandex.ru/dev/market/partner-api/doc/en/concepts/oauth-2.0.md#use). | It is found in all methods. || |# ## 403 Forbidden Errors {#403} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Access denied** | Access is denied. | Check that the resource is specified correctly, as well as whether the user whose authorization token is used in the request has access rights to it. [More information about access](https://yandex.ru/dev/market/partner-api/doc/en/concepts/oauth-2.0.md) | It is found in all methods. || ||**The method is deprecated and is occasionally forbidden. Please stop using it** | The method is outdated, and some requests to it are rejected. Don't use it. | Switch to the current method specified in the documentation. The error is returned to integrations that continue to invoke the outdated method; the proportion of such responses increases over time. | It is found in all methods. || ||**API for business 'businessId' disabled because it has only disabled partners** | The cabinet API is disabled because all its stores are disabled. | Enable the API for at least one store in [the seller's account on the Market](https://partner.market.yandex.ru/business/any/api-settings). If activation is not possible, fix the reasons for disabling stores. [Detailed instructions](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-access.md#business-disabled) | It is found in all methods. || ||**API for campaign 'campaignId' disabled because it has no placement program** | The store's API is disabled because it does not have a placement program. | Complete the store's connection to the placement program in [the seller's account on the Market](https://partner.market.yandex.ru/business/any). [Detailed instructions](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-access.md#no-placement-program) | It is found in all methods. || ||**API for campaign 'campaignId' disabled because there are no active contracts with Market** | The store's API is disabled due to the lack of an active contract with Yandex.Market. | Complete the account connection in the section ["Legal data"](https://partner.market.yandex.ru/business/any) in the seller's office on the Market. [Detailed instructions](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-access.md#no-contract) | It is found in all methods. || ||**API for campaign 'campaignId' disabled due to inactivity** | The store's API is disabled due to inactivity — there were no goods in the window for a long time. | To resume working through the API, enable integration in [the seller's account on the Market](https://partner.market.yandex.ru/business/any/api-settings) and check if it is working correctly. [Detailed instructions](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-access.md#inactivity) | It is found in all methods. || ||**API for campaign 'campaignId' manually disabled** | You have turned off integration — all requests to Yandex.Market are rejected. | Enable integration in [the seller's account on the Market](https://partner.market.yandex.ru/business/any/api-settings). [Detailed instructions](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-access.md#manually-disabled) | It is found in all methods. || ||**Client id is invalid** | Invalid OAuth client ID is specified (`client_id`). | Specify `oauth_client_id` the same application that issued the token, or reissue the token to the desired client. | It is found in all methods. || ||**Contact not found for login 'login' and campaignId 'campaignId'** | The user account whose login was sent to sign the electronic acceptance certificate was not found. | Select the username of the user that is linked to the account or store. | It is found in all methods. || ||**Contacts with available roles for signing not found for login 'login'** | The user account whose login was transferred to sign the electronic acceptance certificate does not have the necessary access rights. | Provide the username of the user who is linked to the account or store and has the necessary access rights. [Access to software methodsApi-Key](https://yandex.ru/dev/market/partner-api/doc/en/concepts/access.md) | It is found in all methods. || ||**Electronic signature is only available for API token authorization.** | The electronic signature is only available when authorized by Api-Key. | Make a request with authorization by Api-Key. How to transmit Api-Key: [manual](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md#use). | [GET v2/campaigns/{campaignId}/shipments/reception-transfer-act](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentReceptionTransferAct.md)\ [POST v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/confirm](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/confirmShipment.md) || ||**No access to campaigns: 'campaigns'** | There is no access to the specified stores. | Send only campaigns belonging to the specified account (`businessId`). | It is found in all methods. || ||**No access to comment modifying.** | There is no access to edit the specified comment. | Check the correctness of the transmitted comment ID. | [POST v2/businesses/{businessId}/goods-feedback/comments/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-feedback/updateGoodsFeedbackComment.md) || ||**No access to feedback modifying.** | There is no access to modify the specified review. | Check the correctness of the transmitted review ID. | [POST v2/businesses/{businessId}/goods-feedback/comments/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-feedback/updateGoodsFeedbackComment.md) || ||**OAuth token is invalid** | The specified OAuth authorization token is invalid. | Get a new token. [How to do it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/oauth-2.0.md) | It is found in all methods. || ||**OAuth token is invalid (account has been globally logged out)**|The user used the function ["Get out everywhere"](https://yandex.ru/dev/id/doc/ru/tokens/token-invalidate) in Yandex ID.|Get a new token. [How to do it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md) | It is found in all methods. || ||**Scope is invalid** | The OAuth token was obtained through the app without access to the Market. | Get a new token. [How to do it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/oauth-2.0.md) | It is found in all methods. || ||**The method is not supported for Market Yandex Go sellers** | This method is not available for Market Yandex Go sellers. These restrictions are specified in the description of the methods. | — | It is found in all methods. || ||**The partner does not have access to the supply request.** | The partner does not have access to the delivery request. | Check the correctness of the transmitted application ID. | [POST v2/campaigns/{campaignId}/supply-requests/documents](https://yandex.ru/dev/market/partner-api/doc/en/reference/supply-requests/getSupplyRequestDocuments.md) [POST v2/campaigns/{campaignId}/supply-requests/items](https://yandex.ru/dev/market/partner-api/doc/en/reference/supply-requests/getSupplyRequestItems.md)|| ||**Token does not have any of the scopes to access the API method** | There is no access to the method. | Get access to at least one group of methods listed in the error text. [How to do it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/api-key.md) | It is found in all methods. || ||**User account is disabled** | The account of the user for whom the specified authorization token was issued is blocked. | Contact customer support. | It is found in all methods. || ||**businessId in X-Business-Id header ('headerBusinessId') does not match the business that the campaign 'campaignId' belongs to ('actualBusinessId')** | Cabinet ID in the header `X-Business-Id` does not match the account that the store belongs to. | Make sure that in the header `X-Business-Id` the ID of the cabinet to which the transmitted store ID belongs is specified. | It is found in all methods in which it is passed `campaignId`. || ||**Entity id from request body does not match businessId in X-Business-Id header ('businessId')** | The ID of the entity in the request body (`businessId`/`campaignId`) does not match the cabinet ID in the header `X-Business-Id`. | If the request body contains `businessId` then make sure it matches the value in the header `X-Business-Id`. If passed `campaignId` then make sure that the store belongs to the business referred to in the header `X-Business-Id`. | It is found in report generation methods. || |# ## 404 Not Found Errors {#404} #| ||**Report not found.** | The report or document specified in the request was not found. | Check the correctness of the transmitted ID of the report or document. | [GET v2/reports/info/{reportId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/reports/getReportInfo.md) || ||**Resource not found** | The resource was not found. | * Check the accuracy URL and the HTTP method, they can be viewed in the documentation on the method page. * Make sure that you are using the correct version of the method. [Learn more about calling methods](https://yandex.ru/dev/market/partner-api/doc/en/concepts/method-call.md) | It is found in all methods. || ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Box not found. Box: 'boxId'** | The box specified in the request was not found. | Check that the transmitted box ID is correct. | [GET v2/campaigns/{campaignId}/orders/{orderId}/delivery/shipments/{shipmentId}/boxes/{boxId}/label](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-labels/generateOrderLabel.md) || ||**Campaign not found 'campaignId'** | The campaign specified in the request was not found. | Check that the transmitted campaign ID is correct. | It is found in all cabinet methods. || ||**Can't find chat by id: 'chatId'** | The chat specified in the request was not found. | Check the correctness of the transmitted chat ID. | [GET v2/businesses/{businessId}/chats/message](https://yandex.ru/dev/market/partner-api/doc/en/reference/chats/getChatMessage.md)\ [POST v2/businesses/{businessId}/chats/message](https://yandex.ru/dev/market/partner-api/doc/en/reference/chats/sendMessageToChat.md)\ [POST v2/businesses/{businessId}/chats/history](https://yandex.ru/dev/market/partner-api/doc/en/reference/chats/getChatHistory.md) || ||**Can't find message by id: 'messageId' for chat 'chatId'** | The message specified in the request was not found in the transmitted chat. | Check the correctness of the transmitted message and chat IDs. | [GET v2/businesses/{businessId}/chats/message](https://yandex.ru/dev/market/partner-api/doc/en/reference/chats/getChatMessage.md) || ||**Failed to find ['resource'] with id ['id']** | The resource specified in the request was not found. | Check the correctness of the transmitted resource identifier (order or shipment). | [GET v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/getShipment.md) [GET v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/act](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentAct.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/delivery/track](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/setOrderDeliveryTrackCode.md) [GET v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/orders/info](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/getShipmentOrdersInfo.md) [GET v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/transportation-waybill](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentTransportationWaybill.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/verifyEac](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/verifyOrderEac.md)\ [PUT v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/pallets](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/setShipmentPalletsCount.md)\ [GET v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/pallet/labels](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/downloadShipmentPalletLabels.md)\ [POST v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/orders/transfer](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/transferOrdersFromShipment.md) || ||**Failed to find order with id 'orderId'** | The order specified in the request was not found. | Check that the transmitted order ID is correct. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/boxes](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/setOrderBoxLayout.md) || ||**Feedbacks not found.** | The reviews specified in the request were not found. | Check that the transmitted review IDs are correct. | [POST v2/businesses/{businessId}/goods-feedback/comments/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-feedback/updateGoodsFeedbackComment.md) || ||**Grade not found.** | The review was not found. | Check the correctness of the transmitted review ID. | [POST v2/businesses/{businessId}/goods-feedback/comments/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/goods-feedback/updateGoodsFeedbackComment.md) || ||**No boxes found for order 'orderId'** | No boxes were found for the order specified in the request. | Check that the transmitted order ID is correct. Make sure that you have provided information about how the goods are distributed in boxes. To do this, use the method [PUT v2/campaigns/{campaignId}/orders/{orderId}/boxes](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/setOrderBoxLayout.md). | [GET v2/campaigns/{campaignId}/orders/{orderId}/delivery/shipments/{shipmentId}/boxes/{boxId}/label](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-labels/generateOrderLabel.md) [GET v2/campaigns/{campaignId}/orders/{orderId}/delivery/labels](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-labels/generateOrderLabels.md) [GET v2/campaigns/{campaignId}/orders/{orderId}/delivery/labels/data](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-labels/getOrderLabelsData.md) || ||**Order not found: 'orderId'** | The order specified in the request was not found. | Check that the transmitted order ID is correct. | [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/deliverDigitalGoods](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/provideOrderDigitalCodes.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/delivery/date](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/setOrderDeliveryDate.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/delivery/storage-limit](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/updateOrderStorageLimit.md) [POST v2/businesses/{businessId}/chats/new](https://yandex.ru/dev/market/partner-api/doc/en/reference/chats/createChat.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/external-id](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateExternalOrderId.md) || ||**Order not found: partnerId = 'partnerId', orderId = 'orderId'** | The order specified in the request was not found. | Check that the transmitted order ID is correct. | [GET v2/campaigns/{campaignId}/orders/{orderId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/getOrder.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateOrderStatus.md) [GET v2/campaigns/{campaignId}/orders/{orderId}/delivery/shipments/{shipmentId}/boxes/{boxId}/label](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-labels/generateOrderLabel.md) [GET v2/campaigns/{campaignId}/orders/{orderId}/delivery/labels](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-labels/generateOrderLabels.md) [GET v2/campaigns/{campaignId}/orders/{orderId}/delivery/labels/data](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-labels/getOrderLabelsData.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/deliverDigitalGoods](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/provideOrderDigitalCodes.md) [GET v2/campaigns/{campaignId}/orders/{orderId}/buyer](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/getOrderBuyerInfo.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/cancellation/accept](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/acceptOrderCancellation.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/delivery/date](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-delivery/setOrderDeliveryDate.md) [PUT v2/campaigns/{campaignId}/orders/{orderId}/identifiers](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/provideOrderItemIdentifiers.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/business-buyer](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-business-information/getOrderBusinessBuyerInfo.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/documents](https://yandex.ru/dev/market/partner-api/doc/en/reference/order-business-information/getOrderBusinessDocumentsInfo.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/external-id](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/updateExternalOrderId.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/identifiers/status](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/getOrderIdentifiersStatus.md) || ||**Outlet not found: 'outletId'** | The point of sale specified in the request was not found. | Check the correctness of the transmitted point of sale identifier. | [GET v2/campaigns/{campaignId}/outlets/{outletId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/getOutlet.md) [DELETE v2/campaigns/{campaignId}/outlets/{outletId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/deleteOutlet.md) [PUT v2/campaigns/{campaignId}/outlets/{outletId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/outlets/updateOutlet.md) || ||**Region 'regionId' not found.** | The region specified in the request was not found. | Check that the transmitted region ID is correct. To get a list of all available regions, use the reference method [GET v2/regions](https://yandex.ru/dev/market/partner-api/doc/en/reference/regions/searchRegionsByName.md) | [GET v2/regions/{regionId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/regions/searchRegionsById.md)\ [GET v2/regions/{regionId}/children](https://yandex.ru/dev/market/partner-api/doc/en/reference/regions/searchRegionChildren.md) || ||**Return 'returnId' for order 'orderId' is not found** | The refund specified in the request was not found. | Check the correctness of the transmitted refund and order IDs. | [GET v2/campaigns/{campaignId}/orders/{orderId}/returns/{returnId}](https://yandex.ru/dev/market/partner-api/doc/en/reference/returns/getReturn.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/returns/{returnId}/decision](https://yandex.ru/dev/market/partner-api/doc/en/reference/returns/setReturnDecision.md) [POST v2/campaigns/{campaignId}/orders/{orderId}/returns/{returnId}/decision/submit](https://yandex.ru/dev/market/partner-api/doc/en/reference/returns/submitReturnDecision.md) || ||**Shipment with ID 'shipmentId' not found** | The shipment specified in the request was not found. | Check the correctness of the transmitted shipment ID. | [POST v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/confirm](https://yandex.ru/dev/market/partner-api/doc/en/reference/shipments/confirmShipment.md) || ||**Supply request not found.** | The application was not found. | Check the correctness of the transmitted application ID. | [POST v2/campaigns/{campaignId}/supply-requests/documents](https://yandex.ru/dev/market/partner-api/doc/en/reference/supply-requests/getSupplyRequestDocuments.md) [POST v2/campaigns/{campaignId}/supply-requests/items](https://yandex.ru/dev/market/partner-api/doc/en/reference/supply-requests/getSupplyRequestItems.md) || ||**Unknown category** | Unknown category. | Check that the transmitted category ID is correct. To find out the ID of the category to which the product you are interested in belongs, use the request [POST v2/categories/tree](https://yandex.ru/dev/market/partner-api/doc/en/reference/categories/getCategoriesTree.md). | [POST v2/category/{categoryId}/parameters](https://yandex.ru/dev/market/partner-api/doc/en/reference/content/getCategoryContentParameters.md) || |# ## Errors 405 Method Not Allowed {#405} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Request method 'method' not supported** | The requested HTTP method is not supported. | Check the methods that are supported by the resource. | It is found in all methods. || |# ## Errors 415 Unsupported Media Type {#415} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Content type 'content-type' not supported** | The requested content type is not supported. | Transmit one of the supported content types. | It is found in all methods. || ||**Unknown content-type: 'content-type'** | Requested content type — unknown. | Transmit one of the supported content types. | It is found in all methods. || |# ## Errors 420 Enhance Your Calm {#420} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Hit rate limit of 'N' parallel requests for {entity}** | Exceeded the global limit on the number of simultaneous requests to Yandex Market API. [What is it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/limits.md#global) | Reduce the number of parallel API requests for a specific entity to `N` requests. | It is found in all methods. || ||**Hit rate limit of 'N' requests per 'period' for resource 'R' for {entity}** | Exceeded the resource limit on the number of `N` resource requests `R` for the period `period` for a specific entity. [What is it](https://yandex.ru/dev/market/partner-api/doc/en/concepts/limits.md#resource)| The time limit is specified in the header. `X-RateLimit-Resource-Until`. The use of the resource will become possible after the specified time. | It is found in all methods. || ||**Active reports limit exceeded, limit='limit'** | The limit on the number of simultaneously generated reports has been exceeded. | Wait for the previous reports to be generated before creating new ones. The number of reports generated at the same time depends on your data plan. Read more about the subscription for sellers [in the Help of the Market for sellers](https://yandex.ru/support/marketplace/ru/marketing/subscription). | It is found in report generation methods. || |# ## Errors 423 Locked {#423} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Business is in migration** | Store migrations are taking place in the cabinet. | Wait for the transfer to finish. | [POST v2/businesses/{businessId}/offer-cards/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/content/updateOfferContent.md) [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) [POST v2/businesses/{businessId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updateBusinessPrices.md) [POST v2/businesses/{businessId}/price-quarantine/confirm](https://yandex.ru/dev/market/partner-api/doc/en/reference/price-quarantine/confirmBusinessPrices.md) [POST v2/campaigns/{campaignId}/price-quarantine/confirm](https://yandex.ru/dev/market/partner-api/doc/en/reference/price-quarantine/confirmCampaignPrices.md) [POST v2/campaigns/{campaignId}/offers/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/offers/updateCampaignOffers.md) [POST v2/campaigns/{campaignId}/offers/delete](https://yandex.ru/dev/market/partner-api/doc/en/reference/offers/deleteCampaignOffers.md) [POST v2/businesses/{businessId}/offer-mappings/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/updateOfferMappings.md) [POST v2/businesses/{businessId}/offer-mappings/archive](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/addOffersToArchive.md) [POST v2/businesses/{businessId}/offer-mappings/unarchive](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/deleteOffersFromArchive.md) [POST v2/businesses/{businessId}/offer-mappings/delete](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/deleteOffers.md) [POST v1/businesses/{businessId}/offer-mappings/barcodes/generate](https://yandex.ru/dev/market/partner-api/doc/en/reference/business-offer-mappings/generateOfferBarcodes.md) [POST v2/businesses/{businessId}/promos/offers/update](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/updatePromoOffers.md) [POST v2/businesses/{businessId}/promos/offers/delete](https://yandex.ru/dev/market/partner-api/doc/en/reference/promos/deletePromoOffers.md) || ||**Campaign is in business migration** | The store is in the process of being moved to another account. | Wait for the transfer to finish. | [GET v2/campaigns/{campaignId}/hidden-offers](https://yandex.ru/dev/market/partner-api/doc/en/reference/hidden-offers/getHiddenOffers.md) [POST v2/campaigns/{campaignId}/hidden-offers/delete](https://yandex.ru/dev/market/partner-api/doc/en/reference/hidden-offers/deleteHiddenOffers.md) || ||**Partner use only default price** | The cabinet uses prices for all stores. | You will not be able to set the price for a separate store. Set uniform prices for all stores in the cabinet. | [POST v2/campaigns/{campaignId}/offer-prices/updates](https://yandex.ru/dev/market/partner-api/doc/en/reference/prices/updatePrices.md) || |# ## Errors 499 Client Closed Request {#499} The error is returned when the client closes the connection before completing request processing on the Market side. Check the timeout settings and the request replay policy on the client side and repeat the call. ## Errors 500 Internal Server Error {#500} Wait for a while and call the method again. If the problem persists, contact customer support. — go to [seller's account on the Market](https://partner.market.yandex.ru/business/any/support) and press the button **Create an appeal**. ## 503 Service Unavailable Errors {#503} #| ||**Description**|**Translation**|**What to do**|**Methods in which the error occurs**|| ||**Service temporarily unavailable. Please, try again later** | The server is temporarily unavailable due to high load. | Try to repeat the request after a while. If the problem persists, contact customer support. — go to [seller's account on the Market](https://partner.market.yandex.ru/business/any/support) and press the button **Create an appeal**. | It is found in all methods. || |# ## Example of an error message {#example} Request: ```httpget translate=no GET v2/campaigns/10003/orders HTTP/1.1 Host: api.partner.market.yandex.ru Accept: */* Api-Key: ACMA:I4c4CxCSYaI41RSC2uYWP2qj3Rhhm4knMiBEga5K:151c0664a ``` Answer: ```json translate=no { "errors": [ { "code": "UNAUTHORIZED", "message": "Api-Key token is invalid" } ], "status": "ERROR" } ```