AutomationHub: What do I do if I receive a Catalog error?

Don’t forget to vote up 👍 or down 👎 if this content was useful for you.
Dear Forums Community,
Today, I'd like to discuss what steps to take when encountering errors while using the catalog API.
There are two main categories of errors you might encounter:
1. ASIN Errors (related to the content of the product in our catalog)
2. Errors in the API Call (related to the content of the API request)
If you're a developer of a third-party application user and encounter errors like catalog matching conflicts or catalog internal errors that are specifically tied to ASIN, the initial action should be for the account owner to reach out to Seller Support. This allows our Catalog team to collaborate with the Seller, conduct thorough research, and troubleshoot to resolve the ASIN-related issue.
When the issue pertains to problems such as Feed processing errors, XSD or XML validation errors, or invalid inputs within the API call itself, such as errors 403, 404, 500, and so on, we recommend contacting our specialized Developer Support department here. When reaching out, please provide the following details:
- Full Request and Full Response (attached in two separate TXT files, including the header and the body)
- As applicable: report or feed ID / order IDs / ASIN/SKUs
- merchant ID and marketplace ID in the request
- Application ID used to submit the request
- API and operation called in the request
- The Timestamp (available in the request)
- The Request ID (available in the response)
This information will help our Developer Support team efficiently address and assist in resolving the API call-related issue.
Let us know if you find this information useful and if you would like to continue reading about this topic.
AutomationHub: What do I do if I receive a Catalog error?

Don’t forget to vote up 👍 or down 👎 if this content was useful for you.
Dear Forums Community,
Today, I'd like to discuss what steps to take when encountering errors while using the catalog API.
There are two main categories of errors you might encounter:
1. ASIN Errors (related to the content of the product in our catalog)
2. Errors in the API Call (related to the content of the API request)
If you're a developer of a third-party application user and encounter errors like catalog matching conflicts or catalog internal errors that are specifically tied to ASIN, the initial action should be for the account owner to reach out to Seller Support. This allows our Catalog team to collaborate with the Seller, conduct thorough research, and troubleshoot to resolve the ASIN-related issue.
When the issue pertains to problems such as Feed processing errors, XSD or XML validation errors, or invalid inputs within the API call itself, such as errors 403, 404, 500, and so on, we recommend contacting our specialized Developer Support department here. When reaching out, please provide the following details:
- Full Request and Full Response (attached in two separate TXT files, including the header and the body)
- As applicable: report or feed ID / order IDs / ASIN/SKUs
- merchant ID and marketplace ID in the request
- Application ID used to submit the request
- API and operation called in the request
- The Timestamp (available in the request)
- The Request ID (available in the response)
This information will help our Developer Support team efficiently address and assist in resolving the API call-related issue.
Let us know if you find this information useful and if you would like to continue reading about this topic.