Walmart reviews search
Run job:search.walmart-reviews through the looot API: 1 provider, from $0.004 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.
Walmart reviews search.
Job id search.walmart-reviews, in Reviews & apps (Search engines). As of 2026-10-01, 1 provider serve it through 1 tool. Run job:search.walmart-reviews and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.
Inputs
This job has one tool, so it takes that tool’s fields. Any key you send passes through unchanged.
| Name | Type | Required | Description |
|---|---|---|---|
aspect_id |
integer | no | |
engine |
string | no | Fixed to “walmart_reviews” for this endpoint. Example: “walmart_reviews” |
page |
integer | no | |
product_id |
string | yes | |
rating |
string | no | |
sort_by |
string | no | |
verified_purchases_only |
boolean | no |
Providers and prices
| Provider | Tool | Price |
|---|---|---|
| SearchAPI.io | searchapi-io-walmart-reviews |
$0.004 per call |
A call that fails at the provider costs $0. See What’s free.
Output
Shape of the run’s result, checked against 1 real answer:
{ product: { link, title, rating, media_count, reviews_count, reviews_histogram: Record<string, { ... }>, recommended_percentage, reviews_with_text_count }, reviews: { customer_reviews: { id, date, text, title, badges: string[], rating, item_id, user_id, iso_date, item_name, user_name, seller_name, fulfilled_by, reference_id, negative_feedback, positive_feedback }[], top_negative_review: { id, date, text, badges: string[], rating, item_id, user_id, iso_date, item_name, user_name, seller_name, fulfilled_by, reference_id, negative_feedback, positive_feedback }, top_positive_review: { id, date, t... ...
The shape is cut here. Signed in, looot inspect searchapi-io-walmart-reviews prints all of it.
Run it
Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.
Example input with placeholder values:
curl -X POST "https://api.looot.ai/v1/runs" \
-H "Authorization: Bearer $LOOOT_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"endpointId":"job:search.walmart-reviews","input":{"product_id":"<product_id>","engine":"walmart_reviews"},"wait":30}'const response = await fetch("https://api.looot.ai/v1/runs", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
"Content-Type": "application/json",
"Idempotency-Key": crypto.randomUUID(),
},
body: JSON.stringify({
endpointId: "job:search.walmart-reviews",
input: {
product_id: "<product_id>",
engine: "walmart_reviews",
},
wait: 30,
}),
});
const run = await response.json();
console.log(run.status, run.result);import os
import uuid
import requests
response = requests.post(
"https://api.looot.ai/v1/runs",
headers={
"Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"endpointId": "job:search.walmart-reviews",
"input": {
"product_id": "<product_id>",
"engine": "walmart_reviews",
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To pin one provider, send its tool id as endpointId instead of job:search.walmart-reviews.