Guides
My Account
  1. Feeds

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. The API supports feed types that return item details.

For items undergoing compliance review, the response can include pendingStatusDescription with review details, editing restrictions, and the expected review timeframe.

Endpoint

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

Path parameters

Name    Type  RequiredNotes                                                                                                                                
feedIdstring     YesFeed identifier returned by the bulk upload. Percent‑encode special characters when used in a URL (for example, encode @ as %40).

Query parameters

Name            Type    DefaultNotes                                                                                      
includeDetailsbooleanfalseWhen true, returns item‑level ingestion results and enables paging.                      
offset        integer0    Zero-based start index for item results. Use only when includeDetails=true.                          
limit          integer50    Number of item detail records to return. Use only when includeDetails=true. Max 1000.

Request sample

curl --request GET \ --url "https://marketplace.walmartapis.com/v3/feeds/F129C19240844B97A3C6AD8F1A2C4997%40AU8BAQA?includeDetails=true&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 while the feed is processing. If feedStatus is INPROGRESS, poll until it changes to PROCESSED or ERROR. Suggested intervals are 15 minutes, 1 hour, 2 hours, and then every 4 hours.
  2. Handle pending compliance reviews. When an item has ingestionStatus set to INPROGRESS and pendingStatusDescription is returned, display or log the message. Edits and resubmissions cannot be processed until the compliance review is complete. The review may take up to 24 hours.
  3. Page item results. When includeDetails=true, request item details in pages using offset and limit.
  4. Convert timestamps. feedSubmissionDate is returned as epoch milliseconds in the JSON example. Convert it to ISO 8601 for logs and monitoring.
  5. Alert on failures. If itemsFailed is greater than 0, inspect itemDetails.itemIngestionStatus[] and ingestionErrors to identify affected items.
  6. Retry responsibly. Use exponential backoff for 429 and 5xx responses. Reuse the same correlation ID when retrying the same API call.

Response sample

{ "feedId": "F129C19240844B97A3C6AD8F1A2C4997@AU8BAQA", "feedStatus": "INPROGRESS", "feedSubmissionDate": 1568310803059, "itemsReceived": 1, "itemsSucceeded": 0, "itemsFailed": 0, "itemsProcessing": 1, "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": "INPROGRESS", "pendingStatusDescription": "This item is currently under review for compliance. You will not be able to edit the existing item until the compliance check is concluded. This process may take up to 24 hours." } ] }
}

Result

  • Overall feed processing status in feedStatus.
  • Item‑level statuses in itemDetails.itemIngestionStatus[] when includeDetails=true.
  • Compliance-review details in itemDetails.itemIngestionStatus[].pendingStatusDescription, when applicable.

Status values

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

Pending compliance review

The optional pendingStatusDescription field can be returned for an item with ingestionStatus set to INPROGRESS when the item is undergoing compliance review. The field explains the review status, editing restrictions, and expected review timeframe. pendingStatusDescription is an informational field and does not introduce a new item ingestion status.

While the review is in progress, edits and resubmissions cannot be processed. The review may take up to 24 hours. When the item is not undergoing compliance review, the field is typically not returned.

This is an additive response field. Existing integrations do not need to change unless they want to display or process the compliance-review message.

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

  • For supported fitment feeds, when itemsFailed > 0, download 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.
  • Detect pendingStatusDescription and notify sellers that edits and resubmissions are unavailable until the compliance review is complete.

Updated about 2 hours ago

Did this page help you?