Bulk item maintenance

Use the Bulk item setup API for bulk item maintenance. Submit an item maintenance feed using feedType=MP_MAINTENANCE to perform partial updates to existing items.

The maintenance feed type uses the same layout as the item setup specification, and entries are submitted based on product type. However, unlike full item setup, you do not need to submit a complete item setup payload. The maintenance feed type typically requires only a small set of required attributes to submit updates for an existing item.


Use cases

  • Apply partial updates to existing items without resubmitting a full setup payload.
  • Update item data in bulk by product type using the same overall structure as item setup feeds.
  • Maintain listings over time (for example, correcting or refreshing item details using the maintenance schema).

Reference guide

This guide explains how to submit an MP_MAINTENANCE feed using the Bulk item setup API for partial updates to existing items.

High-level workflow

  1. Build a maintenance feed file using the MP_MAINTENANCE specification (same general layout as item setup).
  2. Include only the fields required to perform the partial update for each item (you do not need the full setup payload).
  3. Submit the file using POST /v3/feeds?feedType=MP_MAINTENANCE.
  4. Use the returned feedId to monitor processing using your feed status / feed item status workflow and resolve item-level errors.

Endpoint

POST https://marketplace.walmartapis.com/v3/feeds?feedType=MP_MAINTENANCE

Query parameter

  • feedType (string): Use MP_MAINTENANCE for bulk item maintenance (partial updates).

Request body

  • multipart/form-data with required file field (binary) containing the MP_MAINTENANCE feed payload.

Request sample

curl --request POST \ --url 'https://marketplace.walmartapis.com/v3/feeds?feedType=MP_MAINTENANCE' \ --header 'WM_CONSUMER.CHANNEL.TYPE: <consumer-channel-type>' \ --header 'WM_GLOBAL_VERSION: 3.1' \ --header 'WM_MARKET: us' \ --header 'WM_QOS.CORRELATION_ID: b3261d2d-028a-4ef7-8602-633c23200af6' \ --header 'WM_SEC.ACCESS_TOKEN: eyJraWQiOiIzZjVhYTFmNS1hYWE5LTQzM.....' \ --header 'WM_SVC.NAME: Walmart Service Name' \ --header 'accept: application/json' \ --form 'file=@mp_maintenance.json'
import requests url = "https://marketplace.walmartapis.com/v3/feeds"
params = {"feedType": "MP_MAINTENANCE"} headers = { "WM_CONSUMER.CHANNEL.TYPE": "<consumer-channel-type>", # optional "WM_GLOBAL_VERSION": "3.1", "WM_MARKET": "us", "WM_QOS.CORRELATION_ID": "b3261d2d-028a-4ef7-8602-633c23200af6", "WM_SEC.ACCESS_TOKEN": "eyJraWQiOiIzZjVhYTFmNS1hYWE5LTQzM.....", "WM_SVC.NAME": "Walmart Service Name", "accept": "application/json",
} with open("mp_maintenance.json", "rb") as f: files = {"file": ("mp_maintenance.json", f)} resp = requests.post(url, headers=headers, params=params, files=files, timeout=60) print(resp.status_code)
print(resp.text)

Modify your code

  1. Choose what to update

    • Identify the existing SKUs and fields that need partial updates.
  2. Build the MP_MAINTENANCE feed file

    • Use the maintenance spec/version required for your integration.
    • Follow the same general layout as item setup, but include only the subset of fields required for the update.
  3. Submit the feed

    • Upload the file using POST /v3/feeds?feedType=MP_MAINTENANCE.
  4. Track processing

    • Use the returned feedId to monitor feed and item-level outcomes.
    • Fix item-level errors, validate against the schema definition, and resubmit if needed.

Results

After a successful call (200):

  • You receive a feedId to track processing and item-level maintenance outcomes.
  • Items are processed as partial updates; you don’t need to submit a full item setup payload for each item.

Next steps

  • Validate the maintenance feed file against the maintenance schema/version before submission.
  • Log WM_QOS.CORRELATION_ID per request for traceability and support.
  • Refer to the API reference documentation to confirm required headers, supported feedType values (use MP_MAINTENANCE here), request format (multipart file upload), and status/error behavior before promoting changes to production.

Did this page help you?