A WireMock simulation of Walmart's REST API — covering item feeds, cursor-paged listings, retirement acknowledgements, taxonomy, and search.
A shared instance of this template runs on a public endpoint — call it right now from curl, an SDK, or an AI agent. Responses are fixed examples and behavior can't be changed; rate limits apply.
Jump to the endpoints ↓Run this template as a mock API in WireMock Cloud for a private instance you control — edit stubs, add stateful scenarios, use dynamic response templating, and inspect requests in the log.
Open in WireMock Cloud (free) →Live sandbox · no signup, no API key
A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.
Endpoints
POST Get item spec for product types
curl -s -X POST 'https://407om.wiremockapi.cloud/v3/items/spec' \
-H 'Content-Type: application/json' \
-d '{}'GET List items with pagination (data-driven)
curl -s -X GET 'https://407om.wiremockapi.cloud/v3/items'DELETE Retire item by SKU
curl -s -X DELETE 'https://407om.wiremockapi.cloud/v3/items/your-SKU'Spec catalog — Item Management (3.0) · 11 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /v3/feeds | Bulk Item Setup (Multiple) |
| GET | /v3/items | All items |
| GET | /v3/items/{id} | An item |
| DELETE | /v3/items/{SKU} | Retire an item |
| POST | /v3/items/associations | Get Item Associations |
| POST | /v3/items/catalog/search | Catalog Search |
| GET | /v3/items/count | Get items count by status |
| GET | /v3/items/groups/count | Get item count by groups |
| POST | /v3/items/spec | Get Spec |
| GET | /v3/items/taxonomy | Taxonomy |
| GET | /v3/items/walmart/search | Item Search |
Unauthenticated WireMock Cloud demo sandbox for Walmart — not an official Walmart sandbox, and it returns simulated example data only.
Data-driven here means the responses are computed from your request rather than replayed verbatim. Page through /v3/items and the nextCursor is derived from the limit you passed — send limit=5 and the cursor encodes 5. Look up a SKU and Walmart's ITEM_NOT_FOUND envelope arrives with your identifier embedded in its info field; retire one and the acknowledgement repeats your SKU inside Walmart's telltale 48-hours-to-leave-the-catalog wording. Even feed submissions mint ids in the marketplace's hex@-suffix format.
The backing store on the public instance holds no records, while totalItems is a fixed figure — so pages arrive empty even as the cursor advances correctly. Exercise the pagination mechanics here; when a test needs items to actually come back, use the seedable sibling template, or copy this one into WireMock Cloud, where stateful scenarios let the store accumulate whatever inventory your requests write into it.
Walmart's real structure: an errors array whose entry carries code ITEM_NOT_FOUND, a human-readable description, severity ERROR, category DATA — and the SKU you asked about, threaded into the info field. That echo makes it easy to assert your code surfaces the right identifier in logs and messages.
A feed POST earns a plausibly formatted feedId and nothing more — the item store stays as it was. That's sufficient for the submission side of an integration: your code sends the payload, captures the id, and records it for the status polling it would do against the real marketplace.
Two things: that listed items exist (they don't, here), and that totalItems matches what a walk of the pages would count. Anchor tests to the response contracts instead: cursor format, envelope fields, and the SKU echoes described above.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.