Walmart API

Get Walmart product and review data with one API

Name: Walmart Data API
Brand: SocialCrawl
Availability: InStock

Fetch Walmart search, product detail, reviews, categories, and seller offers as structured JSON with one SocialCrawl API key. Shared commerce schema. Reads are priced in credits.

Read the docs How it works Try live

/v1/walmart

5 active endpoints. Advanced tier on all.

GET /v1/walmart/product
GET /v1/walmart/reviews
GET /v1/walmart/search
GET /v1/walmart/category
GET /v1/walmart/offers

What Walmart endpoints does SocialCrawl ship?

Five live read endpoints for Walmart. Product by id, reviews, keyword search, category browse, and multi-seller offers. Data API only.

Product by id

5 credits

/v1/walmart/product

Full Walmart product for a product_id. Title, price, rating, images. Advanced tier (5 credits).

product_id, country

Product reviews

5 credits

/v1/walmart/reviews

Reviews for a Walmart product_id. Rating, text, author, sort and page controls. Advanced tier (5 credits).

product_id, page, limit, sort

Product search

5 credits

/v1/walmart/search

Keyword search across Walmart. Product list with ids for detail and reviews. Advanced tier (5 credits).

query

Category browse

5 credits

/v1/walmart/category

Products in a Walmart category_id. Optional limit. Advanced tier (5 credits).

category_id, limit

Seller offers

5 credits

/v1/walmart/offers

Every seller offering a Walmart product_id. Offer matrix for price and fulfillment. Advanced tier (5 credits).

product_id, country

Walmart API5 endpoints supported

View docs

Products

Reviews

Returns one Walmart product by id: title, brand, price and list price, rating with its star breakdown, images, specifications, availability, and seller.

Use it when you have a Walmart item id and need full product detail. For written reviews use reviews, and for other sellers use offers.

GET/v1/walmart/product?product_id=17835006350&country=US

product_id

product_id · Walmart product id. Either the numeric item id from the product URL (walmart.com/ip/<name>/17835006350) or the alphanumeric catalog id (34J2GQ9D9TFM). Both resolve to the same product.

$ curl https://www.socialcrawl.dev/v1/walmart/product?product_id=17835006350&country=US \
    -H "x-api-key: sc_YOUR_API_KEY"

— · idle

// Running this live needs your own API key — hit "Try it" to see an example response

How the Walmart API works

Walmart is a normal SocialCrawl data surface. You call GET /v1/walmart/… with an API key, spend credits on live misses, and get a single JSON envelope back.

Authenticate every call

Send your key in the x-api-key header. No Walmart OAuth app for public reads. The same key works across SocialCrawl platforms.

GET with query params

All Walmart routes are GET. Pass product_id, query, category_id, country, page, limit, sort as query strings. We validate formats before charging.

Pay in credits, not seats

All five Walmart routes are advanced tier: 5 credits on live miss. Cache hits cost 0. Empty or hard failures refund.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.

The usual integration chain

Most products discover entities first, then deepen detail and reviews only when needed.

01Search

GET /v1/walmart/search?query=…

ProductList with product_id values

Resolve ids before detail spend.

02Product

GET /v1/walmart/product?product_id=…

Full Product for the id

Search rows are not a full PDP.

03Reviews

GET /v1/walmart/reviews?product_id=…

ReviewList with sort and page

Customer language for VoC pipelines.

04Offers

GET /v1/walmart/offers?product_id=…

SellerList of offers

Multi-seller price checks.

request

GET /v1/walmart/search?query=airpods+pro
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

GET /v1/walmart/product?product_id=17835006350&country=US
GET /v1/walmart/reviews?product_id=17835006350&limit=50&sort=recent

response envelope

{
  "success": true,
  "data": {
    "product": {
      "id": "17835006350",
      "title": "Example product",
      "price": { "current": 24.99, "currency": "USD" },
      "rating": 4.3
    }
  },
  "credits_used": 5,
  "credits_remaining": 9995,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.

Productproduct

id, title, price, rating, images, url

ProductListsearch, category

items[] with product_id, title, price, rating

ReviewListreviews

items[] with rating, text, author, published_at

SellerListoffers

seller offer rows for product_id

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint. Walmart is not a sidecar.

Edge receives the call

Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).

Validate, then debit

Registry lookup finds walmart/search (or product, reviews, offers). Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before upstream work.

Cache or fetch

A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: Walmart commerce upstream paths run. Retries on 5xx/network with a circuit breaker if the source is unhealthy.

Normalize and return

Upstream JSON is mapped to commerce archetypes (Product, ProductList, ReviewList, SellerList, App, PlaceList as applicable), validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.

Billing rules that matter in production

All routes live miss: 5 credits
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
product_id is the deepen key from search
category_id browses taxonomy leaves
offers is multi-seller, not product body
No cart or checkout routes

How we get the data

Walmart is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.

What Walmart is for this API

Public product catalog, reviews, category leaves, and seller offers. Read-only.

How SocialCrawl reaches it

Walmart commerce upstream paths behind the unified /v1 envelope.

What leaves our edge

Product, ProductList, ReviewList, SellerList on the shared commerce schema.

What we do not ship live

No cart, inventory, or store-associate tools.

field map sketch

product_id row→ product.*title, price, rating, images

review pages→ ReviewListsort, page, limit controls

offer matrix→ SellerListall sellers on product_id

What this API is used for

The jobs this API is most often used for.

5active Walmart endpoints in the registry

5 creditsadvanced tier on product, reviews, search, category, offers

Retail assortment and review monitoring

Callers concentrate on search or taxonomy, then deepen detail and reviews for shortlisted entities. Flat 5-credit advanced reads across product, reviews, search, category, and offers under one key.

Live misses are typically a few seconds. Some DFS-backed routes can take longer on cold cache.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Retail analysts

Python, BI

search and category for assortment, product for PDP facts.

VoC teams

Node, warehouses

reviews by product_id for brand and competitor language.

Pricing ops

Go, workers

offers plus product for multi-seller price checks.

Call it in two lines

Every Walmart live call is 5 credits. Cache hits are free.

curl "https://www.socialcrawl.dev/v1/walmart/search?query=airpods+pro" \
  -H "x-api-key: sc_your_api_key_here"

curl "https://www.socialcrawl.dev/v1/walmart/product?product_id=17835006350&country=US" \
  -H "x-api-key: sc_your_api_key_here"

Walmart on SocialCrawl

Same key as the rest of the catalog

Platform docs Get an API key

Endpoints

What data does the Walmart API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

ProductGet a Walmart product by id ReviewsGet Walmart product reviews SearchSearch Walmart products by keyword CategoryBrowse Walmart products in a category OffersGet every seller offering a Walmart product

Comparison

How does SocialCrawl compare to Walmart affiliate / partner feeds for Walmart data?

Same Walmart data, two very different paths. Auth, rate limits, schema, and cost — side by side.

Feature	SocialCrawl	Walmart affiliate / partner feeds
Access	API key, working in a minute	Partner application and approval
Customer reviews	Up to 50 per call with full text and photos	Not exposed
Marketplace seller offers	Every seller, price, and condition per item	Not exposed
Store-level pricing	ZIP, state, or store id	National catalogue only
Response shape	Same canonical product and review objects as Amazon and Google Shopping	Walmart-specific feed format

Access

SocialCrawl

API key, working in a minute