urlstringrequired
Walmart product page URL.
https://api.sandbase.ai/v1/api/walmart/productFetch a Walmart product page by URL and get full product details (title, price, availability, ratings, images, and specs) in one normalized response.
Your output will appear here
Complete the inputs, then click Run.
Fetch a Walmart product page by URL and get full product details (title, price, availability, ratings, images, and specs) in one normalized response.
curl -X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "walmart/product", "url": "https://www.walmart.com/ip/Apple-AirPods-Pro-2/5689919121"}'
The result is returned in outputs[0].data. Lookups that find nothing fail with a not-found error.
| Name | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Walmart product page URL. |
requireFields | array | No | Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example productId, and it is served only by a source that returns every one |
Billed at the actual cost of each call, about $0.001 per request. A call can cost more when the first data source fails and another one answers. Failed calls and lookups that find nothing are not charged.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/walmart/product" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"url": "https://www.walmart.com/ip/Apple-AirPods-Pro-2/5689919121"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
urlstringrequiredWalmart product page URL.
requireFieldsarrayOptional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `productId`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a product that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
Walmart ProductThis API Walmart | From $0.001 per call | JSON |
Walmart | $0.015 per call | Async JSON |
Walmart | $0.01 per call | Async JSON |
Walmart | $0.015 per call | Async JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/walmart/product with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
From $0.001 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: url (string). Optional: requireFields (array). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Walmart Product runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Walmart API access separately.