Use this operation to list recent feed submissions and their processing status across your account. Results include the feed type, counts for received/succeeded/failed items, status, and timestamps.

Scope: Marketplace partner feeds (items, inventory, pricing, lag time, and more).

Endpoint

GET https://marketplace.walmartapis.com/v3/feeds

Query parameters

• feedId string, repeatable. One or more feed IDs to filter the results. If the ID contains @, percent‑encode it as %40.
• includeDetails boolean. When true, returns detailed item results and enables paging controls.
• offset integer. Start index. Default 0. Use only when includeDetails=true.
• limit integer. Page size. Default 50. Max 50. Use only when includeDetails=true.

Request sample

curl --request GET --url "<https://marketplace.walmartapis.com/v3/feeds?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. Page through results when details are included. If includeDetails=true and totalResults exceeds your current page, increase offset by limit and repeat until you cover all results.
2. Filter early. Pass feedId for specific feeds or filter by feedType/feedStatus in code.
3. Handle timestamps. feedDate and modifiedDtm are provided as 64‑bit integers in epoch milliseconds; convert to ISO 8601 for logs and dashboards.
4. Alert on failures. If any error counters are greater than zero, or feedStatus is ERROR, fetch the detailed feed status for that feedId.
5. Be resilient. Use retry with backoff for 429 and 5xx responses. Keep your WM_QOS.CORRELATION_ID constant across retries of the same call.

Response sample

{
"totalResults": 115,
"offset": 0,
"limit": 50,
"results": {
"feed": [
{
"feedId": "882DAFBDCAA0480786D1E0435FBC86D7@AU8BAgA",
"feedSource": "MARKETPLACE_PARTNER",
"feedType": "item",
"partnerId": "100009",
"itemsReceived": 1,
"itemsSucceeded": 1,
"itemsFailed": 0,
"itemsProcessing": 0,
"feedStatus": "PROCESSED",
"feedDate": 1568148230011,
"modifiedDtm": 1568148252067,
"fileName": "item.json",
"itemDataErrorCount": 0,
"itemSystemErrorCount": 0,
"itemTimeoutErrorCount": 0,
"channelType": "0f3e4dd4-0514-4346-b39d-af0e00ea066d",
"orgId": "f5e3d40a-1267-46b9-a2f3-7811e4c0b2de"
},
{
"feedId": "9398AC344EC44070A5B336D1E6D4EF27@AQYBAgA",
"feedType": "MP_ITEM_PRICE_UPDATE",
"partnerId": "100009",
"itemsReceived": 0,
"itemsSucceeded": 0,
"itemsFailed": 0,
"itemsProcessing": 0,
"feedStatus": "ERROR",
"feedDate": 1568138099492,
"modifiedDtm": 1568138099615,
"fileName": "Affiliate Template v2.xlsx",
"itemDataErrorCount": 0,
"itemSystemErrorCount": 0,
"itemTimeoutErrorCount": 0,
"channelType": "57c99571-b460-43e2-bcd6-7d12f3ddd5a9",
"orgId": "f5e3d40a-1267-46b9-a2f3-7811e4c0b2de"
}
]
}
}

Expanded example with ISO timestamps

The same entry with timestamps converted.

{
"feedId": "882DAFBDCAA0480786D1E0435FBC86D7@AU8BAgA",
"feedDate": "2019-09-10T20:23:50.011Z",
"modifiedDtm": "2019-09-10T20:24:12.067Z"
}

Result

You receive a paged list of feeds and their processing status.

Status values

• RECEIVED: The feed was accepted and is queued.
• INPROGRESS: The feed is being processed.
• PROCESSED: The feed finished processing. Check the item counts and error counters.
• ERROR: The feed request failed.

Common feed types Is this accurate?

• item
• inventory
• LAGTIME
• PROMO_PRICE
• MP_ITEM_PRICE_UPDATE
• CPT_SELLER_ELIGIBILITY

Next steps

• Get detailed results for a specific feed using its feedId. The Feed item status API returns item-level statuses and error details.
• Use the detailed results to repair item data and resubmit failed items.
• Add monitoring that tracks failure rates by feedType and triggers alerts.