Skip to content
  • There are no suggestions because the search field is empty.

Ingram Micro - Common Errors

Connection Notes

  • When switching the environment (Test/Production) there is a different API Client ID and API Client Secret

Connection Error 

  • Error: "API Call to priceandavailability - 1603467 product authorized: false, product status code: E (expected: S,W ..." followed by "API Call to priceandavailability: Failed (Unexpected status code or product not authorized). Please try a different test SKU."
    • Cause: The Ingram API is returning that you do not have access to Ingram Product ID 1603467
      • 1603467 is the product Spark Shipping checks when the Test SKU field is left blank. The connection passes when Ingram reports the product as authorized for your account, or returns a product status of S or W.
    • Solution:
      • Go to the Ingram portal to find an Ingram Part Number that you have access to
      • Update the Test SKU under credentials
  • Error: "The customer number provided on the API call does not match the registered customer number"
    • Cause: This message is coming from Ingram Micro. It says that the Customer Number you entered in your credentials does not match the Customer Number associated with your account. 
    • Solution: Contact your Ingram Micro Account Rep for your correct Customer Number.
  • Error: "Invalid API call as no apiproduct match found"
    • Cause 1: Your API Client ID does not have Approved access to the Ingram API
    • Solution 1: 
    • Cause 2: You do not have access to the Test SKU.
    • Solution 2: 
      • Contact your Ingram Representative and request test SKUs
      • Enter that SKU into the Test SKU field
  • Error: "Invalid shipping address. Please contact Ingram for more details" 
    (400 - {"errors":[{"id":"68015dc6-900a-4f0d-b87e-d3bbef4c7a28-bw0a10jqhp-2025-09-23T11:51:41.109-07:00","type":"/errors/validation-failed","message":"ERROR-SHIP-TO"}]})
    • Cause: This error usually means that the address provided on the transaction does not match what’s on USPS.
      • Example: buyer put their name in the “Company” field. Ingram requires the street address in addressline1, so the order failed validation.
    • Solution: Update the shipping address (check name, company, and full address) 
      • Ensure the actual street address (e.g., 650 Graham Road) is always in addressline1.

      • If no company name exists, leave the “Company” field blank or repeat the street address.

      • Re-send the PO once corrected.

Catalog Errors

These messages appear in the Test Connection log. Inventory and orders use the API, but the Ingram catalog (price file) is downloaded over FTP.

  • Log message: "SFTP - no credentials provided: Catalog not supported."
    • Cause: The FTP Username and FTP Password under credentials are blank.
    • Solution: Enter the FTP credentials Ingram Micro gave you and click Test Connection again. Learn more -> Ingram Micro - Credentials
  • Log message: "... file not found. Catalog not supported."
    • Cause: The FTP login works, but your price file is not where Spark Shipping expects it.
    • Solution: Confirm with Ingram Micro that your price file has been set up using the Price File Design Form, then test the connection again. If it still cannot be found, contact support@sparkshipping.com.
  • Log message: "SFTP ERROR: ... Catalog not supported."
    • Cause: Spark Shipping could not log in to the Ingram FTP server.
    • Solution: Check the FTP Username, FTP Password and Country under credentials.

Other Order Errors

  • Error: "Not Available for Backorder. Please contact Ingram for more details"
    • Cause: Ingram cannot backorder the item for your account.
  • Error: "SKU not found. Please contact Ingram for more details"
    • Cause: Ingram does not recognize the Vendor SKU sent on the order. Check the Vendor SKU mapped to the product.
  • Error: "Validation error. Please contact Ingram for more details"
    • Cause: Ingram rejected part of the order data. The text in parentheses after the message shows Ingram's response.
  • Error: Invalid third party freight account number
    • Cause: Ingram rejected the third party freight account number entered in Options. Check the number or leave the field blank.
  • Error: "Ingram rate limit reached. Please try again later"
    • Cause: Too many requests were sent to Ingram in a short time. Re-send the order later.
  • Error: Internal system error ("Please try again later or contact Ingram for more details")
    • Cause: Ingram's system returned an error. Re-send the order later.
  • Accounts still on the older Ingram API (with Enable API v6 unchecked) can also see "restricted SKU for this Ingram account", "Ingram will not sell these SKUs to this account" and "Ingram is temporarily unavailable. Please try again later". The first two need your Ingram Account Rep.