The following is a list of known issues or limitations for the Catalog API:

• API calls may not be made while Store Editor is publishing. Attempts to make API calls while Store Editor is publishing will result in the following error message: 10601=Your Store Editor is currently publishing. While this publish is in progress, you cannot use the Catalog API. Once publishing is complete, you may continue to use it.

• API calls may not be made while the maximum numbers of processes (6 processes) are occurring in Store Editor or Catalog Manager. Attempts to make API calls when the maximum number of processes has been reached will result in the following error message: 10600=The maximum number of Store Editor or Catalog Manager processes has been reached, and your request cannot be performed at this time. Please try your request again later.

• API calls will be queued when an action that will take an extended period of time to complete is in process in Store Editor or Catalog Manager. APIs calls made during this type of event will result in the following error message: 10602= An action in Store Editor or Catalog Manager is currently in progress, and may take an extended period of time to complete. Your API call may be queued. To check on the status of your API call, please wait for a period of time and perform a "get" request.

• Multiple values for the same attribute are not detected. When multiple values appear, only the last element is inspected. In the example below, two values are given for the <GiftCert> attribute, but only the last one is detected.
  
  <Item>
  <ID>autoitem1</ID>
  <GiftCert>yes </GiftCert>
  <Name>autoitem1</Name>
  <GiftCert>no</GiftCert>
  <TableId>custom-allattr</TableId>
  </Item>
   

• Responses for calls missing the store ID, security header, partner token, and/or resource list do not include the field name of the missing information. Instead, the response will contain the following:
  
  <?xml version="1.0" encoding="utf-8"?>
  <ystorewsResponse>
  <ErrorMessages>
  <Error>
  <Code> 10400 </Code>
  <Message> Bad request or missing tags </Message>
  </Error>
  </ErrorMessages>
  </ystorewsResponse>
   

• When non-ASCII special characters are updated using the Catalog API, these characters must be sent in the XML request using their HTML entity. Below is an example of how to include the copyright symbol in a request for an item named "test 1 ©":
  
  <ID>createAPIs2</ID>
  <Name>test 1 &amp;copy; </Name>
  <Price>12</Price>
  
  In this example, the HTML entity &amp;copy; is used for the copyright symbol ©. Please note that the symbol (in this case, ©) will not display in its symbol format in Catalog Manager. When the correct entity is used, the symbol will display in its expected symbol format in Store Editor and on the published pages on your live site.