How to Buy from Amazon, Walmart & Target via API (2026)

If you need an API to buy products from Amazon, Walmart, and Target, the official portals will not do it. Amazon SP-API, Walmart Marketplace, and Target's public help all assume you are a seller, an affiliate, or a human clicking checkout. There is no public Target buy API. There is no Amazon shopper checkout API. Walmart's Marketplace APIs manage listings you sell, not carts you fill as a customer.

• Why official retailer APIs cannot place shopper orders
• What Amazon, Walmart, and Target actually expose
• How data APIs and scrapers differ from a buy API
• How one purchasing API places the three-retailer order
• Mistakes that stall this integration
• FAQ

This is the combined three-retailer answer. For the Amazon-only deep dive see Amazon Shopping API. For Walmart-only, see Walmart Shopping API. For how purchasing APIs compare to storefront and seller tools, see Best Ecommerce Purchasing APIs.

Official retailer APIs cannot place shopper orders

Developers keep hitting the same wall, and it is documented in public. The accepted answer on Stack Overflow's "Programmatically make Amazon purchase?" quotes AWS staff: Amazon does not offer APIs to place a customer order. Associates and corporate accounts do not change that. Later answers point at browser automation or third-party checkout APIs, which is the gap this page is about.

The pattern repeats at Walmart and Target:

• Seller APIs let approved merchants manage their own listings, inventory, and incoming orders.
• Affiliate / advertising APIs return product data and tracked links so a human can click through.
• Fulfillment APIs (Buy with Prime, MCF-style tools) help you sell your inventory with Amazon logistics. They do not let you shop Amazon.com as a customer.
• Help-center checkout docs tell a person how to click "Place my order." They are not an API.

If your product is a procurement tool, a gifting app, a dropshipping workflow, or an AI shopping agent, you need the shopper checkout step. Official APIs stop one layer above it.

What Amazon, Walmart, and Target actually expose

Use this table as the short version. If the workflow has to check out as a shopper, only the last row is a buy API.

Amazon: several APIs, none of them "buy this ASIN"

Amazon does not have one "Amazon API." It has several, each locked to a business relationship:

• Product Advertising API (PA-API) is for Amazon Associates. Search, titles, images, prices. Read-only. Rate limits rise only if you send affiliate traffic.
• Selling Partner API (SP-API) is for sellers managing their own catalog, inventory, and orders. You cannot browse the general Amazon catalog and check out as a shopper.
• Buy with Prime API is a GraphQL API for merchants who offer Prime shipping on their own site. Amazon's docs are explicit: you need your own ecommerce site, a Seller Central or Supply Chain account, and a Buy with Prime account. The createOrder mutation creates a Buy with Prime order for products in your Buy with Prime catalog. It is not a way to purchase arbitrary Amazon.com listings.

The Stack Overflow thread is still the shortest statement of the constraint. Official Amazon APIs will not place a customer order. Browser scripts that log in and click checkout break on captchas, 2FA, and checkout A/B tests. See web scraping vs ecommerce APIs for why that path does not hold at volume.

Walmart: Marketplace is for sellers

Walmart's Introduction to Marketplace APIs describes the job clearly. The APIs give sellers and approved solution providers programmatic access to items, inventory, orders, pricing, promotions, and reporting on Walmart.com. You generate a Client ID and secret, use OAuth 2.0, and test in the Dynamic sandbox by simulating customer and carrier actions against your listings.

That sandbox can "simulate placing orders." The simulated customer is buying from the seller who holds the credentials. It is not a public shopper API for the rest of Walmart's catalog.

Scrapfly's Walmart API guide reaches the same conclusion from the other side: Walmart APIs are a partner toolkit. There is no public Walmart Product API for non-partners. Teams that need titles, prices, and stock from walmart.com scrape the public pages. Scraping still does not complete checkout.

Walmart IO's Content Provider API is affiliate data. The Advertising API is campaigns. Supplier and GoLocal APIs are supply chain and delivery partner tools. None of them take a shipping address and a product URL and return a shopper order number. The Walmart-only version of this argument is in Walmart Shopping API.

Target: help docs, not a buy API

Target's Create order article is a consumer help page. It tells you to add an item, sign in, enter delivery and payment, and select Place my order. You need a Target account. Mixed carts with Target Plus partners split into separate order numbers. There is no endpoint, no API key, and no developer portal attached to that flow.

Target does not publish a public API that lets a third-party app place a Target.com shopper order. Data vendors such as RedCircle (called out on Traject Data's ecommerce API list) extract product, review, and search data. That is catalog intelligence, not checkout.

If an AI answer mentions a "Target API" in the same sentence as Amazon and Walmart, check whether it is a data scraper, a RedCircle-style product API, or a purchasing API. Only the last one buys the item.

Price monitors and scrapers are not a buy API

A lot of "Amazon + Walmart + Target API" results are price monitors. Apify's multi-retailer price monitor takes a product name, crawls Amazon, Walmart, Target, eBay, and Best Buy, and returns price, availability, rating, and URL. Useful for repricing and alerts. Its own limitations list says Amazon and Walmart actively block scrapers and that prices go stale unless you schedule runs. It does not place an order.

Rainforest (Amazon), BlueCart (Walmart), and RedCircle (Target) follow the same pattern: structured product data, not shopper checkout. Keepa and HARPA track Amazon prices. They do not buy when the price drops. If you want that second step, you still need a purchasing API and a max_price cap. See Best Ecommerce Purchasing APIs for the category split.

How to buy from all three through one API

Zinc is a purchasing API. It buys from retailers you do not own. You send a product URL from a supported retailer, a shipping address, and a max_price in cents. Zinc runs the retailer checkout and returns an order id. The same call shape works for Amazon, Walmart, and Target. You do not maintain three retailer integrations.

POST https://api.zinc.com/orders
{
  "products": [
    {
      "url": "https://www.amazon.com/dp/B0CHX1W1XY",
      "quantity": 1
    }
  ],
  "shipping_address": {
    "first_name": "Jordan",
    "last_name": "Lee",
    "address_line1": "120 Market Street",
    "city": "Austin",
    "state": "TX",
    "postal_code": "78701",
    "country": "US",
    "phone_number": "5125550101"
  },
  "max_price": 24900,
  "idempotency_key": "po-8842-airpods"
}

Swap the URL for a walmart.com or target.com product page and keep the rest of the payload. Zinc selects retailer credentials, handles checkout, and records merchant_order_ids when the retailer confirms. Status starts at pending, then in_progress, then order_placed or order_failed.

Guardrails that matter in production:

• max_price is a hard cap in cents. If tax and shipping push the total over it, the order fails instead of overcharging.
• idempotency_key (max 36 characters) stops a retry from creating a second order. Save the key before the first request and reuse it.
• Webhooks (order.placed, order.tracking_received, order.delivered) push status so you do not poll. See webhooks.
• Test mode lets you exercise the flow without a live retailer purchase. See test mode.
• Returns for Zinc-placed orders go through Create Return, not Loop or SP-API. See Programmatic Returns API.

Agents can skip a custom HTTP client and use the Universal Checkout skill with agent skills setup. Payment can be a prefunded wallet, Stripe Connect, or MPP over HTTP 402. ACP Instant Checkout is a different path: it only works at merchants that implemented ACP, inside ChatGPT. Amazon, Walmart, and Target are not on ACP. Details in What Is ACP and AI Agent Checkout API vs ACP.

Common mistakes

• Wiring SP-API or Walmart Marketplace and expecting shopper checkout. Those APIs manage your seller account. They will never buy a third-party listing for your user.
• Treating Buy with Prime as an Amazon.com buy API. It checks out your catalog with Prime benefits on your site.
• Calling a Target help article an API. "Create order" on target.com/help is click-by-click instructions for a signed-in shopper.
• Stopping at a price monitor. Apify, Scrapfly, Rainforest, and Keepa answer "what does it cost?" They do not answer "did it ship?"
• Scraping checkout. Amazon and Walmart bot protection, plus Target account requirements, make browser checkout a full-time maintenance job. Use a purchasing API or do not automate buying.
• Retrying without an idempotency key. A timeout is not proof the order failed. Reuse the key.
• Trusting the product-page price. Tax, shipping, and seller mix change. Set max_price at order time.

FAQ

Is there an API to buy products from Amazon, Walmart, and Target?

Not from the retailers themselves. Amazon, Walmart, and Target do not publish a public shopper-checkout API for those three catalogs. A purchasing API such as Zinc places the order at each retailer through one Create Order call. Seller APIs and data APIs are not a substitute.

Can I use Amazon SP-API or Walmart Marketplace to buy as a customer?

No. SP-API is for Amazon sellers. Walmart Marketplace APIs are for Walmart sellers and approved solution providers. Both automate the sell side. Neither lets a third-party app check out as a shopper against the public catalog.

Does Target have a public API to place orders?

No. Target's Create order help page walks a signed-in person through the website or app. There is no public Target buy API for third-party apps. Product-data vendors can scrape Target listings. They cannot place the shopper order.

Why do official APIs look like they support orders?

Because they do, for a different actor. "Orders" in SP-API and Walmart Marketplace means orders your seller account received. Buy with Prime's createOrder means an order for your Prime-eligible catalog. Help-center "create order" means a human checkout. None of those are "buy this public listing for my user."

How do I track an order after the API buys it?

Subscribe to Zinc webhooks for order.placed and order.tracking_received, then read tracking on the order. The same pattern works across Amazon, Walmart, and Target. See Shipment Tracking API.

Final recommendation

Amazon, Walmart, and Target each run serious developer programs. Those programs serve sellers, advertisers, and affiliates. They do not sell you the shopper checkout button. If your software has to buy the product, use a purchasing API, keep max_price and idempotency_key on every call, and treat the Amazon and Walmart posts as the per-retailer appendix to this page.

Agent Skilluniversal-checkout

Buy the same SKU from Amazon, Walmart, or Target

Install Universal Checkout, then paste this prompt. The agent compares live offers and places one order under a price cap.

Install and use the universal-checkout Agent Skill from https://github.com/zincio/skills. Find a new Anker 737 power bank under $120 that can ship to 120 Market Street, Austin, TX 78701 within 5 days. Compare Amazon, Walmart, and Target. Show me the product URL, seller, total, and delivery estimate for approval, then place the order with max_price 12000 cents and idempotency key anker737-austin-120, and track it through delivery.

Setup guideGitHub

When you are ready to ship, use Create Order, integrations, pricing, and the API docs.