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 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 of errors (parameter message
).
If there are too many errors with a certain code, you will receive a notification about it in your account.
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. |
|
|
Internal error in Yandex. 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 queries:
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. |
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. Read more about the delivery rules for DBS stores. 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 size of the content 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. The required encoding is 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 |
The Api Key token is invalid. |
Check the spelling of the Api Key token. If the error persists, get a new token. How to do it |
Api-Key token is revoked |
The Api Key token has been deleted. |
Get a new token. How to do it |
Api-Key token format invalid |
The Api Key token format is incorrect. The prefix and length of the token are correct. |
Check the spelling of the Api Key token. If the error persists, get a new token. How to do it |
Api-Key token length invalid |
Incorrect length of the Api Key token. |
Check the spelling of the Api Key token. If the error persists, get a new token. How to do it |
Api-Key token prefix invalid |
Incorrect prefix of the Api Key token. |
Make sure that you do not use a prefix in the header. If there is no prefix, check the spelling of the Api Key token. If the error persists, 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 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 |
Unsupported authorization type specified in Authorization header |
The type of authorization transmitted in the HTTP header |
Make a headline by Instructions. |
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 to API denied for the client / campaign |
Access to the Yandex Market API is prohibited for sellers. |
Contact your agency to provide access to the API. |
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 methods by Api Key |
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 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. |
— |
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 |
Campaign not found: 'campaignId' |
The campaign specified in the request was not found. |
Check that the transmitted campaign ID is correct. |
Login not found: 'login' |
The username specified in the request was not found. |
Check the correctness of the transmitted username. |
Model not found: 'modelId' |
The model specified in the request was not found. |
Check that the transmitted model ID is correct. |
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. |
Missing Content-Type |
The content type is not specified. |
Pass the content type. |
Unknown content-type: 'content-type' |
The requested content type is 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 |
The global limit on the number of simultaneous requests to the Yandex.Market API for sellers has been exceeded. 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 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"
}