Ошибка error description

If an error occurs, the request processing stops, and the server returns an HTTP response code that identifies the error. In addition to the code, the response contains a short error description.

The error message is returned in the format specified in the request URL after the method name or in the Accept HTTP header.

The error description is passed in the error parameter. This parameter contains the error code (the code parameter) and a short error description (the message parameter).

• For the 400 Bad Request error:

  Description	Explanation	Possible solution
  Collection of field must not be empty	The parameter must not be empty.	Specify at least one element for the parameter.
  Invalid status: 'status'	Invalid status is specified.	Check if the sent status is correct for order filtering by status.
  JSON: {message}	The JSON data format contains an error.	Check if the data passed in the request body has the correct JSON format.
  Missing field	The required parameter isn’t specified.	Specify a value for the required parameter.
  The request is too big	The HTTP request size limit is exceeded.	Cut the request size by reducing the amount of the sent data.
  Too long time period. Maximum is 'maxPeriod' days	The specified date range is too large. Maximum range — maxPeriod.	Reduce the date range to filter orders by date.
  Unexpected character 'character': expected a valid value 'values'	Invalid character.	Check the request body encoding. The required encoding is UTF-8.
  Unexpected end of content	The request body ends unexpectedly.	Check if the data passed in the request body has the correct format.
  Value / length of field (value) must be between min and max [exclusively]	The parameter value (length) must be between the min and max values and not equal to them.	Check if the parameter value is correct.
  Value / length of field (value) must be greater / less than [or equal to] limit	The parameter value (length) must be equal to or greater than (less than) the specified limit value.	Check if the parameter value is correct.
  Value of field has too high scale: 'price'	The accuracy of the parameter is set too high.	Set the parameter values with less precision.
  Value of field must match the pattern: 'regExp'	The parameter value must match the regular expression.	Check if the parameter value is correct.
  XML: {message}	The XML data format contains an error.	Check if the data passed in the request body has the correct XML format.

  Other short descriptions that can be found in messages about this error are provided in the descriptions of the corresponding resources.

• For the 401 Unauthorized error:

  Description	Explanation	Possible solution
  Unsupported authorization type specified in Authorization header	Authorization type passed in the Authorization HTTP header isn’t supported.	Check if the authorization data is correct.
  Authorization header has invalid syntax	The Authorization HTTP header format is incorrect.	Check if the authorization data is correct.
  OAuth credentials are not specified	The request doesn’t include authorization data.	Check that the authorization data is correct.
  OAuth token is not specified	The request doesn’t include the authorization token (the oauth_token parameter).	Check if the authorization data is correct.
  OAuth client id is not specified	The request doesn’t include the application ID (the oauth_client_id parameter).	Check if the authorization data is correct.

• For the 403 Forbidden error:

  Description	Explanation	Possible solution
  Access denied	Access to the specified resource is prohibited.	Check if the resource is specified correctly, and if the authorized user login has access to it.
  Access to API denied for the client / campaign	The client or store isn’t allowed to access the Yandex.Market Partner API.	Agency clients should contact their agency about getting access to the Yandex.Market Partner API.
  Client id is invalid	The specified application ID (the oauth_client_id parameter) is invalid.	Check if the authorization data is correct. If they are correct, get a new app ID, repeat the request with the new authorization data.
  Scope is invalid	The specified authorization token (the oauth_token parameter) doesn’t have the necessary set of rights.	Get a new authorization token, mention the right to use the Yandex.Market Partner API when you receive it, and repeat the request with the new authorization data.
  Token is invalid	The specified authorization token (parameter oauth_token) is invalid.	Check if the authorization data is correct. If they are correct, get a new authorization token, repeat the request with the new authorization data.
  User account is disabled	The user account for which the specified authorization token was issued is blocked.	Contact the Yandex.Market support service.

• For the 404 Not Found error:

  Description	Explanation	Possible solution
  Feed not found: 'feedId'	The price list specified in the request isn’t found.	Check if the sent price list ID is correct.
  Login not found: 'login'	The username specified in the request isn’t found.	Check if the sent username is correct.
  Model not found: 'modelId'	The model specified in the request isn’t found.	Check if the model ID you are passing is correct.

• For the 405 Method Not Allowed error:

  Description	Explanation	Possible solution
  Request method 'method' not supported	The requested HTTP method isn’t supported.	Check the methods supported by the resource. You can find the list of methods in the Requests reference section.

• For the 415 Unsupported Media Type error:

  Description	Explanation	Possible solution
  Content type 'content-type' not supported	The requested content type isn’t supported.	Pass one of the supported content types.
  Missing Content-Type	The content type isn’t specified.	Pass the content type.
  Unknown content-type: 'content-type'	The requested content type is unknown.	Pass one of the supported content types.

• For the 420 Enhance Your Calm error:

  Description	Explanation	Possible solution
  Hit rate limit of 'N' parallel requests	Exceeded the global limit on the number of simultaneous requests to the Yandex.Market Partner API.	Reduce the number of concurrent requests to the partner API within a single store or partner to N requests.
  Hit rate limit of 'N' requests per 'period' for resource 'R'	The resource restriction for the N number of requests to the R resource over the period for the same store or partner is exceeded.	The time until which the limit applies is specified in the X-RateLimit-Resource-Until header. You can use of the resource after the specified time.

• For the 503 Service Unavailable error:

  Description	Explanation	Possible solution
  Service temporarily unavailable. Please, try again later	The server is temporarily unavailable due to high load.	Try repeating the request after a while.