Walmart reference
Walmart API guide
Search retail products, resolve a selected item and inspect available customer reviews. Treat product identity, seller identity, price and availability as separate data points.
Quickstart
Start with Walmart
Search retail products, resolve a selected item and inspect available customer reviews. Treat product identity, seller identity, price and availability as separate data points.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Find a product
Preserve the query and supported sort when requesting another page. Similar titles can be different products or variants. Parameters and current cost →
curl "https://www.monocrawl.com/v1/walmart/search?query=coffee%20grinder&page=1" \ -H "x-api-key: mn_your_key_here"
2. Inspect an item
Replace the example id with the selected Walmart item ID. Read current price and availability together; neither reserves inventory. Parameters and current cost →
curl "https://www.monocrawl.com/v1/walmart/product?id=6138924168" \ -H "x-api-key: mn_your_key_here"
3. Read product reviews
Use the same item id. These are product reviews, not seller reviews; a page is a sample of available discussion. Parameters and current cost →
curl "https://www.monocrawl.com/v1/walmart/reviews?id=265952442&page=1" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| Paging and sorting | Use the documented page and sort controls. Do not send filters merely because another retail endpoint accepts them. Endpoint reference → |
| Review identity | Product and seller reviews use different IDs and operations. Do not combine their rating populations. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| Compare seller offers | offers | Use the product_id accepted by this operation. Compare seller, currency and available fulfillment information. |
| Inspect a seller | seller | Use a seller identifier, not the product item ID. |
| Seller feedback | seller-reviews | Keep seller reputation separate from the product’s rating. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Reviews and offers
Other operations
Search and discovery
Operations
Walmart
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Walmart
8 operationsElsewhere
The same registry, other shapes
- Walmart overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=walmart— the same rows to your code at runtime, for 0 credits.