Feed item status API for tracking fitment files

Use the Feed item status API to get the feed status and item‑level ingestion status for a specific feed. Supports ACES and PIES fitment feeds and other feed types that return item details.

Endpoint

GET https://marketplace.walmartapis.com/v3/feeds/{feedId}

Path parameters

NameTypeRequiredNotes
feedIdstringYesFeed identifier returned by the bulk upload. Percent‑encode special characters when used in a URL (for example, encode @ as %40).

Query parameters

NameTypeDefaultNotes
includeDetailsbooleanfalseWhen true, returns item‑level ingestion results and enables paging.
offsetinteger0Start index for item results. Use only when includeDetails=true.
limitinteger50Number of item results to return. Use only when includeDetails=true. Max 1000.

Request sample

curl --request GET \ --url "https://marketplace.walmartapis.com/v3/feeds/F129C19240844B97A3C6AD8F1A2C4997%40AU8BAQA?includeDetails=false&offset=0&limit=50" \ --header "WM_SEC.ACCESS_TOKEN: <ACCESS_TOKEN>" \ --header "WM_QOS.CORRELATION_ID: 123e4567-e89b-12d3-a456-426614174000" \ --header "WM_SVC.NAME: Walmart Marketplace" \ --header "Accept: application/json"

Modify your code

  1. Poll when INPROGRESS. If feedStatus is INPROGRESS, poll until it changes to PROCESSED or ERROR. Suggested intervals: 15 minutes, 1 hour, 2 hours, then every 4 hours.
  2. Page item results. When includeDetails=true, request items in pages using offset and limit (max 1000).
  3. Convert timestamps. feedSubmissionDate is epoch milliseconds. Convert to ISO 8601 in logs.
  4. Alert on failures. If itemsFailed > 0, inspect itemDetails.itemIngestionStatus[] and the ingestionErrors object to triage.
  5. Retry responsibly. Use exponential backoff for 429 and 5xx. Keep the same correlation ID for retries of the same call.

Response sample

{ "feedId": "F129C19240844B97A3C6AD8F1A2C4997@AU8BAQA", "feedStatus": "PROCESSED", "feedSubmissionDate": 1568310803059, "itemsReceived": 1, "itemsSucceeded": 1, "itemsFailed": 0, "itemsProcessing": 0, "offset": 0, "limit": 20, "itemDetails": { "itemIngestionStatus": [ { "martId": 0, "sku": "0960B3B82687490FA5E51CB0801478A4@AU8BAgA", "wpid": "71ZLHHMKNS6G", "index": 0, "itemid": "51681142", "productIdentifiers": { "productIdentifier": [ { "productIdType": "GTIN", "productId": "00363824587165" }, { "productIdType": "UPC", "productId": "363824587165" } ] }, "ingestionStatus": "SUCCESS" } ] }
}

Result

  • High‑level feed status in feedStatus.
  • Item‑level statuses in itemDetails.itemIngestionStatus[] when includeDetails=true.

Status values

  • Feed status: RECEIVED | INPROGRESS | PROCESSED | ERROR.
  • Item ingestion status: SUCCESS | INPROGRESS | DATA_ERROR | SYSTEM_ERROR | TIMEOUT_ERROR.

Fitment‑specific errors (ACES/PIES)

The following file‑level errors may be returned for fitment feeds.

  • FITMENT_ERROR_001 Zip file is empty or corrupted. Fix and upload again. Refer to the knowledge base article for more information.
  • FITMENT_ERROR_002 No XML ACES file in the zip. Include an ACES XML and retry. Refer to the knowledge base article for more information.
  • FITMENT_ERROR_003 Missing Brand AAIA ID in the XML. Add the ID and retry.
  • FITMENT_ERROR_004 No XML PIES file in the zip. Include a PIES XML and retry. Refer to the knowledge base article for more information.
  • FITMENT_ERROR_005 Multiple Brand AAIA IDs found. Only one is allowed per XML.
  • FITMENT_ERROR_006 Excel header format is incorrect. Upload a file with the correct headers. Refer to the knowledge base article: article for more information.
  • FITMENT_ERROR_007 Excel contains formulas. Remove formulas and retry. Refer to the knowledge base article: article for more information.
  • FITMENT_ERROR_008 Excel contains newline characters in cells. Remove them and retry. Refer to the knowledge base article: article for more information.
  • FITMENT_ERROR_009 Internal system error during processing. Try again later.
  • FITMENT_ERROR_010 Upload request is missing a file. Attach the file and retry. Refer to the knowledge base article for more information.
  • FITMENT_ERROR_011 Upload request is missing the ingestion type (ACES or PIES). Include it and retry. Refer to the knowledge base article for more information.
  • FITMENT_ERROR_012 Upload file is missing a file name. Provide a file name and retry. Refer to the knowledge base article for more information.
  • FITMENT_ERROR_013 Upload file name is not a .zip. Use a .zip file name. Refer to the knowledge base article for more information.
  • FITMENT_ERROR_014 Upload request is missing User ID.
  • FITMENT_ERROR_015 Upload request is missing User Name.

Next steps

  • When itemsFailed > 0, fetch the error report and correct affected items before resubmitting.
  • Add monitoring that alerts on sustained DATA_ERROR and SYSTEM_ERROR rates.
  • Archive request and response payloads with the correlation ID for support.