Fitment error report download

Use the Get Error Download API to download a detailed error report for a submitted feed. Currently supported feed types are FITMENT_ACES and FITMENT_PIES.

If the submitted feed fails to process or is processed without ingestion errors, the API returns 204 No Content with an empty body.

If the submitted feed is processed with ingestion errors, the API returns 200 OK and a zipped CSV that contains line‑item error messages.

Refer to the samples for how to request and save the file.

Endpoint

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

Path parameters

Name	Type	Required	Notes
`feedId`	string	Yes	Identifier returned by the bulk upload. Percent‑encode special characters in URLs (encode `@` as `%40`).

Query parameters

Name	Type	Required	Allowed values	Notes
`feedType`	string	Yes	`FITMENT_ACES`	`FITMENT_PIES`	Feed type for which to download the error report.

Request sample

curl --request GET \ --url "https://marketplace.walmartapis.com/v3/feeds/F129C19240844B97A3C6AD8F1A2C4997%40AU8BAQA/errorReport?feedType=FITMENT_ACES" \ --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/octet-stream" --output fitment_aces_error_report.zip

The response is a zip file that contains a CSV with per‑item errors. Use --output to save the file.

Modify your code

Check feed status first. Call the Feed Item Status API and ensure the feedStatus is PROCESSED before requesting the error report.
Handle 204 No Content. If no ingestion errors exist, the API returns 204 with an empty body; do not retry.
Stream downloads. Save the payload to disk or cloud storage. Avoid loading the entire file into memory for large reports.
Parse CSV. Expect columns that identify the item (for example, SKU, WPID, index) and error fields (type, code, description).
Note: Column names can vary by feed type.
Retry responsibly. Use exponential backoff for transient 429/5xx responses. Keep the same correlation ID across retries.

Responses

HTTP status	Meaning	Body	Notes
`200 OK`	Error report available	`application/octet-stream` (zip containing a CSV)	May include `Content‑Disposition` with a suggested filename.
`204 No Content`	No ingestion errors	none	Returned when the feed had no item‑level errors or the feed did not reach item ingestion.
`400/401/403/404/429/5xx`	Error	JSON error envelope	See error model below.

Error model (JSON)

When a call fails, the API returns the standard error envelope.

Field	Type	Notes
`errors[]`	array	Present on validation or system errors.
`errors[].code`	string	Error code.
`errors[].field`	string	The field that caused the error.
`errors[].description`	string	Description of the error.
`errors[].severity`	enum	`INFO`, `WARN`, `ERROR`.
`errors[].category`	enum	`APPLICATION`, `SYSTEM`, `REQUEST`, `DATA`.
`errors[].errorIdentifiers.gatewayErrorCategory`	enum	`INTERNAL_DATA_ERROR`, `EXTERNAL_DATA_ERROR`, `SYSTEM_ERROR`.

Result

A zipped CSV file with line‑item error details when ingestion errors exist.
204 No Content when there are no ingestion errors.

Next steps

Use the Feed item status API to identify failed items and correlate with the error CSV.
Fix the affected items and resubmit a new feed.
Store the file with the correlation ID for audit and support.

Updated 1 day ago