A WireMock simulation of Walmart's REST API — covering a seedable item store with lookup, search, retirement, and spec endpoints.
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://1k743.wiremockapi.cloud/v3/items/spec' \
-H 'Content-Type: application/json' \
-d '{}'GET Get taxonomy
curl -s -X GET 'https://1k743.wiremockapi.cloud/v3/items/taxonomy'POST Catalog search
curl -s -X POST 'https://1k743.wiremockapi.cloud/v3/items/catalog/search' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Item Management (3.0) · 12 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /v3/__seed/items | Seed items into state |
| 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.
One route sets this template apart: POST /v3/__seed/items, a mock-only control that loads the store with a fixture catalog of three products — electronics, apparel, home. From then on the API behaves like a system of record. Listings return complete Walmart item objects (wpid, upc, gtin, shelf placement, price, lifecycleStatus), a seeded SKU resolves through the lookup route, catalog search finds it, and retiring it genuinely shrinks the next listing until a fresh seed restores the full set.
No — whatever body you send, the store reloads the same three fixtures. That rigidity is deliberate: every test run starts from an identical, known dataset, so a colleague running your suite tomorrow sees the catalog you saw today. Custom inventory means editing the stubs in a private copy.
Seed, then list and observe three items; retire SKU-ELECTRONICS-001 and the next listing holds two; seed again and it's back to three. That sequence — mutation observable through a different endpoint — is what distinguishes this template from response-replay mocks, and it runs in a few seconds of curl.
Begin by seeding rather than trusting what's there: another visitor may have retired half the catalog moments before. Sequences that depend on exclusive access — say, asserting an exact count after a retirement — are safer against your own WireMock Cloud copy, where nobody else holds a write path.
No — /v3/items/count reports a fixed catalog-scale figure in the hundreds regardless of what seeding and retirement have done, mimicking a seller with a large established catalog. Use listings to measure actual store contents, and treat the count route as a stable payload for parser tests.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.