/falabella/products/search

POST /api/falabella/products/search

Price: 20 credits

Search Falabella products by keyword or category id, with filters (brand, seller, condition, color, price range, discount, rating, free shipping, CMR offer) and sorting. Returns product cards with id, name, brand, price, rating, seller and image. Use the region field for Chile (cl), Peru (pe) or Colombia (co).

How to use it

Search Falabella products by keyword or by category_id (one is required). Returns cards with id, sku_id, name, brand, url, image+images, price/event_price/normal_price (local currency), discount_label, rating, review_count, seller_id/seller_name, is_sponsored/is_best_seller/is_verified_seller. Filters: brand, seller_id, condition, color, min_price/max_price, min_discount, min_rating, free_shipping, cmr_offer; sort by relevance, price asc/desc, best rated or brand. Set region to cl, pe or co.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• region string — Falabella marketplace country: cl (Chile), pe (Peru), co (Colombia). (default: "cl"; one of: "cl", "pe", "co")
• keyword string nullable — Search keyword. (examples: "notebook", "iphone")
• category_id string nullable — Category id to list instead of a keyword search. (examples: "cat70057")
• count integer required — Max number of results to return (min: 1)
• sort string — Result ordering. (default: "recommended"; one of: "recommended", "price_asc", "price_desc", "best_rated", "brand")
• brand string nullable — Filter by brand name. (examples: "hp", "samsung")
• seller_id string nullable — Filter by seller id. (examples: "SC9F2B9")
• condition string nullable — Filter by product condition. (one of: "new", "open_box", "refurbished_excellent", "refurbished_very_good", "refurbished_good")
• color string nullable — Filter by product color. (one of: "yellow", "blue", "beige", "white", "burgundy", "brown", "gold", "gray", "purple", "orange", "black", "silver", "red", "pink", "green")
• min_price number nullable — Minimum price filter (local currency). (min: 0)
• max_price number nullable — Maximum price filter (local currency). (min: 0)
• min_discount integer nullable — Minimum discount percent filter (e.g. 20, 30, 40, 50). (min: 1; max: 100)
• min_rating integer nullable — Minimum average product rating filter (1-5 stars). (min: 1; max: 5)
• free_shipping boolean nullable — Only free-shipping items.
• cmr_offer boolean nullable — Only items with a CMR-card price offer.

Response

• @type string (default: "FalabellaSearchProduct")
• id string required
• sku_id string nullable
• name string nullable
• brand string nullable
• url string nullable
• image string nullable
• images array (default: [])
• price number nullable
• event_price number nullable
• normal_price number nullable
• currency string nullable
• discount_label string nullable
• rating number nullable
• review_count integer nullable
• seller_id string nullable
• seller_name string nullable
• offering_id string nullable
• category_id string nullable
• is_sponsored boolean (default: false)
• is_best_seller boolean (default: false)
• is_verified_seller boolean (default: false)

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.