Types of errors and what to do about them
- What do the error codes mean?
- Errors in the query content (400)
- 401 Unauthorized Errors
- 403 Forbidden Errors
- 404 Not Found Errors
- Errors 405 Method Not Allowed
- Errors 415 Unsupported Media Type
- Errors 420 Enhance Your Calm
- Errors 423 Locked
- Errors 499 Client Closed Request
- Errors 500 Internal Server Error
- 503 Service Unavailable Errors
- Example of an error message
If the store's request could not be completed, the Market returns the 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?
|
Code |
Title |
What happened and what to do |
|
|
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. |
|
|
|
The authorization token is not specified in the request (or is specified, but not there). |
|
|
|
|
|
|
|
|
|
|
|
There is no such method on the specified resource. Check the request addresses that the store's system uses. |
|
|
|
The requested content type is not supported by the method. Check the correctness of the request. |
|
|
|
The store exceeded the request limit. Make sure that your system does not send anything superfluous. |
|
|
|
The method cannot be used for this store. Focus on the error description to understand what exactly is wrong. |
|
|
|
The client closed the connection before completing the request processing on the Market side. Check the timeouts on the client side and repeat the request. |
|
|
|
Internal error of the Market. |
|
|
|
The Yandex.Market server is overloaded. |
Errors in the query content (400)
The possible causes of this error depend on the specific request. In the description of many queries, there is a section describing the 400 error options for specific data.
Some error variants with the 400 code are the same for different requests:
|
Description |
Translation |
What to do |
|
Campaign type is not allowed |
This method does not support your store's operating model. |
Make sure that you use a method that supports your store's operating model. |
|
Collection of field must not be empty |
The parameter must not be empty. |
Specify at least one element for the parameter. |
|
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. |
|
Invalid status: 'status' |
An incorrect status is specified. |
Check the correctness of the transmitted status to filter orders by status. |
|
JSON: {message} |
The JSON data format contains an error. |
Check the correctness of the JSON. |
|
Limit exceeded |
The limit on the number of values per page has been exceeded — parameter |
Reduce the number of values. |
|
Missing field |
A required parameter is not specified. |
Specify a value for the required parameter. |
|
Outlet is disabled for editing by partner |
You cannot change the information or delete the store's point of sale because you refused to deliver to the Market's pick-up points. Learn more about the shipping rules for DBS- Read the shops in the Help of the Market for sellers. |
Contact customer support if you are ready to enable delivery to the pick-up points of the Market. |
|
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. |
|
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. |
|
Too long time period. Maximum is 'maxPeriod' days |
The date range is too large. Maximum range — |
Reduce the date range to filter orders by date. |
|
Unexpected character 'character': expected a valid value 'values' |
Invalid character. |
Check the encoding of the request body. Required encoding — UTF-8. |
|
Unexpected end of content |
The request body ends unexpectedly. |
Check the correctness of the format of the data transmitted in the request body. |
|
Value / length of field (value) must be between min and max [exclusively] |
The value (length) of the parameter must be between the values |
Check the correctness of the parameter value. |
|
Value / length of field (value) must be greater / less than [or equal to limit] |
The value (length) of the parameter must be equal to or greater than (less than) the specified value. |
Check the correctness of the parameter value. |
|
Value of field has too high scale: 'price' |
The accuracy is set too high for the parameter. |
Set the parameter value with less precision. |
|
Value of field must match the pattern: 'regExp' |
The parameter value must match a regular expression. |
Check the correctness of the parameter value. |
401 Unauthorized Errors
|
Description |
Translation |
What to do |
|
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 |
|
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 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 |
|
Api-Key token prefix invalid |
Incorrect prefix Api-Key- a token. |
Make sure that you do not use a prefix in the header. If there is no prefix, check the spelling. Api-Key- a token. If the error persists, get a new token. How to do it |
|
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 |
|
Api-Key token is revoked |
Api-Key-the token has been deleted. |
Get a new token. How to do it |
|
Authorization header has invalid syntax |
HTTP header format |
Make a headline by Instructions. |
|
Credentials are not specified |
The authorization data is not specified in the request. |
Make a heading according to the instructions: |
|
OAuth client id is not specified |
The request did not specify the OAuth client ID ( |
Specify |
|
OAuth credentials are not specified |
The authorization data is not specified in the request. |
Make a headline |
|
OAuth token is not specified |
The request does not specify an OAuth authorization token. |
Make a headline |
403 Forbidden Errors
|
Description |
Translation |
What to do |
|
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 |
|
Access denied for business 'businessId' because it is not active |
The method is unavailable due to account inactivity. |
Fix the errors that prevent the goods from being returned to the showcase. If you need API access for this, contact customer support. — go to seller's account on the Market and press the button Create an appeal. |
|
Access denied for campaign 'campaignId' because it is not active |
The method is unavailable due to store inactivity. |
The option to use the API shows the parameter Fix the errors that prevent the goods from being returned to the showcase. If you need API access for this, contact customer support. — go to seller's account on the Market and press the button Create an appeal. |
|
Client id is invalid |
Invalid OAuth client ID is specified ( |
Specify |
|
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. |
|
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 |
|
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. |
|
No access to campaigns: 'campaigns' |
There is no access to the specified stores. |
Send only campaigns belonging to the specified account ( |
|
No access to comment modifying. |
There is no access to edit the specified comment. |
Check the correctness of the transmitted comment ID. |
|
No access to feedback modifying. |
There is no access to modify the specified review. |
Check the correctness of the transmitted review ID. |
|
OAuth token is invalid |
The specified OAuth authorization token is invalid. |
Get a new token. How to do it |
|
OAuth token is invalid (account has been globally logged out) |
The user used the function "Get out everywhere" in Yandex ID. |
Get a new token. How to do it |
|
Scope is invalid |
The OAuth token was obtained through the app without access to the Market. |
Get a new token. How to do it |
|
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. |
|
The method is not supported for Market Yandex Go sellers |
This method is not available for Yandex Go Market sellers. These restrictions are specified in the description of the 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. |
|
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 |
|
User account is disabled |
The account of the user for whom the specified authorization token was issued is blocked. |
Contact customer support. |
404 Not Found Errors
|
Description |
Translation |
What to do |
|
Box not found. Box: 'boxId' |
The box specified in the request was not found. |
Check that the transmitted box ID is correct. |
|
Campaign not found 'campaignId' |
The campaign specified in the request was not found. |
Check that the transmitted campaign ID is correct. |
|
Can't find chat by id: 'chatId' |
The chat specified in the request was not found. |
Check the correctness of the transmitted chat ID. |
|
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. |
|
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). |
|
Failed to find order with id 'orderId' |
The order specified in the request was not found. |
Check the correctness of the transmitted order ID. |
|
Feedbacks not found. |
The reviews specified in the request were not found. |
Check that the transmitted review IDs are correct. |
|
Grade not found. |
The review was not found. |
Check the correctness of the transmitted review ID. |
|
No boxes found for order 'orderId' |
No boxes were found for the order specified in the request. |
Check the correctness of the transmitted order ID. 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. |
|
Order not found: 'orderId' |
The order specified in the request was not found. |
Check the correctness of the transmitted order ID. |
|
Order not found: partnerId = 'partnerId', orderId = 'orderId' |
The order specified in the request was not found. |
Check the correctness of the transmitted order ID. |
|
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. |
|
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 |
|
Report not found. |
The report or document specified in the request was not found. |
Check that the transmitted ID of the report or document is correct. |
|
Resource not found |
The resource was not found. |
|
|
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. |
|
Shipment with ID 'shipmentId' not found |
The shipment specified in the request was not found. |
Check the correctness of the transmitted shipment ID. |
|
Supply request not found. |
The application was not found. |
Check the correctness of the transmitted application ID. |
|
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. |
Errors 405 Method Not Allowed
|
Description |
Translation |
What to do |
|
Request method 'method' not supported |
The requested HTTP method is not supported. |
Check the methods that are supported by the resource. |
Errors 415 Unsupported Media Type
|
Description |
Translation |
What to do |
|
Content type 'content-type' not supported |
The requested content type is not supported. |
Transmit one of the supported content types. |
|
Unknown content-type: 'content-type' |
Requested content type — unknown. |
Transmit one of the supported content types. |
Errors 420 Enhance Your Calm
|
Description |
Translation |
What to do |
|
Hit rate limit of 'N' parallel requests |
Exceeded the global limit on the number of simultaneous requests to Yandex Market API for sellers. What is it |
Reduce the number of parallel API requests within a single cabinet or store to |
|
Hit rate limit of 'N' requests per 'period' for resource 'R' |
Exceeded the resource limit on the number of |
The time limit is specified in the header. |
Errors 423 Locked
|
Description |
Translation |
What to do |
|
Business is in migration |
Store migrations are taking place in the cabinet. |
Wait for the transfer to finish. |
|
Campaign is in business migration |
The store is in the process of being moved to another account. |
Wait for the transfer to finish. |
|
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. |
Errors 499 Client Closed Request
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
Wait for a while and call the method again. If the problem persists, contact customer support. — go to seller's account on the Market and press the button Create an appeal.
503 Service Unavailable Errors
|
Description |
Translation |
What to do |
|
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 and press the button Create an appeal. |
Example of an error message
Request:
GET /campaigns/10003/orders HTTP/1.1
Host: api.partner.market.yandex.ru
Accept: */*
Api-Key: ACMA:I4c4CxCSYaI41RSC2uYWP2qj3Rhhm4knMiBEga5K:151c0664a
Answer:
{
"errors": [
{
"code": "UNAUTHORIZED",
"message": "Api-Key token is invalid"
}
],
"status": "ERROR"
}
The store is disabled because it has not placed products in the showcase for more than 90 days.
There is not a single active store in the cabinet.
The store is disabled because it has not placed products in the showcase for more than 90 days.
All stores in the office are disabled, as they have not placed goods in the window for more than 90 days.