📘

Buy with Prime API is now available for early access

Sign up for early access to the Buy with Prime API using the 'Sign Up' button below. The API may change as Amazon receives feedback and iterates on it.

Sign Up

This topic explains possible errors that you can encounter when you work with the Buy with Prime Catalog interface.

Catalog feed errors

You can encounter the following errors when you upload your catalog by using a catalog feed. For examples of working with catalog feeds, see Upload a Catalog and Get the Result of a Catalog Upload.

Errors creating an upload link

The following errors can occur when you call the createUploadLink mutation.

Errors uploading a catalog feed file

The following HTTP errors can occur when you upload your catalog feed file to the presigned URL that you created by using the createUploadLink mutation.

Errors starting catalog feed processing

The following errors can occur when you call the createCatalogFeed mutation to start catalog feed processing.

Errors getting the catalog feed

The following errors can occur when you call the catalogFeed query to get the status of a catalog feed.

Errors getting the download link

The following errors can occur when you call the downloadLink query to get a presigned URL with which you can download a catalog feed processing result file.

Errors downloading a catalog feed results file

The following HTTP errors can occur when you download a catalog feed results file from the presigned URL that you retrieved by using the downloadLink query.

Errors processing the catalog feed (as shown by the catalogFeed query response)

It’s possible for the entire catalog feed creation operation to fail. For example, if you upload a file that doesn’t follow the CSV template format, catalog feed creation fails entirely.

You can determine whether an entire catalog feed creation failed by using the catalogFeed query. In the response, check the status field. If the status is FAULTED, there has been an internal server error. If the status is FAILED, you can find additional details about the failure in the data.catalogFeed.result.signals field. Signals are a form of feedback that indicate that something needs attention and requires action by you.

{
  "data": {
    "catalogFeed": {
      "id": "example-catalog-feed-id",
      "status": "FAILED",
      "result": {
         "signals": [
          {
            "code": "InvalidFileId",
            "signalMessage": {
              "locale": "en-US",
              "message": "Input file id invalid or not found."
            },
            "impactSummary": {
              "locale": "en-US",
              "message": "The catalog feed could not be imported."
            },
            "reactionSummary": {
              "locale": "en-US",
              "message": "Ensure you're passing the fileId that's returned from calling CreateUploadLink and uploading a CSV file."
            }
          }
         ],
         "resultFile": null
      }
    }
  }
}

A signal contains the following information:

• A signal code, which uniquely indicates what type of signal it is. You can use the signal code to triage signals and take corresponding actions.
• A signal message, which is a human-readable message that describes the signal.
• An impact summary, which is a human-readable message that summarizes the impacts of the signal.
• A reaction summary, which is a human-readable message that describes the possible next steps to address the signal.

The following table shows some common signals that you might see in the catalogFeed query response when the catalog feed operation failed entirely.

Errors processing the catalog feed (as shown by the catalog feed results file)

After the Buy with Prime API successfully processes a catalog feed CSV file, the response to the catalogFeed query shows a status field value of COMPLETED. This value indicates that we were able to process the CSV file, but row processing wasn't necessarily all successful.

To return the row-level results of the import, the catalog field creation operation builds a catalog feed processing result file. To get a presigned URL at which you can download the result file, pass the catalog feed's result.resultReport.fileId to the downloadLink query. The downloadLink query returns a link that you can use to download the result file. For instructions on how to download the file, see Get the Result of a Catalog Upload.

The result file is similar to the input CSV file, with the following new columns:

• The Import Result column indicates the SUCCEEDED, SKIPPED, or FAILED status of the row.
• The Error Type, Error Code(s), and Error Details(s) columns describe the error when the Import Result is FAILED.

For a description of the fields in the catalog feed result file, see Catalog feed processing result file.

Product creation/update/deletion/query errors

You can encounter the following errors when you create, update, delete, and query products in your Buy with Prime catalog. For examples of these operations, see Create and Manage Products in a Catalog and Query a Catalog.

Errors creating and updating products

The following errors can occur when you call the createProduct and updateProduct mutations.

Duplicate ID errors

External ID, SKU, and Amazon SKU attributes must all be unique within a catalog. When you upload catalog data, a common error is to swap the SKU, Amazon SKU, or External ID between two products. For example, you might have the following two products:

• Product 1: External ID is external-id-1, SKU is sku-1, and Amazon SKU is amazon-sku-1
• Product 2: External ID is external-id-2, SKU is sku-2, and Amazon SKU is amazon-sku-2

If you erroneously upload a CSV file that specifies that the Amazon SKU for Product 1 is amazon-sku-2 and the Amazon SKU for Product 2 is amazon-sku-1, the catalog feed creation operation that adds these products would succeed. However, if you try to correct the mapping by directly swapping these Amazon SKU values in a subsequent catalog feed creation operation, the operation would fail with a uniqueness error.

To resolve this error, you must update one product to have an Amazon SKUs that's a third, unrelated value. In this example, you might pick UNRELATED as an unrelated Amazon SKU value that's neither amazon-sku-1 nor amazon-sku-2. This action frees the Amazon SKU for the first product so that it can be mapped to the second product. As a result, you can update the second product to use the now-free, correct Amazon SKU. After you update the second product, you can update the first product again to map it to the correct Amazon SKU.

Errors deleting a product

The following errors can occur when you call the deleteProduct mutation.

Errors querying an inventory item

The following errors can occur when you call the inventoryItem query.

Errors querying a product

The following errors can occur when you call the product query.

Related topics

• Catalog Interface
• Catalog Interface Examples
• Best Practices for Catalogs