ECOMMERCECOMPANYAI API MCP READY

Walmart API

Four modes over one of the largest US retail catalogues. Search returns products with price, was-price, rating and both ids you need downstream; product adds UPC, manufacturer number and the full rating breakdown; reviews returns the customer review text; sellers lists every marketplace offer on a listing with price, availability, delivery date and return policy. The sellers mode is the reliability wedge, since competing tools fail on it most.

RECORDS3
MEDIAN LAGon demand
PARAMETERS5
TOTAL USERS1
MONTHLY ACTIVE1
TOTAL RUNS22
SUCCESS (30D)100.0%
RATINGno ratings yet
LAST MODIFIED2026-08-08
PUBLISHED2026-08

Input parameters

PARAMETERTYPEREQDEFAULTDESCRIPTION
search_mode enum yes search search finds products and returns both ids; product returns full detail; reviews returns customer reviews; sellers lists every offer on a listing.
query string no — Required in search mode. A keyword such as 'laptop' or 'coffee maker'.
item_id string no — Required for product, reviews and sellers. The modes need different ids and every search row gives you both: product and sellers take the alphanumeric productId, reviews takes the all-digits usItemId.
store_id string no — Sellers mode only. Pricing and availability are store specific; copy the storeId from a search row to scope the offers.
max_results integer no 100 Rows to return before stopping. Search returns up to 50 products per upstream call, reviews 20, and paging is automatic. — drives your bill

Worked examples

Keyword search — cheap first run
{
  "search_mode": "search",
  "query": "coffee maker",
  "max_results": 20
}
Every seller on a listing — the buy-box view, needs the productId
{
  "search_mode": "sellers",
  "item_id": "34X621REEQZQ",
  "store_id": "1932"
}
Full product record — adds UPC, category path and variants
{
  "search_mode": "product",
  "item_id": "34X621REEQZQ"
}
Customer reviews — reviews take the all-digits usItemId
{
  "search_mode": "reviews",
  "item_id": "414173778",
  "max_results": 100
}
POWER-USER TIP
Two ids, and they are not interchangeable — Reviews mode needs the all-digits usItemId; product and sellers need the alphanumeric productId. Handing over the wrong one does not error upstream, it silently reports no results and burns a paid call, so the Actor rejects the mismatch before making the request. Every search row returns both ids.
POWER-USER TIP
Store id changes the price — Walmart prices and availability are store specific. Sellers mode without a store_id uses the default store, which may not match what a shopper in your target market sees. Copy the storeId from a search row to pin the comparison.

Coverage

4
modes — search · product · reviews · sellers
21
fields per product — price was-price rating seller stock shipping ids +
17
seller fields — price availability delivery date return policy +

Tasks

Saved runs with the inputs already filled in — each one a standalone page and a working configuration example.

Request a task →

Code

curl

curl -X POST "https://api.apify.com/v2/acts/johnvc~walmart-api/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"search_mode":"search","query":"coffee maker","max_results":20}'

Python

from apify_client import ApifyClient

client = ApifyClient("APIFY_TOKEN")
run = client.actor("johnvc/walmart-api").call(
    run_input={"search_mode": "search", "query": "coffee maker", "max_results": 20}
)
for product in client.dataset(run.default_dataset_id).iterate_items():
    print(product.get("title"), product.get("price"), product.get("sellerName"), product.get("productId"))

What people use it for

Alternatives

Google Shopping API — cross-retailer price comparison rather than one catalogueours Google Immersive Product API — product detail from the Google shopping surfaceours Google Shopping Lite API — a cheaper cross-retailer price feedours