canonical: https://jentic.com/apis/walmart.com

# Walmart APIs

Walmart Marketplace seller APIs for AI agents. Across five APIs, an agent can list and manage catalog items, submit item feeds, update inventory across ship nodes and WFS, set and bulk-update prices, and retrieve, acknowledge, cancel, refund, and ship orders on Walmart.com. Every operation is available through the Jentic API Directory so an agent can search by intent and execute without reading Walmart's reference docs.

## For AI agents

An agent can run a full Walmart Marketplace seller workflow: upload item feeds and manage listings, keep inventory in sync across ship nodes and Walmart Fulfillment Services, set and bulk-update prices, and read, acknowledge, cancel, refund, and ship orders. It calls each operation by intent through Jentic instead of hand-wiring the Walmart marketplace and developer proxy hosts.

## Scope

Use for: Managing a Walmart Marketplace seller account: items, item feeds, inventory across ship nodes and WFS, prices, and the order lifecycle from acknowledgement through ship, cancel, and refund.

Not supported:
- shopper checkout
- payment processing
- customer messaging
- advertising campaigns
- store maps

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Orders API | e-commerce | 9 | Programmatically get all orders, get all released orders. |
| Walmart Marketplace | e-commerce | 9 | Programmatically all items, an item. |
| Inventory Management | e-commerce | 7 | Programmatically bulk item inventory update, wfs inventory. |
| Item API | developer-tools | 6 | Programmatically upload an item feed, get status of an item feed. |
| Price Management | developer-tools | 3 | Programmatically set up cap sku all, update bulk prices (multiple). |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Read, acknowledge, cancel, refund, or ship orders | order | The Orders API covers the full order lifecycle, while the Marketplace API only exposes get-all-orders, get-an-order, and ship. |
| One broad API spanning items, orders, inventory, and price | main | The Marketplace API bundles core read and write operations across all four seller areas into one surface. |
| Update stock across ship nodes or WFS | inventory-management | Inventory Management adds per-ship-node, bulk, and Walmart Fulfillment Services inventory operations the Marketplace API does not. |
| Set or bulk-update item prices | price-management | Price Management is the dedicated surface for single-price updates, CAP SKU setup, and bulk price feeds. |
| Submit item listing feeds | item-api | The Item API handles v2 and v3 item feed uploads and feed-status checks, which the Marketplace API does not expose. |

## Cross-API use cases

### List a new item and price it

Upload an item feed, confirm the feed status, then set the item price so the listing goes live ready to sell.

Example prompt: Call the Item API to upload a feed and poll its status, then call Price Management to set the SKU price.

### Fulfil an order and update stock

Read released orders, acknowledge them, ship the order lines, then adjust inventory for the affected SKUs across ship nodes.

Example prompt: Call the Orders API to get released orders, acknowledge and ship them, then call Inventory Management to update per-ship-node stock.

### Reprice the active catalog

Pull all items on the account, then push a bulk price update feed for the SKUs that need repricing.

Example prompt: Call the Marketplace API to list all items, then call Price Management to submit a bulk price feed for the selected SKUs.

### Sync inventory for listed items

List the account's items, then update inventory for each SKU across ship nodes and Walmart Fulfillment Services.

Example prompt: Call the Marketplace API to get all items, then call Inventory Management to set inventory per ship node and check WFS stock.

## Why Jentic

- **Setup:** Instead of wiring up the Walmart marketplace host and the developer proxy hosts and handling each API's auth separately, you install Jentic One once, add the Walmart APIs you need from the Jentic API Directory, and your agent calls any of them through one interface.
- **Permission scoping:** Your own rules decide which Walmart operations the agent may call. Because Orders, Inventory Management, and the Marketplace API put the order, SKU, or item id in the URL path, a rule can pin the agent to specific resources and allow reads while leaving writes such as cancel, refund, or retire an item out of the allowed set.
- **Credential handling:** Each Walmart credential, including the Marketplace Bearer token, is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** An agent searches the Jentic directory by intent, such as 'ship an order' or 'update inventory for a SKU', and Jentic returns the matching Walmart operation with its input schema, so the right endpoint is found across all five APIs without browsing the reference docs.

## Related vendors

- **Shopify** — Runs the same seller workflow of products, inventory, orders, and fulfillment on its own storefront platform.
- **eBay** — Another large marketplace where sellers manage listings, inventory, pricing, and orders through APIs.
- **Amazon** — Selling Partner APIs cover comparable marketplace listing, fulfillment, pricing, and order operations.
- **Stripe** — Complements marketplace order flows with the payment processing that Walmart's seller APIs do not handle.

## FAQ

### What can an agent do across Walmart's APIs?

It can run the Walmart Marketplace seller workflow end to end: upload item feeds and manage listings, keep inventory in sync across ship nodes and Walmart Fulfillment Services, set and bulk-update prices, and read, acknowledge, cancel, refund, and ship orders.

### Do the Walmart APIs share one login?

No. The Marketplace API expects a Bearer token in the Authorization header, while the Orders, Inventory Management, Item, and Price Management specs declare no authentication. Through Jentic each API's credential is stored once in your own Jentic One instance and injected at execution time.

### Which API should an agent use for orders?

Use the Orders API for the full order lifecycle, including acknowledge, cancel, refund, and ship. The broader Marketplace API only exposes listing orders, getting a single order, and shipping.

### How do items, inventory, and price fit together?

The Item API creates and updates listings through feeds, Price Management sets the price for a SKU, and Inventory Management keeps stock accurate across ship nodes and WFS. An agent typically lists an item, prices it, then syncs its inventory.

### Is there overlap between the Marketplace API and the focused APIs?

Yes. The Marketplace API bundles core item, order, inventory, and price operations into one surface, while the dedicated APIs add depth the bundle lacks, such as per-ship-node inventory, feed uploads, and bulk price updates.

### Are these APIs for shoppers or for sellers?

They are seller-side APIs for managing a Walmart Marketplace account. They do not cover shopper browsing, checkout, or payment; they cover the catalog, inventory, pricing, and order operations a seller runs.